Travel
The enquiry arrives in the evening, the agent calls back in the morning.
At a travel agency most calls arrive exactly when people have time to think about a holiday, which is after six and at weekends. The agency is closed, the call is lost, and the search continues on a website that answers at any hour.
The assistant takes the quote request with destination, dates, party size and an indicative budget, writes it as a lead in the CRM, offers a callback slot from the agent calendar, and confirms by SMS. It makes no bookings and quotes no prices.
What rings at an agency
Almost every useful call ends in the same place: a complete enquiry on an agent desk, with enough detail to search for something concrete.
A quote request
The destination or the kind of holiday, the dates, how many adults and children, the indicative budget.
Document questions
What paperwork a destination needs, whether a visa is required. From your documents rather than from the model memory.
The status of a booking
Taken and handed over, because it concerns an individual file.
Booking a meeting
A real slot from the agent calendar, for complex enquiries.
Groups and corporate events
Recognised early and passed directly to whoever handles them.
From an evening call to a complete enquiry
The flow stops short of the quote, because a travel quote depends on availability in systems the assistant has no access to.
- 01 Establish the shape of the trip Destination or type, approximate dates, how many people and what ages. Four fields, without which nobody can search for anything.
- 02 Ask the budget as a range Not an exact figure but an order of magnitude. It is the question agents avoid, and without it half the search is wasted.
- 03 Answer from your documents For paperwork and entry conditions, from the knowledge base. When it finds nothing, it says the agent will check.
- 04 Offer the callback A concrete slot from the agent calendar, not a vague promise that somebody will ring.
- 05 Write the lead Contact and deal in the CRM with every field, plus an SMS confirmation with the callback time.
What the agent finds in the morning
The difference between a useful enquiry and a lost call is four completed fields. That is all.
| The lead | Contact and deal in HubSpot or Pipedrive, with destination, dates, party size and budget. |
|---|---|
| In the calendar | The time the agent calls back, as an event rather than a mental note. |
| The confirmation | An SMS to the customer with what was taken and when somebody rings. |
| On the call record | The transcript and the structured output with the same fields every time, comparable across enquiries. |
What it does not do for a travel agency
Travel is a category where a price stated wrongly is paid out of the agency margin.
- It makes no bookings It has access to no reservation or distribution system and holds nothing.
- It quotes no prices It does not estimate the cost of a holiday and compares no offers. It gathers the data an agent searches with.
- It does not answer on visas from memory It answers only from your documents, because entry conditions change often and a stale answer sends somebody to the airport for nothing.
- It takes no deposits Not by card, and not through a link sent during the call.
- No link to travel systems There is no connector for booking platforms. Any link is your own HTTP tool.
What agencies ask us
Can it search offers in our system?
Only if it has an API and a tool is written for it. We have no connector for any booking platform. Without one, the value lies in taking the enquiry completely at the hours when nobody answers.
Is it useful if an agent calls back anyway?
Yes, for two reasons: the enquiry arrives complete, so the agent searches for something concrete instead of ringing to find out what the person wants, and the customer gets a specific callback time instead of silence. The second matters more than it sounds.
Can it answer about paperwork and visas?
Only from the documents you upload and keep current. Do not let it answer from general knowledge: entry conditions change, and a wrong answer about a travel document has consequences at a border rather than in a conversation.
Does it work for outbound calls too?
Yes, for calling past customers before the season, through a campaign with windows and suppressions configured. The list and the basis for the call remain yours.
Where to go next
Integrations
25 business connectors, 18 selectable providers, eight storage destinations.
Outbound campaign
Contacts, pacing, window, compliance, start, report.
Assistants
Transcriber, model, voice, tools, knowledge, and a way to prove it still works.
Pricing
Components at their published price, the platform on top, and what we cannot price yet.
Notes
-
1
The tools named on this page are the ones in
App\Services\Integrations\ConnectorRegistrycarryingimplemented. Anything that is only in the catalogue, without that flag, is not named here as though it worked. - 2 The lead is written through the HubSpot or Pipedrive connectors. There is no connector in the registry for travel reservation systems.