Guest Communication Tools That Work With Bokun: WhatsApp, Email and Phone in One Inbox

A guest books a walking tour through your Bókun checkout at 9 p.m. Six minutes later she sends a WhatsApp message asking whether the meeting point is the cathedral or the square behind it. At 9.40 p.m. her partner calls the mobile number from the confirmation email, because nobody replied. The next morning an email lands in a different mailbox asking to move the booking to Thursday.

One guest. One booking. Three channels, three places where the conversation is stored, and no single view of what was promised. That is why the question operators ask about guest communication tools that work with Bókun is rarely "which booking engine should I buy." Bookings are under control. Messages are not.

Why Guest Communication Breaks After the Booking

Booking engines are built to sell: availability, checkout, payments, OTA channels. The conversation that follows the sale was never their core job, so it drifts into whatever app the guest happens to use. And the number of channels keeps growing. OTAs reached 37% of experience bookings in 2025, up from about a third a year earlier (Arival Global Operator Landscape, 4th Edition, n=5,664). Every new channel is another place a guest can write from about the same booking.

Plenty of operators still run that part by hand. In Arival's March 2026 study of multi-day operators, more than one in five managed bookings without any system at all (Arival, State of Multi-Day Tours, 2nd Edition). If the bookings live in a spreadsheet, the conversations about them live in three apps.

Here is the arithmetic, using our own assumptions rather than a study, so adjust the inputs to your operation. Take 2,000 bookings a year. Assume one guest in four asks at least one question before the tour: 500 conversations. Assume each one costs four minutes of hunting across apps to find the booking and what was already promised. That is about 33 hours a year spent searching rather than answering.

The bigger cost is not the hours. It is the three failures that split channels create:

• The lost promise. A guide offers a hotel pickup over WhatsApp. The office confirms the standard meeting point by email. Both are true in their own thread, and neither is visible to the other.
• The unanswered call. The phone rings in a guide's pocket while she is talking to twelve people. Later nobody knows who called, about which booking, or what they wanted.
• The double booking. A reschedule agreed in a message never reaches the booking engine, so the seat stays sold twice.

None of these are exotic. They are the daily texture of the post-booking operations gap: the booking engine did its job, and then the work moved into apps that know nothing about tours.

One Inbox: WhatsApp, Email and Phone in a Single Guest Thread

The fix is not another messaging app. It is one thread per guest, with the booking attached to it. That is what the Communications & AI module in automate.travel does. WhatsApp, email and phone calls land in the same inbox, tied to the guest and the booking rather than to whichever device received them.

• Caller recognition. When the phone rings, the person answering sees who is calling and which booking it concerns. Nobody asks a guest to spell her booking reference while she stands in a square.
• Calls in writing. For calls that are recorded and processed, the transcript is available in the communication thread, so the next person can review what was said.
• One history, many channels. Whoever opens the thread at 7 a.m. reads the same context the office saw at 9 p.m., including what came in by email.

Where AI Helps, and Where a Person Presses Send

Bókun is adding AI on the booking side. Its AI Booking Agent, currently in beta, turns text, guest messages and attachments into draft bookings that a person approves (Bókun documentation). That makes the conversation layer more important, not less. The message still has to reach the right person, attached to the right booking, before anything can be drafted from it.

In automate.travel the AI works on the same principle. It reads the booking and the whole conversation and drafts a reply in the guest's language. It does not send it. A person reviews the draft and presses send, because whoever sends a message owns the promise in it.

For the messages that should never depend on someone remembering, rules beat AI. WhatsApp templates are reviewed by Meta when created or edited. Approved, configured messages such as confirmations and reminders can then go out on a schedule in your company's time zone. Review requests require a permitted contact method and booking channel; keep OTA guests within the marketplace's rules. If you want the full map of which tasks to automate and which to keep human, it is in AI for Tour Operators: What to Automate in 2026.

How This Sits on Top of Bókun

The boundary matters, so here it is precisely. automate.travel does not replace your booking engine. Checkout and OTA channel management stay in Bókun. Bókun bookings sync into automate.travel, so every guest thread knows which booking it belongs to, and your checkout does not change. Guests notice one thing: faster answers.

The guest side of that table deserves a picture. Instead of a confirmation email, a reminder and a follow-up scattered across a week, the guest gets one link that changes with the trip: before the tour it shows the meeting point and what to bring, on the day it shows the plan, and after the tour it can offer a review step when configured. That does not authorize a separate message to an OTA guest.

For the longer version of the split between booking engine and operations layer, see Beyond the Booking Engine and our Bókun and automate.travel comparison.

Seven Checks for Choosing a Guest Communication Tool

Run these on any tool in this category, ours included. They are questions with yes or no answers.

1. Does it attach messages to a booking, or only to a contact? A tool that stores threads by phone number loses the guest who books twice under two numbers.
2. Does an inbound call show the booking before you say hello? If not, your team still asks guests to identify themselves, and the tool has not solved the phone.
3. Is the voice channel written down? Anything agreed by phone has to end up as text in the guest thread. Manual notes stop happening in week three of high season.
4. Who owns the WhatsApp number? Ask what happens to your number and your history if you leave. Easy to skip, expensive to learn late.
5. Does AI send on its own? Drafts save time. Unreviewed sends make promises nobody approved. Know which one you are buying.
6. Does it require moving away from Bókun? If yes, you are not buying a communication tool, you are buying a replatform. Different project, different risks.
7. What happens on day one with your existing bookings? History should come in from Bókun without retyping. Anything heavier needs a reason.

Fast Answers Are Now Part of How Guests Find You

There is a second reason to fix this that did not exist two years ago. Travelers increasingly start with an assistant instead of a list. ABTA found that 14% of UK adults used AI for holiday inspiration in 2026, up from 8% a year earlier (ABTA Holiday Habits, October 2026). An assistant can send you a guest. Your response speed and your review flow decide whether she books and whether she recommends you afterwards, and both live in the inbox. The acquisition side of that loop is in How to Get Your Tours Recommended by ChatGPT.

What This Looks Like on Your Own Data

If your bookings are in Bókun and your guest conversations are spread across a WhatsApp account, a shared mailbox and a mobile phone, judge any tool on three numbers from your own operation: inbound threads per booking, time to first reply, and how often a promise made by voice reaches the person running the tour.

Book a demo and we will walk through one inbox with your channels on demo data, without touching your Bókun account.

Frequently Asked Questions