How a hop-on hop-off city tour operator automated ticket, schedule, and refund support

• Industry: Mobility and Tour Operators

• Format: open-top double decker city tour, day and night departures, fixed-interval schedule across a large stop network

• Channels: web, WhatsApp

• Scope: ticket and booking questions, schedule and stop information, refunds, and lost-item reports

The operator

An open-top double decker city tour operator connecting dozens of major sites across a large network of designated stops, running continuous day and night departures on a fixed schedule. Its customers are almost entirely tourists, often unfamiliar with the city, frequently asking questions in a language other than the operator's own, and usually asking them in the moment, standing at a stop or mid-tour, not from a desk.

The challenge

A hop-on hop-off operator's support load is concentrated around a small set of high-frequency, time-sensitive questions. Is my ticket still valid for tomorrow. Where is the nearest stop from here. How long until the next bus. I missed my stop, what do I do. I want to cancel and get a refund. I left something on the bus. Each question is simple in isolation, but the volume is constant, the customers asking are tourists on a tight schedule who cannot wait long for an answer, and a meaningful share of them are not asking in the operator's primary language.

Refunds and cancellations added a second layer of pressure. A missed departure due to weather or a mechanical issue meant a wave of customers needing rebooking or a refund at the same time, often while still standing at a stop, with no patience for a slow manual process.

Why AutomatiCworX

The operator deployed AutomatiCworX to handle the recurring volume directly on web and WhatsApp, the channels tourists were already using to find and book the tour in the first place. The system answers ticket and schedule questions instantly, verifies eligibility and processes refunds and rebookings within the operator's own rules, and answers in whatever language the customer is using, without routing them to a translated menu or a callback.

Anything genuinely unusual, a safety concern, a dispute over a charge, escalates to the operator's own team with the conversation and relevant booking details attached, so nothing time-sensitive is ever left waiting on a person who isn't available yet.

AutomatiCworX in action

A tourist messages asking whether their ticket purchased yesterday is still valid for a tour today. The system checks the ticket type and validity window and answers immediately, in the language the tourist used to ask.

A customer whose tour was cancelled due to weather asks for a refund. The system verifies the cancelled departure against the booking, processes the refund to the original payment method, and confirms it in the same conversation.

A tourist realises they left a bag on the bus after getting off at a stop. The system opens a lost-item report, logs the stop and approximate time, and relays it to the operator's team for follow-up, keeping the tourist updated rather than leaving them with no path forward.

The results

Tourists get ticket, schedule, and refund questions answered instantly, in their own language, at the moment they're standing at a stop needing the answer, rather than waiting on a call centre or a language barrier. The operator's own team is freed to handle genuine exceptions, safety issues, disputes, and lost-item recovery, instead of fielding the same handful of routine questions on repeat.

What is next

The operator is extending AutomatiCworX to proactive delay notifications when a departure is running behind schedule, so tourists know before they ask.

See what AutomatiCworX can resolve for your customers.