Travel customer support needs to preserve the details that matter after a booking is complete. A traveler may have discussed room preferences or cancellation conditions during planning. The service team must distinguish those requests from the terms the booking actually confirmed.
Expedia Group announced its acquisition of Layla in July 2026, expanding its investment in conversational travel planning and booking. The announcement illustrates the direction of investment. The operational recommendations here apply broadly to travel businesses and do not describe a failure in Expedia’s service.
Distinguish a request from a confirmed commitment
A planning conversation can contain ideas, preferences and questions that never become part of the final reservation. Customer support should not treat the conversation transcript as proof that every request was accepted.
Create a record that separates the traveler’s requested outcome, the supplier’s confirmation and any item still awaiting a response. Attach the applicable terms to the booking so agents can identify the conditions that applied at purchase.
This distinction matters for a room preference, an arrival arrangement or a change request. A clear status helps the agent explain what is confirmed and what still requires action.
Design a handoff that another team can use
A useful booking handoff contains the reservation identifier, relevant dates and the issue the traveler needs resolved. It also shows the contact history and any action already initiated.
Include only the information needed by the receiving team and protect sensitive traveler details through appropriate access controls. A long transcript without a concise case summary can still leave the next agent unsure what to do.
Ask the receiving team to confirm that it has enough information to proceed. If a supplier must approve a request, make that dependency visible in the support record and identify who will follow up.

Assign ownership when several businesses are involved
Travel often involves a booking platform, a property and another service provider. Customers need to understand which business can approve a change, while the support operation needs a clear process for coordinating the request.
For an illustrative situation, a traveler asks to adjust an arrival date after making a conversational booking. The agent should verify the reservation, review the applicable terms and confirm which party has authority to make the change. A request submitted to the property should remain pending until a response arrives.
The customer-facing team can own communication without promising an outcome controlled by the supplier. Explain the next action and when the traveler can expect an update.
Test continuity across channels and urgent situations
A booking issue may begin in chat and continue by phone when departure approaches. Omnichannel support should preserve the existing case rather than create unrelated records for each contact.
Test the handoff with realistic scenarios before expanding the workflow. Include a traveler close to departure, conflicting information in the record and a supplier that has not yet responded. Confirm which situations require urgent escalation and which can follow the standard queue.
Prioritization should reflect the consequence of delay, not simply the order in which messages arrived. Document those rules so different agents reach consistent decisions.
Measure the quality of the complete service journey
Review handoff completeness, repeat contacts about the same reservation and cases delayed by missing information. Track time to an authorized decision separately from time to the first response.
Sample the commitments agents communicate. The record should show whether a change is requested, approved or completed. Confusing these states can create unrealistic expectations even when the underlying process is functioning correctly.
Advensus provides travel and hospitality support. We believe convenient booking experiences need equally clear service ownership afterward. Review your booking support workflow with Advensus to identify where traveler context or responsibility can be lost.



