An AI booking, end to end — with the deterministic engine underneath
90 sec · Watch the video →
Note the key line: the assistant does not decide — the booking is validated against the corporate travel rules before anything is committed. The assistant is a client of the policy layer, exactly as described in the API and ontology reference.
Transcript
What does a corporate travel AI booking look like according to UnityTrip? Well, this is where we've got to. I'm not going to use the widget — I'm going to come in here and say I would like to fly from the offshore island to the mainland, date of travel tomorrow. Yep, that's fine, that'll do me, thanks.
It's having a little bit of a think about that — because of course there are corporate travel rules in play — and it's made some estimates where I wasn't clear about what I wanted. Just me, thanks. So it's now coming back: booking validated, just one traveller. Shall I go and book now? Yep, that's fine, thanks. Done.
The thing is that all of this leverages off the back end: our system prompts, our conversations that you can go in and look at, held as metadata. There's a lot going on here.