Itinerary and inclusions, from the trip page
Day-by-day detail, what the price covers and what it does not, walking grade, group size and age range — from the pages you publish, at the hour people actually research.
Travellers compare at night, three operators' tabs open and a list of things the trip page did not settle. The chat window on your own site has read what you publish — the itinerary day by day, what the price covers and what it leaves out, the walking grade, group size and age range, departures and kit lists — and answers from that, 24/7, in the traveller's own language. A supplement or a deposit is quoted only where your page states one. Refunds and financial protection go to your office.
Fig. 01.A · Tour operators
Fig. 02.A · pain quotesThey arrive long after the office has gone dark, with the tour leader somewhere without signal. What does the free afternoon in the medina actually involve. Does the price take in transfers and entrance fees, or only the coach. How fit is fit enough for a grade you have called moderate. Is there a single supplement, and can sharing avoid it. All of it is on the trip page already; it was not where they looked, so they write — and the same message goes to the operators in the other tabs.
Day-by-day detail, what the price covers and what it does not, walking grade, group size and age range — from the pages you publish, at the hour people actually research.
A single supplement, deposit or balance date comes back only where your pages carry it. Where a departure is unpriced, the assistant says as much and the office picks it up.
Cancellations, transfers, money already paid and financial-protection questions route to a named person, carrying the traveller's wording. The assistant promises nothing.
Itinerary, what the price covers and what it leaves out, the walking grade, how large a group gets and who it suits, supplements and the departures still open — all answered from your own trip pages and booking conditions. Refunds, financial protection, accessibility on a physical tour and dietary needs on an included meal are captured for a named person and never answered here.
'Interested in the walking trip' tells reservations nothing they can work with. The assistant closes the gaps first — which departure, how many travelling, whether anyone needs a single room or would share, and what is still standing between them and a decision — then hands the whole thing over in the traveller's own words. What does not happen is a booking. No reservations system sits behind the chat window: nothing is held, no deposit is taken, no place is allocated. Your office confirms.
With Adoomi
Fig. 06.A · after-hoursThe hours travellers research in are the hours nobody is at a desk, and the one person who knows the route is on the trail. From your own pages, at exactly those hours, the assistant covers what the rest day includes, whether transfers and entrance fees sit inside the price, what a moderate grade means underfoot, and which departures your page still lists as open. A refund question, an accessibility request or a party above your published maximum stops there and goes to the person you named.
Itinerary detail, inclusions and exclusions, walking grades, group size, kit lists, deposit and balance terms straight from your booking conditions: the questions that come back for every departure get answered where they are asked, at any hour, from your pages. What still needs a person gets one — whether a rebuilt knee will manage the ascent, a wheelchair on a cobbled walking tour, a dietary need on an included meal, a party above your published maximum, anything about money already paid.
Fig. 08.A · controlsThree things never get answered here: what your financial protection covers, whether a refund, transfer or cancellation will be granted, and whether a tour suits someone's mobility. Each goes to the office manager or tour leader you name, in the traveller's own wording — an email alert, or the chat moved across to WhatsApp. Everything else comes from your published trip pages; an unanswerable question is a handover, not an invention. None of this makes your business compliant with anything.
Itineraries, booking conditions and the FAQ you connect are all it may draw on. Nothing goes live until you have been through the proposed answers yourself.
A supplement, deposit or balance date is quoted only when your page prints it. An unpriced departure gets a straight 'not on the page' and a handover to the office.
ATOL, ABTA, refunds, transfers and anything about money already paid route to your office manager. The assistant says nothing about cover or outcome itself.
Conversations are held on EU infrastructure, with GDPR export and deletion on request. What a traveller writes stays out of our logs, and no tracking cookies are set.
Single supplements come from your trip page or not at all. Where the page prices one, the assistant quotes that figure and shows the source it came from. Where a departure is still unpriced, it tells the traveller the page does not carry a supplement yet and puts the question to your office.
Financial-protection questions go to a named person, always. The assistant can point a traveller at the booking-conditions page you publish, but it states nothing of its own about what is covered, by whom, or in which circumstances. That answer comes from your office, not the chat window.
Bookings are captured as enquiries, never transacted. No reservations system sits behind the chat window, so nothing is held, no deposit is taken and no place is allocated. The assistant collects the trip, the departure, party size and contact, then hands it to your office.
Accessibility on a physical tour is never settled in chat. Terrain, transfers and accommodation vary by departure, so the question goes to the tour leader you name. Dietary needs on an included meal go the same way, to whoever confirms with the caterer, with the traveller's wording attached.
Refund, transfer and cancellation requests are routed, not resolved. The assistant captures the booking reference the traveller gives and the request in their own words, then alerts your office manager. It cannot look up a booking or predict what your terms will produce.
Credits are the unit, not seats: £0 a month carries 50 message credits, £8 buys 200 on Local, £20 buys 500 on Growth and £75 buys 4,000 on Scale. Connecting the site, checking the proposed answers and adding one line to it runs to ~10 min.
There is no reservations integration to build, because the assistant connects to none. It is a single line added to your existing site, drawing on the trip pages, booking conditions and FAQ you publish, and the enquiry lands where enquiries land today. Your pages are read again on a set cadence, and again the moment one of them changes, so next season's departures answer themselves once published — and a date pulled at short notice is still a question for the office until someone edits it.
Itinerary, inclusions, grade, group size and departure questions answered from your own trip pages, in the traveller's language, at the hour they research.
An unpriced departure gets a plain 'our pages don't show that' and a handover, never a figure the assistant worked out for itself.
Mobility questions on a physical tour go to your tour leader; refunds and protection go to your office manager, with the traveller's own words attached.
From the guides library
Connect your trip pages, booking conditions and kit lists, then push at the edges: the supplement on an unpriced departure, whether a rebuilt knee manages the summit day, what your protection covers, a refund on a trip you pulled. You see every answer before a traveller does, and can delete any of them. Setup — connect, review, one line on the site — is a ~10 min job on the £0 Free plan. Plan comparisons sit on the pricing page; the guardrails and handoff page shows a refusal in full.
Fig. 12.A · Tour operators