All use cases

Convert

Guided trip-planning concierge

"A week in Japan in spring, food and temples, mid-budget" is not a search query — it is a trip waiting for someone to plan it.

Next best thingBehavioral triggerChatWhatsAppTravel

What it does

A traveller arrives with an idea, not an itinerary: a region, a season, a vibe, a rough budget. The site answers with a destination grid and a fare calendar, and most of that intent dissolves into open tabs and abandoned searches because nobody is there to turn the idea into a plan. The agent runs the conversation a good human travel planner would: it asks the few questions that actually shape a trip, reasons over destinations, stays, and things to do, and assembles a sequenced, bookable plan that fits the budget. The cost of doing nothing is a high-intent planner who leaves to assemble the trip across five other sites.

How it works

  1. 1
    Trigger. the traveller describes a trip in broad strokes in chat or on WhatsApp, or browsing behaviour shows them circling destinations and dates without converging on a booking.
  2. 2
    Decision. the agent runs a short discovery dialogue — dates and flexibility, who is travelling, interests, pace, total budget — and combines it with memory of past trips for a returning traveller, then reasons over live inventory across the legs of the trip.
  3. 3
    Action. it composes a sequenced plan in the thread — destination order, nights per stop, a stay per stop, a few anchor activities — each line carrying the reason it fits and a price, and offers to hold or book the components.
  4. 4
    Follow-through. stated preferences and the shape of the trip are written to memory for next time; if the traveller balks at one leg, the agent re-plans that segment within the budget rather than starting over; every planning thread is attributed to its resulting booking.
Example
CustomerI want about a week in Japan in spring — mostly food and temples, nothing too rushed, mid-budget.
AgentLovely brief. Three quick things: are your dates flexible around cherry-blossom week, is it just the two of you, and is your budget for the whole trip or per person?
CustomerFlexible by a few days, two of us, whole trip around 3,000.
AgentHere is a plan that fits: four nights Kyoto for temples and a food-market morning, then three nights Tokyo, with the slower pace you asked for and the train between them booked. Each stop has a stay and two anchor activities, all inside your budget. Want me to hold the whole itinerary, or walk through it stop by stop?

Configuration

How the agent is wired for this use case.

Triggeran inbound chat/WhatsApp message expressing open-ended trip intent, or a browse_no_converge behavioural signal from the booking site's session stream.
Tools & actions
  • Booking platform · search live fares, stay availability, and activity inventory across each candidate leg
  • Itinerary engine · sequence destinations, hold multi-component plans, and re-cost a single leg on objection
  • Customer memory · read past trips and stated preferences, write back the new trip brief and choices
  • Messaging channel · render the plan with per-line reasons and a hold/book call to action
  • Quality judge · gate the plan before it sends (budget respected, dates coherent, in-policy inventory only)
Autonomydiscovery, planning, and holds run unattended under judge gating; any irreversible booking or payment is a customer-confirmed step handed to the booking platform's own secure checkout — the agent never captures payment itself.
Channelschat · whatsapp
Escalationcomplex constraints (special assistance, visa or group logistics, a fare-rule edge case) hand off to a human travel consultant with the full brief and the assembled plan attached.

What you need

The inputs this use case runs on. Your channels stay yours; the agent supplies the judgment.

Signals

inbound trip-intent messages; non-converging destination/date browsing on the booking site.

Data

live multi-leg inventory (fares, stays, activities) with prices and availability; the stated budget and constraints; customer memory of past trips and preferences.

Guardrails

the stated budget is a hard ceiling — the agent never silently plans past it; recommendations restricted to in-policy, available inventory; booking and payment always behind a confirmed, secure hand-off; preferences written to memory only with consent.

Metrics it moves

  • conversion-rateup: broad trip intent is turned into a bookable plan in one conversation instead of leaking across tabs.
  • aovup: a sequenced multi-component trip replaces a single hesitant flight booking.
  • attach-rateup: stays and activities are planned in alongside transport, not bolted on at the end.
  • revenue-per-conversationup: each planning thread is tied to an attributable booking.

See it on your own customer journey

Bring one drop-off, one churn cliff, or one silent segment. We will show you what a proactive agent with memory and judgment does with it.

Book a demo