Seven deployments
Response rates on WhatsApp beat email badly. They also fall far short of what the marketing suggests, and one decision you make at registration decides which of those you get. Here is the whole picture from seven deployments, including the ones that went wrong.
Three moments from a real deployment, reconstructed. The message that opens the conversation, the discovery that follows, and the helpdesk traffic that ends up being most of the volume.
Sena
online
Hi Marie, you are registered for FOST New York next week.
I am Sena, the event concierge. Tell me what you are hoping to get out of the two days and I will put together your sessions, the sponsors worth your time, and who to meet.
A sentence or two is plenty, and a voice note is fine if you are walking.
09:12
Sena
online
Mostly looking for a payments provider we can actually integrate quickly
09:31
Useful, thank you. Two quick things so I get this right:
Are you evaluating now or later in the year, and is the blocker integration effort or pricing?
09:31
Evaluating now, we want something live before Q4. Integration effort is the blocker, pricing is fine
09:34
Got it. Three exhibitors match that, and two have engineers on the stand rather than sales.
Booth 214: ships a drop-in SDK, 2 week typical integration
09:34
What the organizer keeps
Sena
online
which stage is the AI infra panel on
14:02
Stage 3 (Level 2, past the coffee bar on the right).
Starts 14:20, so you have 18 minutes.
14:02
anything after it worth staying for
14:03
Same stage at 15:10 there is a session on cost control at scale, which lines up with the integration problem you mentioned earlier.
14:03
Conversations are illustrative reconstructions in the shape our deployments produce. They are not transcripts, and no real attendee is depicted.
Yes, though not the way most organizers first try it. Messaging a registration list from a personal account or the free WhatsApp Business app gets the number banned, usually the week of the event. Doing it properly means a verified sending identity, consent captured before you send, and every pre-event message cleared through Meta review. That is a compliance project with queues you do not control, not a software integration.
The channel works. The reason most organizers hear about it and never ship it is that nobody mentions the compliance part until they are three weeks in.
We're not a neutral guide. We sell this, already working. Every failure on this page is one of ours. We've already paid for them. You wouldn't have to.
Every number below is a count over its base, from a named deployment. Percentages without denominators are why this category has a credibility problem.
Reply rate by how hard the organizer promoted it
113 replies of 123 delivered (CPME31). 65% across the full funnel, including everyone the send never reached.
67 replies of 177 delivered (FOST Singapore), though 119 of 177, or 67%, were read.
Typical response rate, the baseline most organizers already know.
A deployment where the organizer never mentioned the channel to attendees.
Sources: CPME31 and FOST Singapore deployment reports. Survey baseline is the industry figure organizers already compare against.
Swipe the table to see every column
| Channel | Measured | Where it comes from |
|---|---|---|
| WhatsApp, promoted | 92% replied to the template (113 of 123 delivered); 65% funnel-wide | CPME31 Toulouse, opt-in on the registration form plus on-site promotion |
| WhatsApp, lightly promoted | 38% replied (67 of 177 delivered), though 67% were read (119 of 177) | FOST Singapore, content-led event, no heavy organizer push |
| WhatsApp, not promoted | Around 6% engagement | A deployment where the organizer did not mention Sena at all |
| Written survey | 10 to 20% typical response | Industry baseline, the comparison most organizers already know |
| Event app | 20 to 30% of registered attendees typically use it; ~40% for well-run dedicated networking apps | Buyer-stated benchmarks from organizer conversations |
The spread between rows one and three is the whole argument of this page. The channel is not the variable. The promotion is.
Row two is the one to sit with. Two-thirds opened it. One-third replied. Read is not the same as answered, and at a content-led event your message is competing with the programme itself.
Ask any vendor in this category for the same table. If the answer is a single percentage with no event attached and no base underneath it, you are being quoted a best case. The useful question is not what response rate the channel gets. It is what response rate it got at an event that looked like yours, and what the organizer had to do to earn it.
Five things have to be in place before the first message goes out. We do four. You do one: put the opt-in on your registration form.
01
Event messaging cannot run from a personal WhatsApp account or the free Business app. That route ends with the number banned, usually in the week of the event. The real thing needs a verified business identity, a provider relationship and a Meta review queue with no published turnaround. It is the most common reason a first deployment slips. Sena arrives on a number that already cleared it.
02
Every message you send to an attendee who has not written to you first has to be approved by Meta in advance. Anything that reads like marketing comes back rejected, and each rewrite goes to the back of the queue. Two weeks before your event is not enough runway. Ours are already approved.
03
This one is yours. One checkbox on the form your attendees are already filling in. We give you the wording and where to put it, and we cannot put it there for you. Collecting consent afterwards reaches a fraction of the people.
04
Phone numbers are the dirtiest field in any registration export, and the column that records consent is almost never named the same thing twice. Both fail quietly, which means you find out at broadcast time. We reconcile your export against what actually delivers before anything sends.
05
The moment the first message lands you have an inbox open, and attendees use it for everything: which room, what is next, and telling you they cannot come. An unanswered reply is worse than never messaging at all. Sena answers in seconds, from your programme and your floor plan.
A checkbox on the registration form. If you take one thing from this page, take that.
We have watched this one variable move engagement by more than a factor of four, and it beats everything else we can control: the template copy, the send timing, the quality of the agent. At CPME31 the checkbox was on the form and the organizer talked about it on site. 159 of 209 Speed Business participants opted in, 76%. At FOST Singapore the checkbox existed, the event was content-led, and the push was light. 274 of 1,596, or 17%. Same product, same channel, four times the reach.
We write the wording, tell you where it goes, and give you an activation plan for the weeks around it. We cannot put it on your form, and consent collected after registration reaches a fraction of the people. That is the trade: a few minutes of your registration team's time decides most of what you get back.
Building it yourself, budget two to three months before your event date. Most of that is waiting: business verification sits in a Meta queue with no published turnaround, and every template you write goes into a second queue that restarts each time one comes back rejected.
The trap is that none of the waiting looks like work, so it does not get scheduled. Organizers decide on the channel six weeks out, which feels early, and discover in week four that the number cannot send yet. By then the choice is to launch on an unverified number, which risks a ban in your event week, or to drop the channel and tell the sponsors who were promised it.
On a Sena deployment there is no queue, because it already cleared. What we need from you is your attendee export, your programme and sponsor list, and the checkbox on your form. Events have gone live with us in under two weeks. That is not a claim about our software being fast. It is that the slow part was done a year ago, on somebody else's event.
This is a processor question, not a WhatsApp question. Using the channel does not create a compliance problem. Messaging people who never agreed does, and so does being unable to say who touches their data.
Five things have to hold: an explicit opt-in rather than a pre-ticked box, a privacy notice that names the processors, a retention period you actually enforce, an opt-out honoured the first time someone types "stop", and a straight answer ready for the attendee who asks. On a Sena deployment they are already holding, and we publish our own subprocessor list. This is not legal advice, and an EU-facing event should have someone qualified read its setup.
Attendees do ask. At CPME31 one wanted to know in detail how their data had been sourced and whether scraping was involved. That is a fair question and it deserves a real answer, which is a good reason not to improvise the setup three weeks out.
Every one of these cost us real time on a real event. None of them are in a provider's documentation. Each is a week you would spend finding it out.
The worst one, because it does not look like what it is. Inbound messages keep arriving. Every outbound send fails. The error we saw pointed at authentication, so we went after credentials, and none of it helped. We lost that week twice before we recognised it.
A template with more than one placeholder does not fail for one attendee. It fails for all of them, and the error names a parameter count rather than a person. Obvious in testing, catastrophic if you skip it, and testing it properly needs real handsets on more than one country code.
During the event this is invisible, because attendees message constantly. The morning after, the code path that worked all day starts failing, because every window has quietly expired. Anything you send from then on has to be a template, which means it needed writing and approving before the event ended, back when nobody was thinking about it.
Missing country codes, landlines, numbers with no WhatsApp account, plain typos. They all fail at delivery rather than at import. At CPME31 the gap between the 159 people who opted in and the 123 who received a template was almost entirely this. That gap is never zero, and it only shows up if someone reconciles the two lists.
Rejections are common for anything that reads like marketing, and every rewrite goes back into the queue. Two weeks out is not enough runway on a number that has never sent before, which is exactly when most organizers start.
Run several events off one number and moving it can kill the routing for the old one. Attendees keep messaging and nothing answers. Nothing errors, nothing alerts, and you hear about it from an attendee asking why nobody replied.
Open WhatsApp and attendees will use it for everything, mostly not for the thing you built it for. At FOST Singapore, 78% of conversations were navigation: which stage, which room, what is on next. At FOST Paris the channel handled 2,634 attendee questions, each answered in under three seconds.
Volume runs higher than an email inbox and attendees expect an answer in seconds, not hours. A human-staffed desk at a large event needs more people than anyone plans for. And whatever answers has to be reading your actual programme, venue map and exhibitor list. An assistant guessing at a room number does more damage than silence.
Attendees also message to say they cannot make it, to ask for an organizer, to report a problem with the venue. Once the channel exists it becomes the event's front door, so plan for it to be one.
Everything above is a description of a job, not an invitation to do it. On a Sena deployment none of it lands on your team.
The channel is not the point. It is the only place your attendees will reliably answer a question, which makes it the cheapest way to find out why they came. What you do with that answer is the part your sponsors pay for, and it is the reason this page exists rather than a page about messaging.
Your side is the checkbox and the promotion. Ours is the rest of this page. Pricing starts at 3000€ per event.
Yes, and not from a personal account or the free WhatsApp Business app, which gets the number banned. It needs a verified business sending identity, consent captured before you send, and Meta review on every message you start. That is a compliance project with queues you do not control, and it is the part organizers underestimate. Sena runs on a number that already has all of it.
Any message you start outside 24 hours of the attendee's last message has to be a Meta-approved template. Once they reply, a 24-hour window opens in which you can write freely. The window resets with each attendee message and closes silently. That is why sends that worked all through your event start failing the next morning.
Put the checkbox on the registration form and promote it. Placement is the single biggest thing we have measured. At CPME31 the opt-in was on the form and the organizer pushed it on site: 159 of 209 Speed Business participants opted in. At a content-led event without that promotion, opt-in was 274 of 1,596, or 17%. Same product, same channel.
It can be, and it is your responsibility rather than Meta's. You need a lawful basis, which in practice means an explicit opt-in at registration; a privacy notice naming the processors; a retention period you enforce; and an opt-out honoured on the first request. On a Sena deployment those are already in place. Attendees do ask: at CPME31 one wanted to know in detail how their data had been sourced.
It depends almost entirely on promotion, and the honest range is wide. At CPME31, 92% of delivered templates got a reply (113 of 123) and 65% across the full funnel. At FOST Singapore, with lighter promotion, 38% of delivered templates got a reply though 67% were read. Where an organizer did not promote it at all, engagement sat near 6%. Treat any vendor quoting one number without a denominator with suspicion.
For reach, usually yes. There is nothing to install and the app is already open on the attendee's phone. For agenda, maps and session bookmarking, no. An event app is the right tool and WhatsApp does not replace it. The two solve different problems and most events run both.
Two to three months if you are building it yourself, and almost all of that is queue time you cannot compress: business verification at Meta has no published turnaround, and every rejected template restarts a second queue. The common failure is deciding on the channel six weeks out, which feels early, and finding in week four that the number still cannot send. On a Sena deployment the queues are already cleared and events have gone live in under two weeks.
Either. Most events run on a number we provide, because it is already verified and its templates are already approved, which removes the longest lead time in the project. If you want attendees messaging a number you own, that works too, and you should start earlier: a number that has never sent has to clear review before your first send.
Volume is higher and the expected reply time much shorter than an email inbox, so the staffing most organizers plan for is not enough. FOST Paris ran 2,634 attendee questions through the channel, each answered in under three seconds, and at FOST Singapore 78% were navigation questions rather than networking ones. Whatever answers has to be working from your real programme and floor plan. That is the job Sena does.
The anonymized sponsor report from a live 1,306-attendee deployment, in your inbox.
A real, anonymized sponsor report from a live deployment. No newsletter, no sequence.
Stuck on one of the failures above? Ask us and we will tell you what we did, whether or not you buy anything.