Guide · AI agents · For the owner whose customers write after they have booked
Meta's AI agent for travellers who have already booked: changes, refunds, and what Meta says it must never promise
Meta has published a guide to using its AI agent for business with customers who have already bought a ticket: looking up their journey, explaining what their fare allows, moving them to another departure and saying where a refund has got to. Meta's example is a rail operator, and it also names airlines, ferries, coaches and travel agencies.
Published 6 October 2026
What Meta says this agent is for
Meta separates this from selling. There is nothing to browse and no new customer: the traveller is known, often stressed, and asking about something with a date on it. The expensive mistake is not a lost sale but a wrong answer about whether a ticket can be changed, or a change made to the wrong part of a journey.
- Looks up the traveller's own bookings
- From the business's booking system. Meta says that without this connection the agent cannot see a journey at all.
- Explains what the fare allows
- From the fare rules and conditions the business uploads, for that particular ticket.
- Changes a journey, after confirming the cost
- Any difference in fare comes from the booking system and is confirmed with the traveller before anything changes.
- Reports on a refund already requested
- Where it has got to, nothing more.
- Hands over disruption and complaints
- Cancellations, missed connections and compensation claims go to the team, not answered by the agent.
For travel agencies and resellers selling on behalf of operators, Meta notes the agent usually changes nothing directly and passes the request to the operator.
What the agent answers from
- An instruction
- Look the booking up before answering, take fare differences from the booking system, and hand over anything involving disruption or money owed.
- FAQs for policies that rarely change
- How long refunds take, luggage, assistance for travellers who need it, and how to claim compensation.
- Fare rules and conditions of carriage
- Uploaded as documents. They run to many pages, and the agent draws on them rather than repeating them.
- Help pages, but never live updates
- The agent reads a website as a snapshot. Meta says a copy of yesterday's service updates is worse than no answer, because the traveller cannot tell it is out of date. Live status belongs in a live connection, or with people.
- The system that owns the booking
- Meta says to connect the agent to the booking system itself, not a reporting copy of it.
The mistakes Meta warns about
- Trusting a booking reference
- A reference typed into a chat proves nothing. Meta's agent looks up only bookings belonging to the number the traveller is writing from, so an overheard or guessed reference returns nothing.
- Answering from the general policy
- What this particular ticket allows is the most consequential fact in these chats. The booking system should return the fare conditions with the booking, or the agent will sometimes answer from the general rules instead.
- Guessing which leg
- 'Change my ticket to Sunday' on a return booking does not say which direction. Meta says the agent must confirm the direction in words; guessing has an even chance of moving the wrong one.
- Promising money
- A traveller told they will be refunded treats it as a commitment, and Meta says walking that back costs more than the refund would have. The agent reports refunds already requested and hands everything else to a person.
- A handover that goes nowhere
- Telling the agent to hand over does nothing on its own. Without a real handover set up, the traveller is acknowledged and then abandoned.
Ready for the worst day
Meta points out that messages after a purchase peak exactly when the operation is struggling. It advises testing the booking lookup at several times normal traffic, and deciding in advance what the agent says when the booking system cannot be reached.
- Test the hard cases. A fare that cannot be changed, a return where the direction is unclear, a fare difference, a refund already requested, a compensation claim, a departure cancelled right now, and a reference that belongs to someone else.
- Watch two things separately. Whether the booking lookup is answering, and whether the step that changes bookings is succeeding.
How handing a conversation to a person works, and what an agent may decide alone, are in the support line guide.
Questions
Can Meta's agent change a traveller's booking?
If the fare allows it. Meta's guide has the agent state any difference in fare from the booking system, confirm which part of the journey is changing, and only then make the change.
Can the agent promise a refund or compensation?
No. Meta says it can report on a refund already requested and should hand everything else involving money to a person.
What happens when a departure has just been cancelled?
Meta's guide hands disruption to the team. Live status should come only from a live connection to the business's systems, never from a copy of a website page.
We are a travel agency. Does this fit us?
Meta lists travel agencies and resellers. It notes the agent usually changes nothing directly for them and passes the request to the operator.
How does the agent know the booking belongs to the person asking?
It looks up only bookings belonging to the number the traveller is messaging from, and the business's system refuses a reference that does not belong to that number.
Sources
- Meta's developer documentation: Meta Business Agent, Post-purchase support agent, read 6 October 2026.
- Meta's developer documentation: Meta Business Agent overview, read 6 October 2026.
More plain-language notes like this one are on the guides page.
Want disruption chats to reach a person?
We set up a business's WhatsApp number on a system its team runs, so when an AI agent hands over a complaint or a disrupted journey, a person can pick the conversation up in one place the business owns. A short call is the easiest way to see how that would work for you.
Book a demo