Intent extraction
Pulls dates, party, pace, interests and constraints from free text in the traveler's own words, and shows its reading so you can correct it.
Platform · Itinerary Studio
Itinerary Studio reads an inquiry the way an experienced advisor does, drafts a routed multi-day proposal from your product library, and hands it to a person to finish. The draft takes minutes. The judgment stays yours.

Here is a real-shaped inquiry, lightly disguised:
We’re two, late fifties, ten days in September. She has a knee that complains on long descents. We care more about food than museums. We walked the Dolomites with you three years ago and loved the small hotels, and we’d rather not change beds every night. Our 30th anniversary is on the 14th.
An experienced advisor reads that and already knows a lot: moderate pace, limited downhill, three or four bases rather than eight, a returning-client tone, a dinner worth protecting. A newer advisor might catch half of it.
Itinerary Studio reads it the first way. It turns the paragraph into structured intent, drafts ten days from your own contracted products, checks each day for feasibility, and puts the draft in front of an advisor with notes attached. Kept descents under 400 m a day. Three bases. Anniversary dinner on Day 6 at a lodge you’ve used for anniversaries before. Suggest asking whether they’d like a rest day after the longest walk.
The advisor spends their time on the part that wins trips, which is judgment, warmth and the line about the hotel owner who remembers them, instead of rebuilding Day 3 from a spreadsheet.
Intent capture
Nobody writes a spec for a holiday. They write we're not big on museums and she's fine on the flat, and an experienced advisor hears a whole brief in it. Studio does the same first pass. It separates what's fixed from what's flexible, notices what's missing, and asks one good question instead of sending a thirty-field form.

How it works
Five stages, with a person in charge of the one that matters most.
Paste an email, forward a web form, drop in call notes or a WhatsApp thread. Studio extracts intent and shows you what it understood before it drafts anything.
Days are assembled from products you actually sell and places your team has verified: contracted hotels, guides, transfers, restaurants with notes. Anything outside your library is marked as a suggestion, never slipped in as fact.
Each day goes through Route Engine for opening windows, travel times, pacing and supplier capacity. Days that don't hold together come back flagged, with the reason.
The advisor edits a tracked draft: swap a day, ask for something gentler, adjust the tone. Studio explains each choice, and nothing reaches the traveler until a person approves it.
Approved proposals go out as a web proposal, PDF or mobile itinerary in your design and voice. When the traveler says yes, Booking Flow picks up the supplier requests.
Pulls dates, party, pace, interests and constraints from free text in the traveler's own words, and shows its reading so you can correct it.
Drafts only from your products, contracts and verified places. No invented cafés, no trails that closed two seasons ago.
Ask for a quieter Day 4 or something outdoors instead of the cooking class and get two or three options, each one route-checked.
Cost, sell price and margin per line and per trip, so the advisor sees what a swap does to the business before making it.
Your tone rules, the phrases you love, the phrases you ban, and how you introduce your own guides. Studio writes inside them.
Every draft, edit and approval is kept. Senior staff can require sign-off on trips above a set value or with specific risks.
Measured, not promised
From a 12-week pilot with a family-run walking-tour operator in the Alps, measured against a four-week baseline taken before anything changed. Read the case study.
Pilot figures from one operator and one season. They are our measurements, not a guarantee; we baseline your current process before we estimate anything for you.
It reads an inquiry the way my best coordinator does. It noticed the knee, it noticed they'd walked with us before, and it asked about the anniversary. Then it got out of the way.
Questions
Not as fact. It drafts from your product library and the places your team has verified. If something outside the library would suit the traveler, Studio marks it as a suggestion for the advisor to check. It never adds it silently.
Your advisor, every time. Studio drafts, explains and checks; a person edits and approves. You can require senior sign-off above a trip value or for specific risks. We call this draft, don't decide.
Yes. During onboarding we build a house-style guide from proposals you're proud of: tone, structure, words you avoid, how you introduce guides and lodges. Your advisors' edits keep refining it.
No. Studio exports approved proposals and booking lines into the systems you already run. The categories we connect are on integrations.
We test Studio against a set of your past inquiries, scored by your own advisors for feasibility, fit and tone, before it goes live, and we keep scoring in production through Managed AI Operations. The method is in How we evaluate an itinerary generator.
Related
Send an anonymized inquiry from last month. On the discovery call we'll draft it in Studio, show you every choice it made, and let your best advisor pull it apart.