How not to lose bookings from Viber, Telegram and other messengers

A passenger writes on Viber. Another gets in touch through Telegram. A third asks a question in Instagram Direct, and a fourth phones the dispatcher. The more communication channels a carrier uses, the more chances there are to sell a ticket. But only on one condition: that no enquiry gets lost between chats, spreadsheets and staff members' personal phones.

To stop losing bookings from Viber, Telegram and other messengers, every enquiry has to be moved into a single system that tracks trips and seats.

The trouble starts when each channel works on its own. A message was read but not acted on. A passenger was promised a seat, but it was never added to the list. Payment was confirmed in one chat while the dispatcher checks it in another. In the worst case the same seat is sold to two people.

Let us look at why bus carriers lose enquiries from messengers, and how to build a process in which every enquiry turns into a booking you control.

Why enquiries from messengers get lost

Viber, Telegram, WhatsApp, Facebook Messenger and Instagram Direct are convenient for conversation, but on their own they do not replace a bus ticket booking system. A passenger's message is not automatically linked to a particular trip, a seat in the vehicle, a payment or a passenger list.

While the dispatcher transfers information by hand, several typical risks appear.

The message was read but not acted on

A read receipt does not mean a seat has already been booked for the passenger. The member of staff may have opened the message, been distracted by a call and never returned to the conversation. To colleagues, the enquiry will already look handled.

The enquiry stayed in a private chat

If passengers write to dispatchers' personal numbers, the sales history effectively stays on one person's phone. When they are off shift, ill or leave the company, the team cannot see the full picture.

There is no clear status

From the correspondence it is not always obvious what stage the customer is at:

• only asked about the price;
• is choosing a trip;
• is waiting for a reply;
• asked to reserve a seat;
• received the payment details;
• paid for the ticket;
• cancelled the journey.

As a result, some passengers are messaged twice while others are forgotten.

Seats are checked in different lists

One dispatcher looks at an Excel file, a second at a photo of the seat map, a third at a list in a chat. If changes are not synchronised immediately, the same seat can be offered to several passengers.

Data is transferred by hand

The name, phone number, date, destination, pick-up point, seat number and amount paid all have to be copied from the message into a spreadsheet or another program. Even a careful member of staff can make a mistake in the date, the phone number or the boarding city.

The owner cannot see the losses

Without a single register the manager does not know:

• how many enquiries are waiting for a reply;
• how quickly dispatchers respond;
• how many enquiries turned into bookings;
• at what stage passengers drop out;
• which channel brings in more sales.

A lost message never reaches a report, although for the business it is a lost ticket.

The main rule: a message is not yet a booking

A carrier needs to separate two things:

• an enquiry — a passenger wrote or called;
• a booking — a record has been created in the system, a trip and a seat chosen, the passenger added and the payment status set.

While the arrangement exists only in a chat, the team cannot reliably control the sale.

The correct process looks like this:

Passenger enquiry
        ↓
Bot or assigned operator
        ↓
Current trip and available seats
        ↓
Booking created
        ↓
Payment or reservation control
        ↓
Electronic ticket and notification to the passenger

The messenger remains a convenient channel for conversation, while the source of current information becomes a single booking system.

One chat for all channels

In BUSPORTAL, passenger enquiries from connected channels can be brought together in one multichannel chat:

• Telegram;
• Viber;
• WhatsApp;
• Facebook Messenger;
• Instagram Direct.

The dispatcher does not have to keep switching between apps. They see the conversations in one workspace, can continue the exchange and move straight to creating a booking on the right trip.

If the channel supports a bot scenario, the passenger can find a trip, look through the available options and start buying a ticket on their own. When human help is needed, the conversation is handed to an operator. The passenger does not have to repeat their question from the beginning, and the member of staff sees the context of the enquiry.

The bot must not create a separate list of seats. It works with the same trips, fares and availability as the carrier's website and admin panel.

Seven rules that protect a booking

1. Use the company's official channels

Customer enquiries should arrive through channels the carrier controls: corporate messenger accounts, an official bot, the website, a work email address or a contact number.

A member of staff's personal phone must not be the only place where an arrangement with a passenger is kept.

2. Assign someone responsible

An enquiry must not sit in a state of "someone will reply". For every enquiry you need:

• a responsible member of staff;
• the time it was received;
• the current status;
• the next action.

If the conversation is handed to another dispatcher, the new owner must be able to see its history.

3. Create the booking during the conversation

As soon as the passenger has settled on a trip, the dispatcher creates the booking in the system. There is no point writing the details on paper first, transferring them into Excel at the end of the shift, and then compiling a list for the driver all over again.

The fewer intermediate steps, the lower the risk of error.

4. Use one current seat map

The website, the bot, the dispatcher and the driver must all work from the same seat availability. When a seat is reserved, sold or closed by the carrier, its state is immediately reflected in the other connected channels. This helps avoid selling the same seat twice.

It protects against the situation where the website sells a seat the dispatcher has already promised to a passenger in a chat.

5. Limit how long an unpaid reservation is held

If seats are held without a limit, a trip can look full even though some passengers never completed payment.

For online orders, BUSPORTAL can apply a limited reservation window. For example, a seat is held for 15 minutes while the passenger completes payment. Once the window closes, the unpaid seat returns to sale.

For bookings created by a dispatcher, the carrier can apply different rules according to the payment method and its own sales process.

6. Send the passenger a confirmation

After the booking is made, the passenger should receive a clear result:

• the route and the date;
• the time and place of boarding;
• the seat number;
• the amount and payment status;
• the electronic ticket;
• the carrier's contact details.

Notifications can be sent through the connected channels, including email, Telegram, Viber or SMS. This reduces the number of repeat questions and disputes about what was agreed in the chat.

7. Hand over the shift by a list, not from memory

At the end of a shift you need to check:

• enquiries with no reply;
• unfinished bookings;
• unpaid reservations;
• records without contact details;
• passengers who were not sent a confirmation;
• trip changes that still need to be announced.

The next dispatcher should see these tasks without reading through all of the previous shift's chats.

What changes once the channels are brought together

What the carrier gets

A single seat availability

The dispatcher sees the same free seats as the passenger on the website or in the bot. The system also accounts for seats sold on different sections of the route.

Where needed, the carrier can close individual seats to online sale or create a reservation for regular customers, groups or partners. Such seats remain available only to authorised staff.

An up-to-date passenger list

A confirmed booking goes into the trip's list. After every change there is no need to send the driver a new Excel file or a photo of the list.

Control over payments

In the booking you can see the price, the currency, the amount paid, the balance, the payment method, refunds and additional services. Staff do not have to hunt for a payment screenshot in the message history.

An electronic ticket and useful information

The passenger receives an electronic ticket with a QR code. The ticket can be added to Apple Wallet or Google Wallet.

If GPS monitoring is active for the trip, the passenger can open a public map, see where the bus currently is and the estimated time of arrival.

Managing sales by channel

The carrier can manage sales availability separately. For example, stop online booking before departure while leaving an administrator able to issue a ticket.

A history of changes

The system shows who created or changed a booking, when it happened and which details were amended. The team does not have to work out who deleted a row or changed the colour of a cell in a spreadsheet.

More about working with passengers, payments and repeat sales — on the page CRM for bus operators.

If enquiries still arrive by voice or on paper

Moving to a single system does not mean every member of staff and every partner will change their habits at once.

BUSPORTAL can help bring text notes, photographs of notebook pages and voice messages into the working process. AI recognises the details, finds the likely trip and prepares the booking for checking.

The operator always checks the result before confirming. AI reduces manual transfer, but it must not quietly create a ticket without a member of staff's oversight.

How to tell that a carrier already needs automation

A single system is needed if:

• enquiries arrive through at least two different channels;
• several dispatchers work on the same trip;
• seats are controlled in Excel or in chats;
• staff regularly ask again whether a passenger has paid;
• the driver is sent the list as a file or a photograph;
• customers complain about slow replies;
• after a trip change every passenger has to be tracked down by hand;
• the owner cannot quickly work out how many enquiries were lost.

The longer a company puts off automation, the more unofficial spreadsheets and manual rules pile up around every trip.

The result at VD-EXPRESS

After BUSPORTAL was introduced at VD-EXPRESS, bookings, seats, passengers, payments, transfers, drivers and vehicles all work in a shared process.

In the system:

• over 600 bookings are processed each month;
• 2 active routes are running;
• 25% of tickets are sold online;
• 8 transfer service areas are configured;
• 11 vehicles are connected.

More detail: the VD-EXPRESS automation case study.

How to move to one system without stopping sales

1. List every source of enquiries

Write down the website, the phone, email, messengers, agents and partners. You need to see the full path of an enquiry before you change it.

2. Decide on a single place where bookings are created

Agree with the team: a message in a chat is not a booking until the passenger has been entered into the system.

3. Set up routes, seats and fares

Dispatchers must work with current trips and a real seat map, not with arbitrary notes.

4. Connect the channels gradually

Start with the channels that bring in the most enquiries. Test the working process, train the team, and then connect the next ones.

5. Set up the shift handover

The next dispatcher should immediately see unhandled enquiries, bookings, reservations and payments.

6. Measure the result

Keep track of:

• the number of enquiries;
• bookings created;
• tickets paid for;
• expired reservations;
• the speed of the first reply;
• the share of online sales;
• the reasons orders were not completed.

Frequently asked questions

How do you avoid losing bookings from Viber and Telegram?

Do not leave the arrangement only in the chat. Once the trip has been chosen, create a booking in a single system with the current seat, the payment status and a responsible member of staff.

Can different messengers be brought into one chat?

Yes. BUSPORTAL brings enquiries from connected channels, including Telegram, Viber, WhatsApp, Facebook Messenger and Instagram Direct, into one operator workspace.

Can a passenger book a ticket through a bot?

Yes. In connected channels a bot can help find a trip and start a booking. If the passenger needs a person, the conversation is handed to an operator.

What if a passenger does not want to use a bot?

The dispatcher creates the booking during the phone call or the exchange of messages. For the passenger the way of getting in touch stays familiar, but the details end up in a single system.

How do you avoid selling one seat to two passengers?

All connected channels must use the same seat map. When a seat is reserved, sold or closed by the carrier, its status is taken into account for other sellers and passengers.

Can some seats be kept for the administrator only?

Yes. The carrier can close individual seats to online sale or create a reservation for groups, partners and regular customers. Such seats are available only to authorised staff.

Does the passenger get a confirmation?

After the booking is made, an electronic ticket and journey information can be sent through the connected channels: email, Telegram, Viber or SMS.

Do not lose sales between chats

The problem is not that passengers write in different messengers. The problem arises when each messenger turns into a separate system of record.

BUSPORTAL leaves the passenger a convenient way to get in touch, and gives the carrier a shared process for conversations, routes, seats, bookings, payments and tickets.

See BUSPORTAL in action

We will show how to organise enquiries from messengers, the website and the phone using your own routes as the example.