--- title: "WhatsApp for Events and Ticketing: Templates and Flow" description: "WhatsApp for events and ticketing: registration confirmations, e-tickets with QR codes, reminders and venue changes with SMS fallback, plus sample templates." canonical: "https://omnichannels.ai/blog/events-ticketing-messaging/" language: "en" updated: "2026-11-06" publisher: "BroadNet Technologies" brand: "OmniChannels.ai" category: "marketing" primaryQuery: "whatsapp for events" keywords: ["whatsapp for events", "whatsapp event ticketing", "send e-tickets whatsapp", "event reminder messages", "event registration confirmation whatsapp", "event sms reminders", "whatsapp event updates", "post event survey whatsapp"] published: "2026-11-06" author: "OmniChannels.ai Editorial Team" reviewer: "BroadNet Messaging Solutions Team" readingMinutes: 10 answer: "Use WhatsApp for events by collecting opt-in at registration, then sending approved utility templates for the confirmation, the e-ticket with its QR code, reminders and venue changes, and SMS as fallback for urgent updates. Keep promotions for the next event in separate marketing templates, use free-form replies inside the 24-hour window for questions, and send a survey after the event." takeaways: ["Messages that follow a registration or purchase, such as the confirmation, ticket, reminder and venue change, fit Meta's utility category when they stay non-promotional. Adding an offer or upsell makes them marketing.", "A WhatsApp template can carry an image or document header, so the QR ticket can be delivered as an attachment, and up to two URL buttons, so a link to the ticket or map can sit on the message.", "Outside the 24-hour customer service window only approved templates can be sent, so event reminders days in advance must be templates.", "A venue change or cancellation should go on more than one channel. WhatsApp first, SMS as fallback after a short delivery timeout, and a confirmation of the new details on the ticket link.", "Treat QR codes as access credentials: unique per ticket, validated at the gate, and not shared on social media."] faq: - q: "Can I send event tickets and QR codes on WhatsApp?" a: "Yes. Send the ticket as a template message with an image or PDF document header, or as a link button to a ticket page that shows a unique QR code. Use an approved utility template if the message is sent outside the 24-hour window. Each QR code should be unique to one ticket and validated at the gate, so a forwarded screenshot cannot be reused." - q: "Are event reminders marketing or utility messages on WhatsApp?" a: "A reminder about an event the person registered for or bought a ticket to normally meets Meta's utility definition of a message specific to or requested by the user, provided it has no promotion. Invitations that try to persuade people to attend, and offers for other events, are marketing. Meta decides the final category on review, so write the template accordingly." - q: "Do I need consent to message event attendees?" a: "Yes. WhatsApp requires opt-in before you message someone, inside or outside the 24-hour window, so capture it at registration in a clear tick box that names WhatsApp and SMS and explains what you will send. Keep a record of when and how each attendee agreed, and offer a simple way to stop. This is general guidance, not legal advice." - q: "How early should I send event reminders?" a: "A common pattern is one reminder a few days before for planning, one the day before with entry details and one on the morning of the event with the gate, time and ticket link. Adjust to your audience, avoid prayer times and, in Ramadan, check timing against local schedules. Measure no-show rate and reply volume to refine." - q: "What happens if the venue or time changes at the last minute?" a: "Send an approved utility template on WhatsApp stating the change first, the new details and the ticket link, and add an SMS fallback if delivery is not confirmed in a short time. Meta's utility category includes messages essential to the user, which a venue change normally is. Update the ticket page so scanned codes show the new details." - q: "How do I run a post-event survey on WhatsApp?" a: "Send a short survey as a template or a WhatsApp Flow after the event, linked to the attendee's own ticket. Meta treats a request about a specific interaction as utility, whereas a generic survey is not, so keep it tied to the event they attended and put promotions in a separate marketing template." sources: - title: "Template categorization, WhatsApp Business Platform, Meta for Developers" url: "https://developers.facebook.com/documentation/business-messaging/whatsapp/templates/template-categorization" - title: "Template components, WhatsApp Business Platform, Meta for Developers" url: "https://developers.facebook.com/documentation/business-messaging/whatsapp/templates/components" - title: "Send messages and the customer service window, Meta for Developers" url: "https://developers.facebook.com/documentation/business-messaging/whatsapp/messages/send-messages" - title: "WhatsApp Business Messaging Policy" url: "https://whatsappbusiness.com/policy/" --- # WhatsApp for Events and Ticketing: Templates and Flow Canonical: https://omnichannels.ai/blog/events-ticketing-messaging/ Language: en Publisher: OmniChannels.ai by BroadNet Technologies This guide is for event organisers, venues, ticketing teams and agencies that want to run attendee communication on WhatsApp with SMS as a safety net. It covers the messages to send at each stage, the Meta template category for each, copy you can adapt and the mistakes that cause no-shows or blocked templates. ## What should you send at each stage of an event? Send a confirmation at registration, the ticket straight after, reminders in the days before, live updates during and a survey afterwards. Each stage has its own template, category and fallback. | Stage | Message | WhatsApp category | SMS fallback | |---|---|---|---| | Registration | Confirmation with event name, date, venue | Utility | Yes, short | | Ticket | E-ticket with QR code (image or PDF) | Utility | Link to ticket page | | Planning | Reminder a few days before | Utility | Optional | | Day before | Entry details, gate, time, what to bring | Utility | Yes | | Day of | Morning reminder and ticket link | Utility | Yes | | Change | Venue, time or cancellation | Utility | Yes, urgent | | During | Live schedule updates, replies to questions | Service (inside the window) | Rarely | | After | Survey, thanks, recordings | Utility if tied to the attendee's own visit | No | | Next event | Early-bird or invitation | Marketing | Only with SMS consent | The category is chosen by Meta on review from the content, not from what you label it. Meta's documentation says utility templates must be non-promotional and either specific to or requested by the user, or essential to them. Adding an offer or a push to buy makes a template marketing. ## How do you collect consent at registration? Add an unticked opt-in box to the registration form that names the channels, describes the messages and links to your privacy notice. WhatsApp's policy requires opt-in before messaging a person, so this is the foundation for everything that follows. Suggested wording: "Send me my ticket and event updates on WhatsApp and SMS. Marketing about future events only if I tick this second box." Keep the two permissions separate, as marketing consent should not be a condition of getting a ticket. Record the timestamp, the form version and the number. Our [opt-in consent generator](/tools/opt-in-consent-generator/) produces wording and [opt-in and consent for multichannel campaigns](/blog/opt-in-consent-multichannel-campaigns/) explains the evidence to keep. Ask for the attendee's mobile number in international format and validate it with the [phone number formatter](/tools/phone-number-formatter/). ## How do you deliver e-tickets and QR codes on WhatsApp? Deliver the ticket as a template with an image or document header, or with a URL button to a ticket page. Meta's template components allow image, video and document headers, and up to two URL buttons with one variable each. Options, from simplest to most robust: 1. **Image header with the QR code.** The attendee saves it from the chat. Easy, but a screenshot can be forwarded. 2. **Document header with a PDF ticket.** Suits multi-session passes and invoices. 3. **URL button to a ticket page.** The page shows a QR code that refreshes and can display the latest venue or time. The variable in the button can carry the ticket ID. Whatever you choose, treat the QR code as a credential: unique per ticket, linked to one attendee and marked as used when scanned. Use the ticket ID, not the attendee's name, in the URL, and make it hard to guess. Body text in a template is limited to 1,024 characters and the header text to 60, so keep the details short and put the full schedule on the ticket page. ## What are good WhatsApp templates for events? Good event templates are short, specific and free of promotion. Below are five examples for a synthetic expo called Najm Expo. Variables are shown in double braces and each template is labelled with the Meta category it is written for. **1. Registration confirmation (Utility)** > Hello {{1}}, you are registered for Najm Expo on {{2}} at {{3}}. Your ticket ID is {{4}}. We will send your QR ticket shortly. Reply STOP to opt out of event messages. **2. E-ticket (Utility, image or document header, URL button "View ticket")** > Hello {{1}}, here is your ticket for Najm Expo, {{2}}, {{3}}. Gate: {{4}}. Please bring this QR code and a valid ID. **3. Day-before reminder (Utility)** > Reminder: Najm Expo is tomorrow at {{1}}. Gate {{2}} opens at {{3}}. Parking and map: use the button below. Your ticket ID is {{4}}. **4. Venue or time change (Utility)** > Update for Najm Expo, {{1}}: the session "{{2}}" has moved to {{3}} at {{4}}. Your ticket is still valid and no action is needed. **5. Invitation to next year's event (Marketing)** > Hello {{1}}, thank you for joining Najm Expo. Registration for the next edition is open. Tap below to reserve your place early. Notice that template 5 is marketing because it persuades the person to act. If template 3 added "Buy a VIP upgrade for tomorrow", Meta could treat it as marketing, which is also billed at the marketing rate. Check the current rates on our [WhatsApp pricing by country](/whatsapp-pricing/) pages and in Meta's rate card; do not rely on a remembered figure. Browse more wording in the [message templates tool](/tools/message-templates/) and the [WhatsApp template examples](/blog/whatsapp-message-template-examples/). For approval tips see [WhatsApp template categories and approval](/blog/whatsapp-template-categories-approval/). ## What should the SMS fallback say? The SMS fallback should state the essential fact first and fit in one segment. Use GSM-7 for English (160 characters, 153 per part when joined) and expect Unicode for Arabic (70 characters, 67 per part). | Purpose | Text | Characters | Encoding | Segments | |---|---|---|---|---| | Confirmation | `Najm Expo: you are registered. Ticket NX4821. Gate B opens 9:00 on 12 Dec. Show this SMS or QR in the app.` | 106 | GSM-7 | 1 | | Reminder | `Najm Expo reminder: tomorrow 9:00, Gate B, Hall 3. Ticket NX4821. Reply STOP to opt out.` | 88 | GSM-7 | 1 | | Change | `Najm Expo: Hall 3 session moved to Hall 5, 10:30. Ticket NX4821 is unchanged.` | 77 | GSM-7 | 1 | | Arabic ticket | `نجم إكسبو: تذكرتك NX4821. البوابة B تفتح 9:00 يوم 12 ديسمبر.` | 60 | Unicode | 1 | Check your own copy in the [SMS character counter](/tools/sms-character-counter/), because a single emoji or curly quote turns an English message into Unicode with a 70-character limit. If the message is sent to a promotional audience, add opt-out text and use a registered sender ID where the country requires one; see the [sender ID checker](/tools/sender-id-checker/). Our regulation data shows transactional traffic running 24/7 in the UAE and Saudi Arabia while promotions follow quiet hours; confirm each country in [SMS marketing rules by country](/blog/sms-marketing-rules-by-country/). ## How do you handle last-minute changes and cancellations? Send one clear message on the primary channel straight away, then a fallback to anyone whose delivery is not confirmed within a few minutes. The first line must state what changed. Procedure: 1. Update the event record and ticket page first, so anyone who clicks sees the truth. 2. Send the approved utility template on WhatsApp to every ticket holder, using the delivery status per recipient. 3. After a short timeout, send the SMS version to unconfirmed recipients through [channel fallback](/blog/channel-fallback-strategy/). 4. Post the same notice on the website, social accounts and the entry signage. 5. Open the inbox for questions, and route refunds and rebooking to agents. Replies from attendees open a 24-hour customer service window in which you can answer with free-form text, images and interactive messages. After the window closes only approved templates can be sent. ## How do you run live updates and Q&A during the event? Use the free-form window and interactive messages for attendee questions, and a broadcast of utility templates for schedule changes. Reply buttons and lists answer the usual questions without a human: "Where is Hall 5?", "Find my session", "Contact the help desk". Keep the rules simple. Do not send agenda marketing during the event, hand over to a person when the bot cannot answer and avoid message storms by combining changes into one update. A [shared inbox](/platform/unified-inbox/) lets the help desk see the whole conversation, and our [WhatsApp interactive messages guide](/blog/whatsapp-interactive-messages-buttons-lists/) covers buttons and lists. A [WhatsApp Flow](/blog/whatsapp-flows-guide/) can also handle session choice or last-minute registration inside the chat. ## What should you send after the event? Send a thank-you with a short survey within a day, then a separate marketing message for the next event, only to people who agreed to marketing. Keep them apart. A survey tied to the person's own visit meets Meta's utility examples of feedback requests about a specific interaction, whereas Meta states that generic surveys do not. Ask two or three questions, such as overall rating, one reason and permission to follow up. Our [CSAT, NPS and CES guide](/blog/csat-nps-ces-customer-satisfaction-metrics/) explains the scores. ## Are there GCC and Ramadan considerations? Yes, but keep them general. Time reminders around local working hours and prayer times, write in Arabic and English where the audience is mixed, and in Ramadan expect different attendance hours and evening events. Local rules on promotional messaging hours can differ from transactional ones, so check the country page rather than assuming; our regulation data covers hours for the UAE and Saudi Arabia, for instance. See [Ramadan messaging campaigns in the GCC](/blog/ramadan-messaging-campaigns-gcc/) and [Arabic customer messaging best practices](/blog/arabic-customer-messaging-best-practices/). ## Worked example: a three-day Riyadh trade show "Najm Expo", a synthetic exhibition, has 6,000 registered attendees across three days. - **At registration:** a form with a WhatsApp and SMS opt-in and a separate marketing tick box. Confirmation sent instantly as a utility template. - **Ticket:** a PDF header and a "View ticket" button with the ticket ID as variable. The ticket page shows a QR that is marked used on first scan. - **Reminders:** a utility reminder three days before, entry details the day before, and a morning message with the gate. - **Change:** a hall change on day two goes out as one utility template, with SMS to those not confirmed after ten minutes, and the signage updated. - **After:** a two-question survey to scanned attendees. Marketing for next year goes only to those who ticked the second box. The team tracks delivery, replies, no-show rate against registration and the share of tickets scanned, and reviews them after the show. ## What mistakes cause problems? - **Promotion inside utility templates.** It can lead to recategorisation to marketing, and misuse can bring warnings and restrictions under Meta's rules. - **One QR code for a whole group.** One screenshot admits everyone. - **Sending only on WhatsApp.** Attendees without it, or with failed delivery, miss urgent changes. - **Long messages.** Put schedules on a page and link them. - **No opt-out.** Keep STOP handling for both channels. - **Forgetting the window.** A reminder days ahead is a template, not a free-form message. ## How OmniChannels.ai helps OmniChannels.ai, powered by BroadNet Technologies, sends WhatsApp templates (utility and marketing) with media headers and buttons, SMS through direct operator connectivity and configurable fallback from WhatsApp to SMS. Campaigns support Excel or CSV upload, personalisation and scheduling, and the Omni Inbox gives the help desk one thread per attendee. Delivery reports can be exported to CSV. To plan an event flow, [book a demo](/demo/).