Event reminder SMS templates for ticket holders

A good event reminder SMS tells ticket holders which event they're attending, when to arrive, where to go, and what they need to do next. Use a short text for the information they need close to arrival, put the longer instructions in email, and send a separate update whenever an important detail changes.

So you've sold the ticket. The money's in, the buyer has a confirmation, and your attention moves to getting the event ready. Then the questions start. Where's the entrance? Is that the doors time or the show time? Can I show the ticket on my phone?

Some questions deserve a conversation. Others tell you the information never reached the person who needed it. Your reminder should deal with those before the queue forms.

Below you'll find templates for normal reminders, ticket access, arrival instructions, and changes. We'll also cover when to send them, who should receive them, and how to check the final message. Copy the ones your event needs. You don't need to send the whole collection.

Start with the basic event reminder template

Use this when nothing has changed and the ticket holder needs the essentials.

The organizer name helps the recipient recognise you. The event name helps someone who has several bookings. Separate doors from the start time if both matter, and link to the current arrival information.

Here's an illustrative version with the fields filled in:

Replace the example names and times with your own. Then read it as someone who has never visited the venue. If they can still walk to the wrong entrance or arrive after the performance starts, fix that before sending.

Don't start with "The wait is almost over!" and spend the remaining space squeezing in the address. Excitement belongs in your event marketing. This person has already paid. Help them enjoy what they bought.

Decide what belongs in a text

The first thing you want to do is separate information people need now from information they might want later.

Arrival time, an entrance change, a ticket access reminder, and an immediate transport problem can belong in SMS. A full programme, parking options, accessibility arrangements, refund terms, and a detailed list of permitted items need more room. Put those in a clear email or event information page and use the text to point people there.

Your SMS should still say the essential thing without requiring a click. "Important update, see link" makes the attendee work to discover whether you're cancelling the event or announcing a new food vendor. "Tonight's show is cancelled" gives them the information immediately.

Think about what the attendee is doing. A person standing outside needs the entrance name. A person travelling across the country needs enough notice to change plans. A person checking their phone during work needs a message they can understand quickly.

You don't need a text for every email. If your email says everything clearly and no time sensitive action follows, another message may add nothing. SMS earns its place when missing the information would cause a real problem.

Event reminder SMS templates you can adapt

These are starting points, not finished sends. Replace every bracketed field, add whatever sender identification or opt-out wording your service and applicable rules require, and check the completed version. The examples are not promises that each message will fit into one billable SMS segment.

The day-before reminder

Send this when attendees need a final prompt to plan their journey. Include the date because someone might read the message late. "Tomorrow" on its own becomes unhelpful once tomorrow arrives.

For a venue your audience knows well, the name may be enough. For a new location, include the street or direct people to a page with the address and correct entrance. Don't assume the venue's main postcode takes people to your check-in point.

The event-day reminder

This works when the main arrival problem is people searching for tickets at the front of the line. Use it only if opening the ticket before arrival is actually helpful for your ticket system.

If doors and the performance start are different, include both when space allows. Otherwise make the most important time explicit and put the rest in the linked instructions. "See you at 7" doesn't tell anyone what happens at 7.

The ticket access reminder

Use this when you expect ticket access questions, rather than sending a replacement ticket link to everybody by default. A reminder can point people back to the place where their tickets already live.

For events sold through Loopyah's ticketing, the confirmation email links to the buyer's QR tickets. That gives you a specific instruction to use. Make sure your help page explains what a buyer should do if they can't find the confirmation.

The timed-entry reminder

Send each ticket holder their booked slot. Don't write "Doors open at noon" to someone whose ticket admits them at 3pm and leave them to work out the difference.

If attendees can arrive within a window, state that window accurately. If late arrivals need staff assistance, explain the process on the information page. Never invent a grace period because it sounds friendlier than the policy you've actually agreed with the venue.

The workshop preparation reminder

The required item should be genuinely necessary. A laptop for a software workshop belongs here. A long list of optional stationery probably doesn't.

Give people enough notice to prepare. An instruction to install software is useful before they leave home, not when they're already waiting outside. Put download instructions and technical requirements in the longer message, and keep the text focused on the action they might otherwise miss.

The reserved-seating reminder

Only send this to the section that uses that entrance. A general instruction to every ticket holder can send people around the building unnecessarily.

For reserved seating, the reminder should match the purchased seat and the venue's actual entry plan. Loopyah's seat charts let buyers choose seats on a venue layout. Your operations team still needs to confirm the routes, signs, and assistance available when those buyers arrive.

The parking or transport reminder

A useful restriction might be "No parking at the venue" or "North car park closes at 11pm." The point is to prevent a problem, not to repeat every route listed on your website.

Verify transport information close to the event. A service you checked when tickets went on sale may have engineering works or a changed timetable now. If you're linking to a transport operator, make sure the page covers the relevant date and route.

The accessible-arrival reminder

Use the venue's confirmed wording. A step-free entrance doesn't tell someone whether the whole route, seating area, or toilet provision meets their needs. The linked page should explain the actual arrangements and how to ask a question.

Don't put a person's disability or access request into a text that could appear on a locked screen. Send useful arrival information without exposing private details. Where individual support has been agreed, confirm it through the appropriate private conversation.

The age or ID reminder

Write the rule you can enforce. "Bring ID" leaves people guessing whether a photo on their phone is accepted or whether everyone needs identification.

This requirement should already have been clear before purchase. A reminder reinforces a disclosed condition; it shouldn't introduce a new restriction at the last minute. If the condition has changed, treat that as an event update and work through the consequences for affected ticket holders.

The door-opening time change

Say what changed and what remains relevant. If only doors moved, people shouldn't have to wonder whether the performance moved too.

Pause the old reminder before sending the update. Otherwise someone can receive your correction and then a scheduled text with the original time. Check email, the event page, and staff instructions as well. One correct SMS won't fix several other places still showing the wrong information.

The start-time change

Give the new time directly. "Running a little late" isn't enough for someone deciding when to travel or whether they can still catch the last train home.

Only say you've updated the information after you've done it. If the final start time isn't confirmed, say when the next update will come instead of guessing. Your audience can cope with uncertainty better than confidently wrong instructions.

The venue change

A venue move deserves more than a casual reminder. People may have booked travel, arranged assistance, or chosen the event because the original venue worked for them.

Send the full explanation by email, update the event page, and make the SMS clear enough to stop someone travelling to the wrong place. Explain ticket validity and any available options in the detailed update. Don't promise that every ticket or seating arrangement transfers unchanged unless that's confirmed.

The entrance change

This is particularly useful when mapping apps point to the old entrance. Name the street or landmark that helps people find the new one.

Have staff and signs in place before directing people there. A text is one part of the arrival plan. It doesn't replace the people who manage the queue or help someone who never received the message.

The weather update

The confirmed decision might be that the event is going ahead indoors, that entry is delayed, or that the event is cancelled. Don't send "We'll probably be fine" while the team is still deciding.

For weather that affects safety, use the message approved by the people responsible for the event. Keep the instruction practical. "Wear sensible shoes" can be useful preparation, but it isn't a substitute for a clear decision about unsafe conditions.

The cancellation notice

Put the cancellation first. The attendee needs to know before you explain how disappointed the team feels.

The linked information should say what happens next, who handles questions, and when people can expect another update. Promise only the refund process and timing you've confirmed. Send email too, and make the notice visible wherever attendees will check the event.

The postponement notice

Postponed doesn't automatically mean everyone can attend the new date. Explain the options in the full update, including what happens if the new date hasn't been agreed.

Remove the original date's scheduled reminders. When a replacement date is confirmed, check recipients again rather than carrying over an old list without reviewing refunds, transfers, and contact preferences.

The online-event reminder

For an online event, the time zone is part of the time. Someone joining remotely can't infer it from your venue address. Use a label your audience understands and check any daylight saving change that falls between purchase and the event.

Keep personal joining links private. A general help page can explain how to access the session without exposing a ticket holder's link or letting an unpaid visitor into a paid event.

Test the joining journey as a buyer. Can they open the link on a phone? Is another login required? Does the waiting room explain when the session starts? Put those answers in the preparation email. The text should bring the attendee back to instructions that already work.

When should you send event reminder texts?

There isn't one best schedule for every paid event. Start with the decisions your ticket holders need to make, then choose the send times that help them make those decisions.

For a straightforward local evening event, a day-before reminder can be enough. Add an event-day message if it contains useful arrival information people are likely to need on their phones. For a workshop with preparation, send those instructions earlier. For an event that requires long-distance travel, send important logistical details before people have to commit to the journey.

Treat that as a starting plan, not an evidence-backed promise about attendance. The right schedule depends on your event, audience, previous questions, and the permission you have to contact people.

Avoid sending several texts that all say "Don't forget." Each send should answer a different question or communicate a real change. If the event-day text repeats the day-before message word for word, decide whether you need both.

Choose a reasonable local time for routine reminders, and confirm the rules and sending restrictions that apply in the recipient's location. Travellers can be in another time zone, so don't assume the event's time zone always matches the phone owner's.

For an urgent change, speed matters. Still check the audience and wording before sending. A fast message with the wrong venue creates another problem your team has to fix.

Late buyers need attention too. Someone who buys after the day-before reminder should still receive the current ticket confirmation and arrival instructions. They don't need the old reminder arriving immediately after checkout if it adds nothing new.

Send to the right ticket holders

Build the audience around the information you're sending. An entrance change for balcony tickets belongs with balcony ticket holders. A Saturday reminder shouldn't go to people booked for Sunday. Refunded or cancelled orders shouldn't keep receiving routine arrival prompts.

The tricky part is that a buyer isn't always every attendee. Someone can buy several tickets for friends, buy a gift, or book on behalf of a colleague. Check what contact information you actually hold and who is authorised to receive the message.

Don't assume a purchaser's phone number gives you permission to text everyone in their party. Equally, don't ask the purchaser to hand over friends' numbers so you can add them to a marketing list.

Where you only have the buyer's contact, make the information easy for them to pass to the people attending. Your order page or arrival email can explain how the group should access its tickets and whether members need to arrive together.

Check ticket transfers before an important send. If ownership changes but your SMS list doesn't, the update can land with someone who no longer has the ticket while the new holder knows nothing about it. Understand how your ticket system and messaging service keep that information current.

Deduplicate carefully. Two tickets don't necessarily mean two identical texts to the same number. But one number might represent bookings for different dates or entry slots, so don't merge away information that someone needs.

Keep reminders separate from promotional SMS

A ticket holder needing directions and a past attendee receiving an offer are different situations. Write and send them accordingly.

The UK's Information Commissioner's Office explains that factual service messages can sit outside direct marketing, but adding promotional content changes the assessment. A reminder about an event someone already bought can be a service message; adding an invitation to buy an upgrade can turn it into marketing.

That's why "Doors open at 7pm" and "Doors open at 7pm, upgrade to VIP here" shouldn't share the same sending decision. If you want to sell the upgrade, use the appropriate marketing audience and rules for that separate message.

The ICO's electronic mail marketing guidance covers texts as well as email. It sets conditions for marketing consent or the customer soft opt-in and requires an opt-out. Those are UK rules, not a blanket answer for every country.

Before using these templates, confirm the requirements for your audience, your sending method, and your SMS service. A ticket purchase alone isn't a universal permission slip for any text you want to send.

Keep evidence of the permission or other applicable basis you're relying on, respect contact restrictions, and use an opt-out process your service actually supports. Don't write "Reply STOP" if replies aren't supported by the sender you've chosen. A phone number collected for one purpose shouldn't quietly become a general advertising list.

Check the message length after filling the fields

Your short template can become a long message once you insert the full venue name, actual link, and required footer.

Twilio's SMS character limit documentation explains that a single segment generally holds 160 characters with GSM-7 encoding, while UCS-2 has a 70-character limit. Longer texts split into segments, with less room per segment because some space is used to join the pieces.

You don't need to learn the encoding details to write a useful reminder. You do need to preview the completed message in your sending service and check its segment count. An emoji or curly punctuation can change the encoding and increase that count.

Keep necessary information. Cut the empty enthusiasm first. "We are so excited to welcome you to an unforgettable evening" takes space that could tell someone which entrance to use.

Don't damage names or remove helpful language just to force everything into one segment. If the audience needs another language, write that language properly and budget for the result. Saving on a text that the recipient can't understand is a poor trade.

For cost planning, use the actual rate your service charges for the destination and the completed message. Recipient count multiplied by billable segments and your applicable rate gives a basic send estimate. Check any additional service charges separately.

Make the link and sender easy to trust

A person who paid for your event should recognise why you're texting them. Put your organizer or event name early, use a sender you've told people to expect, and link to a page they can identify.

The Federal Trade Commission's guidance on recognising spam texts describes how scammers use unexpected messages and links to seek personal or financial information. Your legitimate event update shouldn't resemble that experience.

Don't ask for card details, passwords, or one-time login codes by reply. Don't tell people to pay an unexpected charge through a mysterious link to keep a ticket they've already bought.

If payment or account action really is required, explain the issue through your normal secure process and give people a way to verify it independently. Your published contact details should match the support information your staff uses.

Open the reminder link on a phone before sending. Check whether it lands on the current event, whether the important information is easy to find, and whether it exposes somebody else's order. A general arrival page should not contain private ticket information.

Give email and SMS different jobs

Email can carry the full plan. SMS can bring the immediate instruction back into view when someone needs it.

For example, your arrival email might explain public transport, parking, entry conditions, accessibility information, and how to find the ticket. The day-before text can give the event name, time, and one link back to that information.

Loopyah's attendee email tools support event updates to ticket holders, scheduled sends, and test emails. That lets you put the detailed instructions alongside the ticketing information and check the email before it goes out.

These SMS templates don't assume Loopyah sends texts. If you use a separate SMS service, confirm how its audience stays current and how it handles replies, suppression, and delivery problems. Keep the information consistent across both channels.

Here's what's useful about doing this properly. The text can stay short because the fuller answer already exists. Staff can direct people to the same information instead of explaining a different version in every reply.

Test the reminder before the audience gets it

Read the final message aloud and send a test to a real phone. Check the filled fields, link, sender, segment count, and any footer your service adds.

Then have someone outside the planning team read it. Ask them when they would arrive and which entrance they would use. Their answer tells you more than asking whether the text "looks good."

Check the audience count against the ticket group you meant to contact. A surprising count deserves investigation before sending, especially after refunds, transfers, or a ticket-type change.

Confirm who handles replies and questions. If the sender can't receive replies, provide a real help route where needed. Don't invite replies that disappear while your attendee thinks they're waiting for an answer.

For changes that affect arrival, coordinate with venue staff. The Health and Safety Executive's crowd-management guidance puts roles, planning, and crowd controls within the wider safety work. Your reminder should support that agreed plan, rather than create new instructions the door team hasn't seen.

Plan for people who miss the text

Some ticket holders won't receive the SMS. Others will see it after they arrive. Keep the event page current, send important changes by email too, and make sure staff can give the same answer.

If an entrance moves, put help at the old entrance where practical. If a ticket holder can't open a ticket, give the door team a confirmed way to handle that situation. If the event is cancelled, consider where someone would look before travelling.

Build that fallback into the plan before sending. Your reminder is useful, but your event still has to work for the person whose phone is flat. That includes knowing who can make a decision when a ticket problem holds up someone already waiting at the door.

Review what happened after the event

Start with whether the information reached the intended audience. Review failed deliveries and the questions people still asked. A delivered message doesn't prove someone read it or followed the instruction.

Look at the door experience too. Were people ready with tickets? Did they arrive at the correct entrance? Did a repeated question reveal something missing from the reminder or the linked page?

Change the next send around what you learn. If everyone asks about parking, improve the travel information. If people confuse doors and start time, make both explicit. If an unnecessary event-day text generates complaints, remove it.

Be careful about claiming SMS increased attendance. Attendance can change because of the programme, weather, travel, or the people who bought. A comparison between two different events doesn't isolate the effect of your reminder.

The useful result is a reminder you can trust. Choose the template that solves the attendee's actual problem, fill it with confirmed details, send it to the right ticket holders, and check what happened. Help people get through the door ready for the event they paid for.