Solutions / 
Industries

AI customer service for travel: a concierge connected to your bookings

Before booking, while preparing, on the way and after the trip: what the concierge can answer, what your booking system has to allow, and where your team and partners come in.

Travelers ask before they book, while they prepare, on the way and after they're home, and each answer depends on a booking, a product description or a partner. An AI concierge that can read the booking answers in the traveler's language, keeps one conversation, and brings in your team or a partner such as a hotel or airline without the traveler starting again.

How far it gets depends on your booking system more than on the AI: whether bookings can be read, and whether changes can be written back. Below, stage by stage: what travelers need, what we've learned from implementations, and how Typewise handles it.

  1. Before bookingChoosing the trip"Which hotel suits us with a toddler?"
  2. PreparingDocuments, changes, payments"I haven't received my vouchers."
  3. During the tripHelp on the way"Our transfer isn't here. What now?"
  4. After the tripFeedback and complaints"The room wasn't what we booked."
The travel journey a concierge can accompany

How the concierge works with your booking system

Typewise doesn't replace your booking system or your helpdesk. It connects to them and keeps three things apart.

Information. Lookups read bookings and product information from connected systems. A booking system connects through an MCP server that exposes its data, or through Salesforce or Zendesk where booking data already sits. See the integrations for what is available.

Actions. Actions change a booking, if your booking system offers that operation. You configure each action separately, and approval by a person is on by default.

Handoff and partners. When a case needs your team, the concierge hands it over with the conversation history and a summary. When the answer sits with a hotel, airline or other partner, your team forwards the case from Typewise, and the reply comes back to the same case.

Your admins set this up: which Specialist handles which topic, which lookups and actions it may use, and when it hands over. Nova, the AI Operator in Typewise, can draft that configuration with them. Its changes stay drafts until someone publishes them, and Nova never writes to customers. The concierge your customers talk to is the AI Agent.

What travelers need at each stage, and how the concierge handles it

1. Can an AI answer travel enquiries before booking?

Yes, from your own product information. Web enquiries can arrive as a few selected fields, an offer code and one short question, without dates, room type or travel class.

From implementations. Use the concierge to complete the enquiry before your team builds the offer. It can look the offer up in your catalogue, answer from your product information and ask the traveler what is still open, so your team builds the offer once.

In Typewise. The concierge answers from the knowledge you add and the catalogue lookups you connect, and web forms reach it through the Form API. The offer itself, and the judgment about what suits the traveler, stay with your team.

2. Can the AI resend travel documents or change a booking?

It can answer questions about a booking it can read and explain what a fare or product allows. Resending vouchers or tickets needs an integration that returns the document, or a standard file you upload. Changing a booking needs write access to your booking system.

From implementations. Some older booking systems have no interface that provides write access. Plan the connection, who owns it and how changes are written back as part of the project, not as a later phase. Until then, the concierge collects what a change needs and your team makes it.

In Typewise. A booking lookup and a booking change are configured separately. The change is an action, with approval by a person on by default. A change that depends on a supplier becomes a specific task for your team, and the traveler hears back in the same conversation.

3. Can travelers get help from the AI during the trip?

This stage is one to build toward rather than switch on. Travelers on the way may write from a phone, in a hurry and from another time zone, and help on the way depends on knowing exactly what was booked. It needs the booking connection and a way to identify the traveler first.

Plan first. Decide before you open this stage where urgent cases go: to whoever is on duty, with the booking and the conversation attached, so nobody asks the traveler to repeat the story.

In Typewise. With those in place, the concierge can answer what the booking and your guidance cover in the channels you run, such as chat, email or WhatsApp, including outside office hours. On WhatsApp the phone number identifies the traveler. On chat, your site can pass a signed-in traveler's details in a signed form.

Also possible. Updates to the travelers affected by a disruption. Your team can start an email conversation with each traveler from Typewise, and replies come back to the same ticket. Sending these updates automatically from your booking or operations system is an integration to scope with us, and on WhatsApp it needs approved message templates.

4. How can AI help with travel complaints?

By collecting the details and documents once and, where the booking system is connected, checking them against the booking, so your team starts with a complete case.

From implementations. A complaint can take more of a team's time than its share of tickets suggests when it needs several rounds with a hotel, airline or agency. Size this stage by handling time, not ticket count.

In Typewise. The concierge receives attachments in the conversation and hands the case to your team with the history and a summary. Compensation and goodwill follow your policy and your approvers. If the traveler is identified as the same customer, for example by phone number on WhatsApp or signed in on chat, the concierge can find earlier conversations when they plan the next trip.

Also possible. Getting complaint themes to the people who plan the next season's offer. Ticket data, including customer ratings, can be pulled into your reporting through the Tickets API.

Five decisions that set how far the concierge gets

Settle these questions before a pilot starts. Each one changes what the concierge can do on day one.

DecisionWhy it mattersAsk early
Booking accessRead access lets the concierge answer about a booking; write access lets it change oneCan the booking system be read and written through an interface, and who builds that connection?
Which cases reach the AIA service address also receives supplier notices, no-reply mail and long existing threadsWhere do your routing rules live, and which new cases and web forms should the concierge receive?
Partner contactSome answers sit with a hotel, airline or provider, sometimes only reachable by phoneHow does a partner's answer get back into the same case?
SizingRequests differ in effort: a documents question is quick to answer, a rebooking or a complaint involves more steps and peopleWhat does each type of request cost in handling time, not just in volume?
Pilot timingWith approval on every reply, a pilot moves only as fast as the people who approveWho owns the pilot, and when does your peak season start?

Tour operator or booking platform: who owns the answer

Tour operators. You own the package and the relationships with hotels, airlines and local partners. The concierge can speak for the whole trip, and your team arranges what has to change with the partners behind it. Check your own booking-system access as well as your supplier dependencies; either can set the limit.

Booking platforms. You sell other companies' products, so answers about the product itself sit with the airline, hotel or provider, and agents may have to phone them in the middle of a conversation. The traveler needs to hear what's happening while they wait, and the partner's answer has to end up in the same case.

Keeping the thread when your team and partners step in

TravelerChat, email or WhatsApp
ConciergeOne case, one conversation
Your teamTakes over with history and summary
Airline, hotel or partnerReply returns to the same case
Your team forwards the case to the partner from TypewiseWhere a partner offers an interface: connect it, and the concierge asks the partner itself
One case for the traveler, your team and your partners, so nobody has to tell the story twice.

Decide where routing happens before the concierge goes live. A service address also receives supplier notices, no-reply mail and replies to conversations already in progress, and those replies need to stay with the case they belong to. If every incoming email reaches the AI first, it has to handle all of that. One option is to keep routing and queue rules in Salesforce or Zendesk and pass on only the new cases and web-form enquiries that qualify. Keep that rule in one place you can edit, and mark the cases the concierge is handling so nobody works them twice.

When a traveler's request needs your team, the handover carries the conversation history and a summary, in Typewise or in the helpdesk you already use. When the answer sits with a partner, your team can forward the case to them from Typewise. Their reply comes back to the same case, so whoever picks it up next sees the whole story. Our article on handoff ownership covers who owns the case after it.

Your team decides which decisions stay with people: refunds, compensation, goodwill and anything that depends on a partner.

How to start

Size the work by handling time, not ticket count. Group a year of requests by topic, estimate the handling time and the system each topic needs, and build the business case from that. A topic with few tickets, such as complaints, can free more time than a frequent but quick one. Our article on how much customer service AI can automate shows how to estimate it.

Plan the pilot around people. Name a small group of agents who own it and keep a list of cases that don't work yet. Go live in a period with enough real traffic to learn from, but not in your peak weeks. Then extend stage by stage as booking and supplier connections allow.

One published example of starting small: vtours began with a chatbot for frequently asked questions and added Typewise's writing assistant for its service agents, and its service center director recommends starting with simple applications and building from there. Read the vtours story.

Common questions

Which travel companies use Typewise?

Typewise has published a customer story with the travel operator vtours. It describes its own setup, and the results in it are the ones the customer reported.

Can Typewise connect to our booking system?

If the booking system offers an interface for the data you need, yes. It connects through an MCP server that exposes its lookups and actions, or through Salesforce or Zendesk where your booking data already sits. Reading bookings comes first; changing them needs write access and an action you configure, with approval on by default.

Can the concierge change bookings with our suppliers?

Where your booking or supplier system offers the change through an interface the concierge is connected to, and your policy allows it, yes, with approval where you want it. Where there is no connection, the request becomes a task for your team, and the traveler hears back in the same conversation.

How is a traveler who isn't logged in verified?

Through a check you define against booking data, for example a booking reference together with the traveler's name or email. Match the strength of the check to the request: reading a departure time needs less than changing a name. Run the check as a lookup in your systems, rather than relying on what someone writes in a chat.

Do we have to replace our helpdesk?

No. The concierge can work alongside the helpdesk you already use for routing, reporting and partner data, and hand cases over into it.

Our service is personal and bespoke. Is a concierge relevant?

It can be. The concierge doesn't have to answer everything itself. Collecting the details, keeping the traveler informed while a partner is asked, and handing your team a complete case can free the time that personal service needs.

Customer stories

Published customer stories.

Typewise has published a customer story with the travel operator vtours. It describes its own setup and results.

See all customer stories →

See the concierge on your own bookings.

Book a demo and we'll walk through your travelers' journey, the booking and partner systems behind it, and where your team wants to stay involved.