Google has expanded AI Mode to handle transactional travel workflows—flight price tracking across 180+ countries, hotel booking through ten major chains, and loyalty points redemption—whilst deliberately preserving the merchant-of-record relationship with partners. Users discover and compare options within Google's interface, but the actual booking, payment processing, and crucially, all customer service obligations remain with the hotel chain or travel site. This represents Google's systematic application of a proven pattern: Google controls the discovery and checkout surface, captures user intent data, and directs qualified transactions to partners who absorb operational friction. The architecture mirrors earlier rollouts with Walmart, Wayfair, and Etsy, where Google monetises the conversion funnel without owning post-sale accountability.
For CX teams, this creates a structural problem that existing ticketing and case management systems may not yet address. When a customer books a hotel through Google AI Mode but encounters a cancellation dispute, billing error, or room availability issue, the support ticket lands in your system—but the customer's journey began in Google's interface, their expectations were shaped by Google's conversational AI, and their payment was processed through Google Pay. The merchant-of-record designation is legally clear, but operationally ambiguous: your team now owns resolution for transactions you didn't control the discovery or initial checkout experience for. This raises a critical question for support leaders already managing Salesforce Service Cloud or Zendesk: how do you instrument visibility into customer intent and booking context when the transaction originates outside your owned channels? Teams relying on traditional case routing and knowledge management may find themselves unable to reconstruct the customer's decision journey or validate what Google's AI promised versus what your property actually offers.
The loyalty points feature compounds this complexity. When customers can compare hotel rates in both currency and miles within AI Mode, your revenue management and loyalty programme teams must now coordinate with Google's pricing display logic—a dependency that sits outside your CRM or revenue management system. Support teams will inherit disputes about points valuation, redemption eligibility, and rate parity that require cross-functional escalation to resolve. The question becomes whether your current CX infrastructure can handle transactional accountability that spans Google's AI layer, your booking system, and your loyalty platform simultaneously, or whether you're building technical debt by treating these as separate support channels rather than integrated customer journeys.
Google adds hotel booking to AI Mode, but partners keep customer service Cryptopolitan
Google’s AI Mode can now track flight prices, help book hotels, and more TechCrunch