How a South African online ticketing company used WhatsApp to connect event discovery, ticket ordering, support and ticket delivery.
You find an event you want to attend.
You have a question about the date. Then another about ticket categories. You buy the tickets, look for the confirmation, search your email for the PDF, and later wonder where you saved it.
Then the venue changes the start time.
Suddenly, buying a ticket feels less like booking a night out and more like managing a small project.
An online ticketing company in South Africa took a different approach by bringing more of that journey into WhatsApp.
The result was not simply a chatbot answering questions. WhatsApp became a connected route through event discovery, ticket ordering, customer support, ticket delivery and event communication.
Key points
- Customers can move from event questions to ticket selection in one familiar channel.
- Guided conversations can make ticket ordering easier to follow.
- PDF tickets can be delivered back through the same conversation.
- Event reminders and changes can stay connected to the original purchase.
- Automation can handle predictable questions while people remain available for problems that need investigation.
- The real value comes from connecting WhatsApp to the ticketing process behind it.
Why does buying a ticket still involve so many steps?
Because ticketing has several jobs to do at once.
The customer wants to discover an event, understand what is available, make a purchase and get their ticket.
The business needs to handle availability, payment, customer questions, delivery, reminders, changes and support.
Those jobs often live in different places.
A customer might discover an event on social media, click through to a website, ask a question through email, complete payment somewhere else and receive the ticket in an inbox they will have to search again later.
Each individual step may work perfectly well.
The customer journey can still feel disjointed.
The ticketing provider in this case wanted to bring more of those conversations together, using WhatsApp as a familiar customer-facing channel.
What can WhatsApp actually do for ticketing?
More than send a confirmation message.
The WhatsApp journey supported customer questions about events and existing bookings, while also guiding customers through ticket ordering.
A customer could move through steps such as:
- Choosing an event
- Viewing available dates or categories
- Selecting the number of tickets
- Providing attendee or contact information
- Confirming the order before payment
That changes the experience from “here is a website, good luck” to something closer to guided assistance.
The customer still makes the decisions. The journey simply makes the next decision clearer.
That distinction is useful. Automation should not make customers feel like they have accidentally entered an escape room.
It should help them get somewhere.
What happens after the customer pays?
This is where many digital journeys quietly fall apart.
The customer has completed the important bit, but now they need the ticket.
In this case, purchased tickets could be delivered as PDF documents through WhatsApp.
That keeps ticket access close to the purchase conversation. The customer can return to the chat when they need the document rather than trying to remember which email contained the attachment.
The payment process itself still needs to use the appropriate secure payment route for the ticketing platform, integration and market.
The important point is continuity.
The customer should not have to mentally stitch together the purchase, confirmation and ticket retrieval processes.
What happens when the event changes?
Events have a habit of refusing to stay exactly as planned. It happens.
Start times change. Venues change. Schedules move. Customers need updated information.
WhatsApp can give the ticketing company a direct route to communicate those changes.
Messages can include the event date and start time, venue and access information, ticket retrieval guidance, schedule changes and important event-day notices.
That is useful because the communication is tied to something the customer has already done: they bought a ticket.
The message therefore has a reason to exist.
It is not another generic broadcast competing for attention.
Can WhatsApp help customers discover events too?
Yes, and this is where rich media becomes useful.
An events business has something that a plain text notification does not: a product people want to see.
Images and video can help customers discover upcoming events, deals and discounts before they have decided what they want to attend.
That makes WhatsApp more than a support channel.
It can become part of the discovery journey as well.
The same principle applies to newer WhatsApp formats such as Media Card Carousels, where a business can present a small number of relevant options rather than sending customers to search through an entire catalogue. Cellfind’s recent work on WhatsApp Carousels makes the same point: more options are not automatically more useful. The customer needs enough information to make the next decision.
See how Cellfind uses WhatsApp Carousels to simplify customer choice.
Cellfind’s WhatsApp Business solution
What should be automated?
The easy stuff.
“How do I get my ticket?”
“What time does the event start?”
“Where is the venue?”
“What events are coming up?”
Those questions are predictable enough for automation.
Cellfind Flow Builder can be used to automate common questions and guide customers through predictable tasks.
But not everything belongs in a bot.
A failed payment may need investigation. A refund may need a person. A cancelled event can involve a customer who is understandably unhappy. A missing ticket is not the ideal moment to make someone navigate another six-button menu.
The better model is simple:
Automate the predictable. Keep people available for the complicated.
Cellfind’s work on moving businesses from rigid chatbots towards more responsive “Choice-Bots” follows the same principle: the journey should respond to what the customer is trying to accomplish rather than forcing every person through the same menu.
From Chatbots to “Choice-Bots”
What needs to sit behind the WhatsApp conversation?
Quite a lot.
The customer sees a chat.
Behind it, the business needs the information and processes that make the chat useful.
That can include:
- Event availability
- Ticket categories
- Order information
- Customer details
- Payment status
- Ticket records
- Event updates
- Customer support processes
This is why a WhatsApp chatbot on its own is not the whole solution.
If the chatbot cannot access the information the customer needs, it can only apologise very efficiently.
A connected WhatsApp journey can use the relevant business systems and processes to provide useful answers, collect information and route exceptions to the right person.
Cellfind’s WhatsApp Business offering is designed around that broader model, connecting messaging with automation, customer support and business systems.
Cellfind WhatsApp Business API
What about ticket security and personal information?
Tickets and booking information can contain personal details, so convenience cannot be the only consideration.
The journey needs appropriate identity checks, controlled access and responsible handling of customer information, particularly when customers request replacement tickets or access to booking information.
The same applies to event reminders and promotional communication.
Businesses need to consider customer opt-in choices, WhatsApp template requirements and South African privacy obligations when designing the journey. The Information Regulator is the official South African authority responsible for monitoring and enforcing compliance with POPIA.
Information Regulator South Africa
The technology should make the journey easier without making the underlying controls disappear.
What should ticketing companies measure?
Not just how many messages were sent.
A busy WhatsApp number can look impressive while customers are still abandoning the purchase halfway through.
More useful measures include:
- Questions resolved through self-service
- Ticket-order completion
- Drop-off at different stages
- Live-agent handover
- Failed payment journeys
- Ticket retrieval
- Customer support queries after purchase
- Event update engagement
- Customer satisfaction
The point is to find where customers are getting stuck.
If people regularly start an order but do not finish it, the problem may not be the number of WhatsApp messages. The payment step, availability information or ordering process may need attention.
The conversation gives you another way to see where the journey is working — and where it isn’t.
Where to start
Ticketing is a good WhatsApp use case because the customer journey already has recognisable stages.
Discover the event.
Choose the option.
Buy the ticket.
Get the ticket.
Prepare for the event.
Deal with whatever happens next.
Start by mapping those stages and the questions customers ask at each one.
Then identify which questions are predictable enough to automate, which actions need integration with the ticketing platform, and where a person needs to take over.
The WhatsApp conversation is the visible part.
The real work is connecting that conversation to the event data, purchase process, ticket records and support team behind it.
In this case, Cellfind helped an online ticketing company create a more connected route from event enquiry to ticket access and ongoing event communication.
The lesson is straightforward: customers do not really want a WhatsApp chatbot.
They want to buy the ticket, get the ticket and know what happens next.
WhatsApp simply gives businesses a better place to make that happen.
Talk to Cellfind about building a connected WhatsApp journey for your ticketing or events business.
