This is a scripted walkthrough of an enquiry of the kind we receive on WhatsApp most days. Press the button to advance. Nothing here calls a model — the responses are written to show the shape of the interaction.
Worth understanding, because it determines what is easy and what is hard to build.
Turn the sentence into structured fields: nights, budget, party composition, passport, tolerance for driving. This part is genuinely easy and reliable.
Against our own inventory, live pricing and visa rules for that passport. This is a database query, not a model. Accuracy comes from here.
Assemble stays, activities and transfers into three coherent trips that differ meaningfully rather than trivially. This is the hard part.
Say plainly what each option costs and what it gives up. This is what customers remember, and what a comparison site cannot do.
The critical design decision: prices and availability come from our systems, never from the model. The model writes the sentences around numbers it is given. That is what keeps it from inventing a hotel that does not exist or a fare we cannot honour.