An event is the only product that loses all its value the minute it starts. This concentrates sales in the last days, turns every unanswered question into an empty seat, and makes attendance confirmation as important as the promotion itself. This guide covers the entire WhatsApp operation, from the first announcement to post-event, detailing what to automate, what to handle personally, and where money is currently being lost.
In this article
- The problem for ticket sellers
- The five stages of event sales
- Real objections and how to answer them
- Batches, deadlines, and genuine urgency
- The confirmation that prevents empty seats
- What to automate and what to keep human
- What the official API allows in this case
- Online events have their own rules
- Group, list, or individual chat
- Post-event, where the next sale is
- What to record for each participant
- The accounting of one edition
- Mistakes that empty the room
- Where to start
- Frequently asked questions
The problem for ticket sellers
Selling an event is selling a date. Unlike a digital product that remains available indefinitely, a ticket loses all value the minute the event starts. This changes the operational logic: sales are concentrated, most people postpone their decision until the last days, and every unanswered question in the final week becomes an empty seat that won’t be filled.
That’s why WhatsApp has become the central channel for those producing events, in-person courses, workshops, retreats, congresses, or live classes. It addresses three critical moments: the question before purchase, confirmation after purchase, and the reminder that ensures attendance.
This guide covers the entire operation—from the first announcement to post-event—with what to automate, what to keep human, what the official platform allows, and the accounting that shows where money is currently being lost.
The number almost no one tracks: the difference between tickets sold and people present. In free events, this gap can be huge, and in paid events, it determines whether there will be a second edition.
It’s worth saying from the start that most money lost in event sales isn’t in the announcement. It’s in three much cheaper places to fix: unanswered questions during the decision week, people who bought but forgot, and the participant list lost between editions, forcing the producer to buy the same audience again who already attended.
Continue reading for free
Fill out once and unlock this and all other blog articles. We don’t charge anything — we just want to know who we’re writing for.
Takes 20 seconds. Prefer to talk directly on WhatsApp?
The five stages of event sales
Each has a different message and objective:
- Interest. The person saw the announcement or invitation and wants to understand what it’s about. The goal here isn’t to sell, but to qualify and answer questions.
- Decision. They understand and are evaluating price, date, travel, and schedule. This is where most objections arise.
- Purchase. The moment of the payment link, where friction kills sales.
- Confirmation and preparation. Between purchase and event, when people forget, get disorganized, or change their minds.
- Attendance. The 48 final hours that decide how many seats will be occupied.
Operations that treat everything simply as "selling tickets" lose out in the last two moments, which are precisely the cheapest to improve.
Real objections and how to answer them
In events, objections are rarely about content. They are logistical and can be answered with information:
- "Can I make it?" Date, start and end times, and what happens if the person arrives late.
- "How do I get there?" Address, landmarks, parking, transportation. For online events, what is needed to watch.
- "What if I can’t go?" Transfer policy, rescheduling, or access to the recording. This is the most underestimated and easiest objection to resolve.
- "Is it worth the price?" Answered with detailed programming, who will be present, and what the person takes away.
- "Can I pay in installments?" For higher ticket prices, this defines the sale.
Having these five answers written and ready to send allows responding in minutes instead of hours — and in event sales, responding quickly is more valuable than responding well.
Batches, deadlines, and genuine urgency
Event sales have a rare advantage: the urgency is real. The date exists, seats are limited, and the promotional batch has a deadline. This allows using scarcity without fabricating anything, which is exactly what maintains credibility.
Three precautions make a difference. The first is to deliver what was announced: a batch that "ends" but continues at the same price teaches the audience to ignore all subsequent deadlines. The second is to notify beforehand, not after — a "last day of batch" message sent the day before converts much better than a "batch ended" message. The third is not to stack triggers: limited seats, deadline, bonus, and discount all at once sound like pressure and undermine the trust the event needs.
The confirmation that prevents empty seats
Buying doesn’t mean attending. Between purchase and event, there is a gap when people forget, change plans, or simply don’t organize their day. The sequence that increases attendance has four contacts, none of which are demands:
- Right after purchase: confirmation with essential data — date, time, location or link, and what to bring. Short and to the point.
- One week before: detailed schedule and useful information, such as parking, arrival time, or preparation.
- One day before: reminder with the most practical information possible, including room opening or registration time.
- On the morning of the day: a short message with the address or link and a last-minute contact phone number.
In online events, this last contact is what most changes the outcome, because the person is one tap away from joining and one forgetful moment away from missing out.
What to automate and what to keep human
The division that works is clear. Automate everything predictable: purchase confirmation, reminder sequence by date, sending tickets or access links, registration instructions, and post-event surveys. Keep human everything exceptional: specific content questions, ownership transfer requests, installment negotiations, payment problems, and any irritated contact.
An important operational point: messages triggered by date need to be calculated from the event date, not the purchase date. Someone who buys three months in advance and someone who buys the day before need different reminders, and misconfigured systems send "one week left" to those who bought the day before.
What the official API allows in this case
Events are one of the cases where the official WhatsApp platform fits well because most messages are utility: purchase confirmation, scheduling reminder, time updates, and access instructions. Three points must be clear:
- Approved template is required to start conversations outside the service window, and the correct category depends on content — confirmation and reminders are utility, promotional invitations are marketing.
- Recipient permission remains mandatory. Buying participant lists from other events is the fastest way to get blocked and receive complaints.
- Within 24 hours after the person writes, the conversation is free, covering most question handling.
In practice, those who regularly organize events benefit from having the official number precisely because of predictability: the message arrives, is delivered, and doesn’t depend on a phone being on a desk.
Online events have their own rules
Live classes, online workshops, and digital congresses share the date logic, but the operation changes in four points worth addressing separately.
The first is attendance rate, which is usually much lower than in-person events because there’s no travel cost or social pressure to attend. This makes the reminder sequence even more decisive, especially the message sent at start time with the direct link and nothing else. A one-line message at the opening minute usually brings back a relevant portion of those who had gotten distracted.
The second is access. Links sent in advance get lost in chat history, and people ask again just when everyone else is asking. The practical solution is to resend the link on the day, always, even to those who already received it, and to use a fixed, short address instead of one generated for each session.
The third is the recording. Promising a recording reduces live attendance, and promising nothing reduces sales. The balance that usually works is offering access to the recording for a limited time and making clear that questions and interaction happen only live, preserving the value of attendance without penalizing those with unforeseen issues.
The fourth is sales made during the event. In online events, the offer presented at the end needs an immediate WhatsApp path because the person has their phone in hand and the decision window lasts minutes. Having someone attending in real time during and just after the broadcast usually pays off more than any presentation adjustment.
Group, list, or individual chat
Many producers create a group with all participants. It works for community and engagement but has three problems in sales operations: one dissatisfied person speaks to everyone else, no one can be served individually without leaving the group, and each participant’s history is lost.
The most efficient design separates functions. Service and operational messages stay in individual chats, where history exists and the person can be served. The group, when it exists, serves the event experience and community afterward, with clear rules and moderation. Mass communication is sent individually, not via group, because group messages are read by fewer people than expected.
Post-event, where the next sale is
The most valuable window of an event is the 72 hours following it, when the experience is still fresh. It’s the time to request feedback, deliver promised materials, offer the recording to those who couldn’t attend, and open the interest list for the next edition.
Two moves yield especially well. The first is separating those who attended from those who bought but missed: these are different audiences, and the message to the latter should offer a solution, like access to the recording or credit for the next edition, instead of an awkward reminder. The second is recording who participated, because this list is the most qualified base the operation will have for the next event, and most producers lose it between editions.
What to record for each participant
With organized history, each edition becomes easier than the last. The minimum useful data is: which announcement or invitation the person came from, which batch they bought in, the amount paid, attendance, survey rating, and interest in another event. Six pieces of information that fit in simple service fields and, over three editions, allow discovering which channel brings those who actually show up — which is quite different from which channel brings buyers.
The accounting of one edition
An in-person workshop with 120 seats and a ticket price of R$ 390:
- Potential revenue with a full house: R$ 46,800.
- Common scenario, without organized operation: 94 tickets sold, 71 present. Revenue of R$ 36,660 and attendance of 76%.
- Scenario with quick service and reminder sequence: 112 sold, 101 present. Revenue of R$ 43,680 and attendance of 90%.
- Revenue difference: R$ 7,020 in the same edition.
- Attendance difference: 30 more people in the room, which changes the event’s energy, the number of testimonials, and sales made during it.
The gain didn’t come from more advertising. It came from quick responses during the decision period and reminders to those who already bought.
Mistakes that empty the room
- Taking too long to respond in the final week, which is exactly when most decide.
- Extending the announced batch, teaching the audience to ignore deadlines.
- Not having a clear absence policy, which blocks purchases from those with uncertain schedules.
- Sending reminders based on purchase date instead of event date.
- Using groups as service channels, mixing complaints with announcements.
- Losing the participant list between editions.
Where to start
Write the five logistical objection answers and have them ready to send. Set up the four-reminder sequence calculated from the event date. Separate individual service from community groups. Define and publish absence and transfer policies. Record attendance at the event’s end and send the post-event message within 72 hours. That alone, without any new advertising investment, usually moves attendance rates enough to pay for the entire operation of the next edition.
Frequently asked questions
How to increase attendance at an event?
Attendance rises with a sequence of contacts between purchase and event date, none of which should feel like a demand. The effective design has four messages: a short confirmation right after purchase with date, time, location or link, and what to bring; a message about a week before with detailed programming and practical info like parking or arrival time; a reminder the day before with the most operational info possible; and a short message on the event morning with address or link and a contact phone number. A technical detail often ruins everything: triggers must be calculated from the event date, never the purchase date.
Can I send event messages via the official WhatsApp API?
Yes, and events are one of the best fits for the official platform because most messages are utility: purchase confirmation, scheduling reminder, time change, and access instructions. To start conversations outside the service window, an approved template is required, and the category must match the content—utility for confirmations and reminders, marketing for promotional invitations. Recipient permission remains mandatory in all cases, and using participant lists from other events without consent is the fastest way to get blocked. Within 24 hours after the client writes, the conversation is free, covering question handling.
Is it better to create a group with participants?
Groups work well for community and event experience but are poor channels for sales operations and service. One dissatisfied person speaks to everyone at once, no one can be served individually without leaving the group, and each participant’s history is lost. The most efficient design separates functions: service, confirmation, and reminders happen in individual chats where history exists and specific responses can be given, while the group, when it exists, serves community and event experience with defined rules and moderation.
Fill the room with those who already bought.
VeyloCRM triggers the reminder sequence by event date, maintains individual service with history, and records attendance — the list that makes the next edition sell faster.