Playbooks · 5 min read
Events and Ticketing on WhatsApp: The Two Messages That Matter
We do not ship WhatsApp, so nothing below is a feature description. It is about a category where the channel does two unrelated jobs badly explained as one, and where separating them changes what you build.
Job one is selling: answering the questions people ask before they buy. Job two is operational: telling ticket-holders something changed. They have different audiences, different urgency, and different consent, and a setup that treats them as one thing fails at both.
Before the event: the four questions
Almost every pre-sale message is one of these, in some order.
- Is it still on, and are there tickets left? Asked more than anything else, and the answer changes constantly.
- Where exactly, and how do I get there? Not the venue name — the entrance, the parking, the nearest station.
- What are the timings? Doors, start, and whether the advertised time is when it begins.
- What is the ticket type difference? Which one includes what, and whether the cheap one still sees the stage.
All four are facts. None depends on who is asking. All four are safe to answer instantly, and answering them instantly demonstrably sells tickets, because the alternative is somebody deciding later and forgetting.
Nobody has ever bought a ticket because a reply was warm. Plenty have not bought one because a reply was slow.
On the day: the message with the highest value on the channel
The event moved, the timing changed, the gate is different, it is cancelled.
This is the single most welcome message a business can send on WhatsApp, and it is the one where the channel genuinely outperforms email — because people read it, immediately, without opening anything.
What Meta's rules do to the plan
Business-initiated messages generally require a pre-approved template, which has a practical consequence people discover at the worst moment: you cannot improvise an announcement the afternoon the venue changes.
The fix is to submit the templates you might need before you need them — cancellation, timing change, venue change — with the variable parts as placeholders. Doing that in the calm week costs an hour. Doing it on the day costs the announcement.
The specifics of categories, approval and pricing change and vary by country. Take them from Meta's own documentation on the day you plan around them.
The failure mode worth designing against
Not spam. Silence at the moment it counts.
The pattern: an event business builds an elaborate pre-sale flow, uses the channel heavily for promotion, accumulates blocks and reports over a season, and then finds its delivery degraded on the one day it needs to reach four hundred people about a cancelled show.
The reputational budget you spend on promotion is the same budget the emergency message draws on. That is the whole argument for restraint here, and it is more persuasive than any argument about tone.
What this looks like on Instagram
PostEngage answers Instagram comments and DMs, which is where a lot of ticket questions actually arrive — under the announcement post, publicly, from people who have not bought yet.
The useful shape there is comment-to-DM: the public reply says something short and true, and the private message carries the detail and the link. One rule handles the whole "is it still on" wave.
Two things worth setting on any event automation. The window: Instagram allows a reply to a comment for seven days, and a DM only within twenty-four hours of their last message, which is short relative to how long an event post keeps attracting comments. And the negative keywords, because a refund question arriving under a ticket-sales post is the one message that must not get the sales reply.
Why the post keeps working after the event
Something specific to this category, and usually treated as a problem rather than an opportunity.
An event post does not stop attracting comments when the event ends. People find it weeks later, ask whether there is another one, and get nothing — because the automation was switched off the morning after.
Leaving a rule running with a different reply is close to free and catches the one audience that is genuinely easy to sell to: people who wanted to come and could not. What they need is not the ticket link, which is dead. It is a way to be told about the next one, which is a capture rather than a sale.
The same applies to the questions that arrive during a run of events. A series accumulates a body of repeated questions that is stable across every date, and that body is the automation. Rewriting it per event is the mistake.
The counts worth keeping
There is no analytics product here on any channel. Three numbers, tallied by hand after each event: how many pre-sale questions arrived, how many were one of the four above, and how many people asked something the automation could not answer.
The third number is the one that tells you what to write next time.
Where to read more
For the broader event argument, there is a post on event marketing, and for the Instagram version of the ticketing question specifically, start here. The consent question is covered properly in the opt-in post.
