This article is auto-synced from its in-app version in Tai.
If your company runs on Nezasa's TripBuilder, connecting it to TAI lets your AI agents work with your real trip data and reach your travellers where they already are.
When you'd use this
Use the TripBuilder integration when you want agents grounded in your actual bookings, travellers, and trips — not generic answers. For example: a customer care agent looks up a booking the moment a traveller calls, summarises a traveller's history, or pulls a booking-trend breakdown for a manager. The same connection lets you drop TAI chat straight into your TripBuilder-powered apps, so help shows up in context instead of in a separate tool.
How it works
The integration links your TripBuilder account to your TAI workspace, then opens up three things:
Agents work with your TripBuilder data. Once connected, agents can read your booking, traveller, and trip data — look up a booking by reference, review a traveller's recent trips, or answer aggregate questions like "how many bookings did we create per destination last month". This is read-only: agents query your data, they never change a booking. Today this capability is available through the built-in TripBuilder Ops & BI Agent, which is purpose-built for booking lookups, traveller history, and booking analytics.
Embed TAI chat where your travellers and agents already are. Using the TAI Chat SDK, you can embed a TAI-powered chat into your TripBuilder-based portals and apps. Travellers and your own staff get AI help in context — on a booking page, in a support panel, or as a floating widget — without switching tools. When the chat is embedded on a specific booking, it can scope to that booking automatically.
Single sign-on for your TripBuilder users. Your TripBuilder users can use TAI agents without creating or signing into a separate TAI account. They stay signed in to TripBuilder, and TAI recognises them through a secure, trusted connection between the two systems — so each user only ever sees the data they're allowed to see in TripBuilder.
Setting it up
The TripBuilder integration is configured together with Nezasa rather than switched on from a settings page. Nezasa links your TripBuilder account to your TAI workspace and sets up the data connections it relies on. Those connections are currently Nezasa-managed — consistent with how connectors work today (Nezasa provisions and operates the built-in connectors that reach external systems). Reach out to Nezasa to enable the integration for your company; once it's live, your agents and embedded chat start working with your TripBuilder data with no further setup on your side.
Tips and limits
Agents read your TripBuilder data — they never modify bookings or write back to TripBuilder.
Live booking lookups reflect the current state of a booking. Aggregate analytics (counts, trends, breakdowns) are typically refreshed daily, so very recent changes may not appear yet.
The data-access part of the integration is reached through agents that are configured for it — today, the built-in TripBuilder Ops & BI Agent. Setting up the integration and its data connections is handled by Nezasa, not self-service.
Each user only sees the bookings and data their TripBuilder account is permitted to see — the integration carries your existing access rules across, it doesn't widen them.
Related