Muse for Travel Pros: Itinerary Drafts, Client Preference Notes, and Booking Confirmations That Match
A travel advisor setup for Muse: turn intake notes into a preference profile, draft day-by-day itineraries from confirmed details only, and reconcile every booking confirmation before the client travels.

A travel advisor’s work is a chain of small facts that have to agree. The name on the booking has to match the passport. The hotel check-in has to line up with the flight arrival. The final payment date in your tracker has to match the supplier’s date, or the booking can lapse. One trip can involve five or six suppliers, each with its own confirmation, deposit schedule, and cancellation policy. The itinerary is the easy part to draft. Keeping every version of it true is the job.
The Travel Institute describes the work as a lifecycle with seven phases, from inquiry and intake through planning, booking, and post-booking, then travel itself and closure after the client comes home. That lifecycle maps directly onto a Muse setup. Muse drafts the itinerary from the intake, maintains the client preference note that makes the next trip faster, and reconciles booking confirmations against the itinerary before anything goes to the client. You keep the supplier relationships, the booking decisions, and every payment. Muse does the drafting, the cross-checking, and the follow-up list.
One rule holds the setup together: a confirmed detail comes from a confirmation, not from a draft. A flight time comes from the airline confirmation. A hotel rate and cancellation policy come from the supplier confirmation. A client preference comes from the intake or the client’s own words. A draft itinerary is never a source for itself.
The short version
- Build one preference profile per client from the intake and update it after every trip. The profile is what makes the second trip faster than the first.
- Draft itineraries in three labeled layers: confirmed, held, and proposed. Never let a proposed option read as booked.
- Reconcile every booking confirmation against the itinerary line by line: names, dates, times, totals, deposit and final payment dates, and cancellation terms.
- Send the final itinerary two to four weeks before departure, built from confirmations, with a day-before check for flights and transfers.
- The failure mode to watch for is a polished itinerary built on a stale draft. The fix is one master itinerary and a confirmation check before any client-facing version goes out.
The Setup: The Travel Desk
Call the whole arrangement the Travel Desk. The example I run it against is Cedar & Compass Travel, a two-advisor agency that plans custom leisure trips. The client in this lesson is the Alvarez family, two adults and two teenagers, planning nine days in Portugal, Lisbon and the Alentejo, for next spring. Every job below runs on the same desk: the intake form, the preference profile, the master itinerary, and the confirmation folder, all in one place per trip.
The setup rests on the same pieces every time. A standing instruction from our memory guide sets the house rules: never present a proposed option as booked, never state a price, time, or policy from a draft when a confirmation exists, and never send a client-facing itinerary without a human read. The intake is the source for preferences, and the supplier confirmation is the source for booked details. The tracking runs on a scheduled routine: a Monday sweep for payment deadlines and a pre-departure check for every trip leaving in the next 30 days.
For bookings that run through Muse itself, the boundary is the same one in our trip planning guide for travelers: Muse can search and compare options, it asks before spending money, and the advisor verifies the confirmation independently afterward. Where a connector exists, use it and keep the confirmation it returns. Where it does not, the supplier portal confirmation is the record. Either way, the Travel Desk treats the confirmation as the only proof a booking exists.
Prompt 1: Turn the Intake Into a Preference Profile
Run this right after the discovery call, and update it in the closure phase after every trip. The Travel Institute’s intake covers the nuts and bolts: dates, number of travelers, destinations, travel style, budget range, and interests, plus traveler information forms for dates of birth, passport details, allergies, and similar facts. The preference profile is the layer on top of that form, the notes that let you plan the next trip without asking the same questions again: aisle or window, early flights or no red-eyes, walkable neighborhoods over resort strips, dietary needs, mobility notes, loyalty numbers, and the pace the client actually enjoyed, not the pace they asked for before they knew.
Keep two kinds of notes separate. Hard facts go in the traveler record: legal names as they appear on passports, dates of birth, loyalty numbers, and accessibility or dietary needs. Judgment notes go in the preference profile: what they loved, what they would skip, how much structure they want in a day. A hard fact never changes because a draft assumed it did. A preference note gets revised after every trip, because clients learn what they like by traveling.
Store passport and payment details in the system your agency already uses for sensitive documents, not pasted into a prompt or a general notes file, and reference them by pointer: the profile says where the document lives, not what it says.
Build the preference profile for the Alvarez family from the intake and discovery notes below. (1) Traveler record: legal names exactly as written, dates of birth, and any dietary, mobility, or medical notes the intake states, copied word for word. Do not correct, shorten, or guess any name or date. (2) Preference profile: flight preferences, hotel style and neighborhood preferences, daily pace, food interests, activities they asked for, activities they said to avoid, and budget range, each tied to the line in the intake or notes that supports it. (3) Missing list: anything a booking would need that the intake does not state, such as passport expiry dates or loyalty numbers, listed as missing, never filled in. Rules: if the intake and the discovery notes disagree, flag the disagreement and use neither until I confirm. Do not invent a preference the client did not state.
Intake form: [paste it]. Discovery call notes: [paste them]. Previous trip notes, if any: [paste them].
Read the profile against the intake before you save it. The errors that matter are small and expensive: a middle name dropped from a legal name, a food allergy recorded as a preference instead of a need, a budget range remembered one tier higher than the client stated. The profile is worth building because it compounds. The second trip starts from what the first trip taught you, and the client feels known instead of re-interviewed.
Prompt 2: Draft the Itinerary in Three Layers
Run this in the planning phase, after the discovery call and the planning fee, if you charge one. The advisor’s proposal in the Travel Institute lifecycle is a personalized itinerary with a clear reply-by date, so momentum does not die while a hold expires. A good draft gives the client three labeled layers and no ambiguity about which is which: confirmed means a confirmation exists, held means a supplier is holding the option until a stated time, and proposed means it is a recommendation with a price to verify, not a booking.
Build the draft day by day, with transfer times and check-in windows in it, because an itinerary that ignores the drive from the airport is a draft that will break on day one. For each day, state what is booked, what is held, and what is still a choice for the client. Where you offer options, offer a small set with a recommendation and a reason tied to the preference profile, best fit, best value, or the upgrade, instead of a long list the client has to research themselves. That curation is the service. Muse can assemble it, and the recommendation and the reason stay yours to approve.
Draft the nine-day Portugal itinerary for the Alvarez family. Work from the preference profile and the supplier options below. (1) Day by day: date, base, confirmed items with their confirmation references, held items with the exact hold expiry, and proposed items labeled proposed with the price marked “to verify.” Include arrival and departure transfers with realistic travel times, hotel check-in and check-out times, and no more than [number] planned activities per day, per the family’s pace preference. (2) Options: for the Lisbon hotel and the Alentejo stay, give up to three choices each, labeled best fit, best value, and upgrade, with one sentence each tying the choice to a stated preference. (3) Money table: deposit due now, final payment dates per supplier, and the cancellation terms for each item, copied from the supplier terms below, never summarized from memory. (4) Client reply-by date: [date], with a short proposal note I can send with the draft. Rules: never move a proposed or held item into the confirmed layer. If a time, price, or term is not in the material below, mark it missing.
Preference profile: [paste it]. Supplier options and terms: [paste or attach them]. Flights already confirmed, if any: [paste the confirmation].
Check the draft against the profile before it goes to the client. The common error is pace: an itinerary that packs Lisbon into two full days for a family whose profile says slow mornings. The second error is a hold presented without its expiry, so the client deliberates past the deadline and loses the room. The draft should make both impossible to miss: the pace visible in the day plan and the expiry printed next to every held item.
Prompt 3: Reconcile the Confirmations and Close the Trip
Run the first half after every booking, and again when you send the final itinerary two to four weeks before departure. Run the second half in the closure phase, a few days after the client comes home. The booking phase in the lifecycle has its own task list: deposit authorization, insurance quote, deposit applied, confirmation email sent, each step in sequence. The reconciliation is the check that the sequence produced a trip that matches what the client approved.
Read each supplier confirmation against the master itinerary line by line: traveler names, dates, flight times and flight numbers, hotel dates and room type, transfer pickup times, totals, deposit paid, balance due and its date, and cancellation terms. A mismatch found here is an inconvenience; the same mismatch found by the client at check-in is a crisis, and it is your crisis at the worst possible hour.
Reconcile the Alvarez Portugal trip and prepare the closure update. Work from the master itinerary and the supplier confirmations below. (1) Confirmation check: for every booked item, compare the confirmation against the master itinerary on names, dates, times, room type or cabin, total price, deposit paid, balance due and due date, and cancellation terms. List every mismatch in a table with the itinerary value, the confirmation value, and which document I need to fix. If an item has no confirmation, list it as unconfirmed, do not treat the draft as proof. (2) Final itinerary draft: rebuild the client-facing itinerary from the confirmations only, in departure order, with confirmation numbers, pickup times, and a day-before contact note. Leave a clear gap for any item still unconfirmed instead of filling it from the draft. (3) Closure, to run after travel: draft a welcome-home note, a review request, and an updated preference profile that adds what this trip taught us, what they loved, what they would skip, and the pace they actually kept, each point tied to their feedback below. Rules: every name, date, time, and amount comes from a confirmation or the client’s feedback, never from the draft itinerary. If a confirmation and the itinerary disagree, say so and use the confirmation.
Master itinerary: [paste it]. Supplier confirmations: [paste or attach them]. Client feedback after travel, for part 3: [paste it when you have it].
The post-booking phase has its own rhythm, and the routine carries it: final payment reminders before each supplier deadline, excursion and dining reservation windows when they open, and the pre-trip call for first-time or less experienced travelers. The welcome-home note and review request complete the closure phase in the Travel Institute lifecycle. Closure leads to the next inquiry: a client whose preferences are on file and whose last trip ended with a check-in is a client who books the next trip with you.
| Job | When | What it answers |
|---|---|---|
| Preference profile | After intake, updated after every trip | Who is traveling, what do they need, and what did the last trip teach us? |
| Itinerary draft | Planning phase, with a reply-by date | What is confirmed, what is held, until when, and what is still proposed? |
| Confirmation reconciliation | After each booking, and again 2 to 4 weeks before departure | Does every confirmation match the itinerary on names, dates, times, and money? |
| Payment and deadline sweep | Every Monday | Which deposits, final payments, and hold expiries land in the next 30 days? |
| Closure update | A few days after the client returns | What did they love, what would they skip, and what goes in the profile for next time? |
What Can Go Wrong: The Final Itinerary Built on a Stale Draft
Here is the failure mode you will meet first. The client approves the draft and you book the flights, and the airline moves the departure by three hours. The supplier confirmation shows the new time, but the master itinerary still shows the old one, because the confirmation went into a folder and nobody reconciled it. Two weeks later the final itinerary goes out, built from the draft, with the old departure time, the old transfer pickup, and a hotel check-in note that no longer fits. The family arrives at the airport on your time, not the airline’s.
The cause is the pattern in our failure modes guide: a clean, finished-looking document gets less checking than a rough one, and the final itinerary is the most finished-looking document in the file. It reads as the trip. If it was built from the draft instead of the confirmations, it is a polished copy of a trip that no longer exists.
The fix has three parts, and all three are already in the prompts above. First, the master itinerary has one owner and one version, and drafts get marked as drafts in the file name, so a client-facing version is never built from an old copy by mistake. Second, Prompt 3 rebuilds the final itinerary from the confirmations only, and leaves a visible gap for anything unconfirmed, so a missing confirmation cannot be papered over with draft text. Third, the pre-departure check runs again the day before travel for flights and transfers, because schedules move after the final itinerary goes out too. A booking counts as the confirmation states it, with the names, dates, and times the supplier holds.
Start With One Returning Client
Do not rebuild the whole agency this week. Pick one returning client with a trip in planning, run Prompt 1 on their last intake and your notes from their previous trip, and read the profile against the source before you save it. Then run Prompt 2 for the new trip and notice what the profile saved you: the questions you did not have to ask again, and the options you did not offer because the profile already ruled them out.
Run that way, one client tests the profile, the three-layer draft, and the confirmation check before the next inquiry arrives.
The seven-phase lifecycle, inquiry, intake, planning, booking, post-booking, travel, and closure, the intake items, the booking task list, the final itinerary sent two to four weeks before travel, and the post-booking reminder pattern follow Christina Schlegel's guide to repeatable processes for travel businesses, published by The Travel Institute. Muse booking behavior, search and compare, approval before spending, and independent verification of confirmations, follows the All Things Muse trip planning guide linked above.


