Industry

WhatsApp for travel agents and tour operators

Endelir keeps a trip's whole conversation on one WhatsApp number — the enquiry, itinerary follow-up, booking confirmation, traveller details, documents and trip updates — owned by one consultant and visible to the team. A trip is sold in pieces — a question one evening, dates the next morning, a costing, two revisions, a deposit, then documents and a departure reminder weeks later. Endelir keeps that whole run of messages on one business number, with the details saved as data rather than scrolled back to. Your consultants share the number; the traveller only ever sees your agency.

Updated 29 September 2026 · Written by the Endelir team

Start free for 14 days Talk to us

A sea-facing homestay room made up for arrival, towels folded into swans on the bed

Live

Message to inbox in under a second.

The trip lives on one consultant's phone

Travel is sold on personal handsets. The destination, the dates, the ages of the children, the budget that was never written down, the price that was quoted on a Tuesday — all of it sits in a chat only one person can open. When that person is on leave, out with a group, or has left the agency, the trip stalls and the traveller starts again with someone who knows nothing about them.

The gap makes it worse. Weeks pass between the first question and departure, so follow-up depends on somebody remembering. Vouchers and tickets go by email and are not opened. Then the traveller lands, the transfer is not where it should be, and they write to the one number they have, which is the consultant who is asleep.

One number from the first question to the trip report

Endelir puts every enquiry on your business number into a shared inbox that your whole team signs into, each person with their own login. A chat flow asks the things no costing can be built without — destination, travel dates, how many are travelling, departure city — and writes each answer onto the contact record, so the enquiry reaches a consultant with the facts attached rather than as a paragraph someone has to read twice. The flow can hand it to the right team by the answer, so a Europe enquiry and a domestic weekend do not sit in the same queue.

After that the thread carries the trip. Itineraries, vouchers and tickets go as documents in the same conversation. Timed follow-up chases a costing that went quiet without anyone setting a reminder. Departure messages go out on an approved template because the traveller has usually not written that week. What Endelir does not do is decide availability: it holds no calendar and no inventory, so seats, rooms and departure dates are confirmed in your own system and the conversation carries the answer.

How the traveller journey runs

1 The enquiry arrives Someone writes to your business number from an ad, your website, or the QR code on a brochure. If it came from a click-to-WhatsApp ad, the ad, its headline and the source are recorded against that message, so you can see which campaign produced the enquiry.
2 The basics are collected A flow asks destination, dates, number of travellers, departure city and roughly what kind of trip they want. Every answer is saved to a field on the contact record instead of staying loose in the chat.
3 It reaches a consultant The conversation is assigned — by the destination the flow captured, or by hand — and the ownership is visible in the inbox, so two people do not quote the same traveller two different prices.
4 The proposal and its revisions stay together The itinerary goes as a document in the thread. Changes to it are asked for and answered in the same place, so the newest costing is the one furthest down the conversation rather than one of six files in an inbox.
5 The booking is made in your own system Endelir does not hold availability. Your team books it where you book it now, or a flow step calls your system and brings the answer back. Once it exists there, the confirmation goes out on the thread, with your own payment link for the deposit.
6 Traveller details and documents Name spellings as they appear on the passport, meal preferences, insurance details — asked in the conversation and saved on the record. Vouchers, tickets and transfer details go back the same way, where the traveller can find them on the day.
7 Departure, the trip, and afterwards A departure reminder goes out a few days before, on an approved template. During the trip a message from the traveller opens the service window, so your team can answer freely. After they return, a short feedback flow asks how it went.

What this looks like in practice

A tour operator sells small-group trips to three regions and has four consultants. The ads produce enquiries all day, most of them saying little more than the name of a country and the word "cost". Before Endelir, whoever saw the notification first replied, and the follow-up depended on that person's memory.

Now the enquiry lands in one inbox. A flow asks the month, the number of travellers and the departure city, saves the answers, and hands the conversation to the consultant who sells that region. A costing with no reply after three days triggers a follow-up on an approved template. When the booking is confirmed in the operator's own system, the voucher and the flight details go into the same thread, and a week after the group returns the feedback questions arrive on it too.

What happens when the traveller replies

They ask for a change A different hotel, one night fewer, a child added. The request comes back on the thread the costing went out on, so nobody rebuilds the context first.

They accept the costing Your team books it in your own system, then confirms in the conversation. The confirmation carries the facts of the trip, not an offer.

They pay the deposit Your own payment link goes into the chat. Endelir does not take the money and is not told when it arrives, so mark the booking paid when your payment provider confirms it, not when the link is sent.

They send their passports Photographs and PDFs sent by the traveller arrive in the conversation and stay with that contact, so the person preparing the file is not chasing an email.

They go quiet A timed follow-up goes out on its own. Once 24 hours have passed since their last message, that follow-up is an approved template rather than a free-form line.

They write from the airport Their message opens the service window and your team answers freely. Out of hours, a keyword auto-reply can say when someone will pick it up; anything it does not recognise waits for a person rather than being guessed at.

Your systems hear about it A flow step can call your own URL, and your booking system can push updates in through the API, so the record and the conversation agree.

Works across travel businesses

Tour operators Fixed departures sold over weeks, with the costing, the revisions and the joining instructions on one thread.

Retail travel agencies Counter staff share one number, so an enquiry taken on Monday is picked up on Wednesday by whoever is in.

Destination management companies Ground arrangements confirmed with the agent abroad and the traveller separately, from the same workspace.

Pilgrimage and group departures Large groups where the same questions come every day, answered once by a flow and escalated when they are not routine.

Adventure and activity operators Fitness, experience and equipment sizes asked before the trip and saved against the traveller.

Honeymoon and special-occasion travel Long, slow conversations with several revisions, kept in one place instead of a consultant's personal chat.

Corporate travel desks Requests from staff at client companies handled on a shared number with a named owner for each one.

Transfers, car hire and visa services Pick-up details, documents and collection times sent where the traveller will actually read them.

What to know before you set it up

While the traveller is writing to you, you can answer freely — the service window stays open for 24 hours after their last message. Starting a conversation yourself, or answering after the window has closed, uses a message template Meta has approved in advance. Keep the two kinds of message apart: "your flight now departs at 06:40 and pick-up moves to 03:30" is a utility message about a real booking, while "our October Kerala departure has three seats left" is marketing, needs a marketing template, and goes only to travellers who have opted in. Past travellers are a good list precisely because they chose you; that is not the same as having their permission to advertise to them, so record it.

Be clear about what Endelir is not. It holds no calendar and no inventory, so it cannot tell you whether a seat, a room or a departure has space — that answer comes from your own system, either from a person looking or from a flow step that calls it. It issues no tickets and creates no vouchers; it sends the documents your system produced. It does not take payments, so the payment link is your own. And since passport details and traveller information end up on the contact record, ask for what the booking needs and no more.

What to measure

Enquiries received, and which ad or page produced them
How long a new enquiry waits for its first reply
How many enquiries reach a costing
How many costings become bookings
Follow-ups sent, and how many are answered
Traveller details collected before departure
Feedback replies after the trip
Repeat bookings from travellers who went before

Use cases Lead qualification Ask each enquiry the questions your sales team needs answered, save the replies onto the contact record, and r… Use cases Booking confirmations Take reservation enquiries on WhatsApp, collect the details a booking needs, and send the confirmation, the re… Use cases Pre-arrival check-in Ask guests for arrival time, party size and transfer needs before they travel, save the answers on their recor… Use cases Invoices and documents Send invoices, receipts, vouchers and tickets to the same WhatsApp thread as the transaction. Your system make… Use cases Customer feedback Ask for feedback after a completed order, stay or appointment, save each answer onto the contact record, and s… Use cases Win-back campaigns Bring quiet customers back on WhatsApp. Build a win-back audience from people who opted in, send an approved M…

Questions people ask

Can travellers book a trip through WhatsApp?

They can start one, and for most agencies that is the useful part. A chat flow collects the destination, the dates, the number of travellers and the departure city, saves each answer onto the contact record, and hands the enquiry to the consultant who sells that region. What Endelir cannot do is tell you whether the seats or rooms exist. It holds no calendar and no inventory of its own. Availability is checked in your own reservation system, by a person or by a flow step that calls it, and the confirmation then goes out on the same thread the enquiry came in on.

How do we send tickets, vouchers and visa documents?

As documents in the conversation. Endelir sends PDFs and images on your business number, so a voucher, an e-ticket, an insurance certificate or a set of joining instructions lands in the same thread as the rest of the trip, where the traveller can find it at the airport without searching an email account. Endelir does not create those files — it carries the ones your booking system or your team produced. Documents the traveller sends you, such as passport pages, arrive the same way and stay attached to their contact record.

Can we keep in touch while the traveller is abroad?

Yes, and this is where one number earns its place. A traveller with no local SIM can still reach you over hotel wifi, and when they message you the service window opens, so your team answers freely for the next 24 hours. Whoever is on duty sees the whole trip — the itinerary, the transfer details, what was agreed six weeks ago — rather than one consultant's private chat. If you need to reach them first, for a schedule change or a cancelled transfer, that goes out on an approved template.

Can we message past travellers about new departures?

Only those who have opted in, and Endelir enforces it rather than trusting the list. A marketing campaign is refused for a contact with no recorded consent, and an opt-out is honoured from then on. Somebody having travelled with you before is not by itself permission to advertise to them, so collect and record consent — at booking, on your own booking form, or in the conversation. Campaigns go to contact groups you build, on an approved marketing template, and replies come back into the shared inbox like any other message.

Does it connect to our booking system or CRM?

Through your own connection rather than a packaged one. Endelir has a REST API and webhooks, so your reservation system can push a confirmation, a schedule change or a document into the right conversation, and a step inside a chat flow can call a URL of yours as the traveller answers — which is how a qualified enquiry reaches your CRM as it happens. There is no ready-made connector for the travel booking platforms, so this part is work your developer or ours does once.

Can several consultants work from the same number?

Yes. The number is connected once and each consultant signs in as themselves, so there is no shared password and no handset being passed around. Each conversation can be assigned to a person and the ownership shows in the inbox before anyone starts typing. A trip can be reassigned when someone is on leave, and the history goes with it. When someone leaves the agency you remove their login, and the conversations stay with the business. How many people can sign in depends on your plan.

What happens to enquiries that arrive at night?

They wait in the inbox rather than in one person's notifications, and they are still there in the morning with their place in the queue visible. A keyword auto-reply can acknowledge the message and say when someone will answer, and a chat flow can collect the destination and dates in the meantime, so the consultant starts the day with the enquiry already half-worked. Endelir does not improvise answers about prices or availability out of hours; anything a flow does not cover is left for a person.

Keep the traveller conversation connected from enquiry to return.

Put your enquiries, your consultants and your trip documents on one business number. We set the number up with you on a call, and go through where your booking system needs to talk to it.