Travel insurance quotes in ChatGPT: what Manulife's launch means for agent builders

On September 28, 2026, Manulife announced a CoverMe plugin in ChatGPT. Eligible Canadian travellers describe their trip in the chat and get a personalised travel insurance quote. The company calls it the first plugin of its kind in Canada and its first ChatGPT plugin globally, and trade press picked it up through the following week (ITIJ, Travelweek).

For anyone building an AI travel agent, the interesting part is not that an insurer showed up in ChatGPT. It is where the flow stops.

Quote in the chat, purchase on the website

Per Manulife’s announcement, the plugin asks trip questions and returns a quote. The traveller then completes the application and purchase on CoverMe.com, and anyone whose needs require more information or other coverage options is sent there too.

That is a sensible first step for a single insurer launching in a consumer assistant. It also shows the two halves of selling insurance through an agent:

Step	In the Manulife plugin	What an agent needs to own it end to end
Quote	In ChatGPT	Trip, dates, travellers in; products and price out
Accept	Traveller decides in chat	An explicit yes captured by the agent, not inferred
Bind / issue	On CoverMe.com	A paid call that issues the policy, safe to retry
After-sale	Insurer’s own channels	Policy reference stored with the trip so support can find it

Manulife’s Chief AI Officer put the direction plainly: “Agentic commerce is quickly becoming a customer preference to find and choose products, and that shift is global” (ITIJ).

Why builders care about the handoff

An OTA or travel agent product that already holds the itinerary is in a better spot than a general assistant. It knows the destination, the dates, and who is travelling, so it can price cover without re-asking. If the purchase then jumps to a third-party site, the agent loses the session and the trip record loses the policy.

Keeping it in-session comes down to three rules we cover in Build an AI travel agent that fulfills ancillaries:

1. Quote before commit. Show the supplier’s price and exclusions before anything is bought.
2. Bind only on an explicit yes. The model should never treat a quote as consent.
3. Idempotent paid calls. A network retry must not issue a second policy.

One insurer per plugin, or a shelf

A branded plugin covers one insurer’s products in one market. Builders serving several markets usually want more than one supplier behind the same tool shape, so the agent can quote a trip to Japan and a trip from Germany without new prompts.

On Ancilair, travel insurance is routed as anc.insurance.quote, then anc.insurance.bind. Suppliers include Cover Genius, battleface, AXA Partners, and Hepstar, and you can name one supplier when only that one should answer. The price is quoted on the call at the supplier’s rate with 0% markup, and the bind runs only after an explicit yes with an Idempotency-Key. Details are on the insurance use case and the Cover the trip workflow. If your host speaks MCP, see Travel MCP server for ancillaries.

What to watch

• Whether more insurers follow Manulife into AI assistants, and whether purchase moves inside the chat.
• Embedded platforms aimed at partners, such as Allianz Partners’ new Metaportal for banks and loyalty programmes (ITIJ), which point the same way: cover sold inside someone else’s journey.

Sources

• Manulife press release via Newswire (Sept. 28, 2026)
• ITIJ: Manulife brings travel insurance quotes to ChatGPT
• Travelweek: Manulife now offering travel insurance quotes in ChatGPT
• ITIJ: Allianz launches digital platform for tailored travel cover
• Ancilair insurance use case

Not affiliated with Manulife or OpenAI. This is not insurance advice; coverage, eligibility, and exclusions are set by each insurer. Product details summarised from public announcements as of October 2026.