Skip to content
Back to Blog

Travel agent resources7 min read

Writing a travel proposal cover email

A repeatable system for travel agents to write proposal cover emails: structure, worked example, copy‑paste template, and a Nowah planning prompt.

Editorial illustration of travel-planning work: writing a travel proposal cover email

A travel proposal cover email should do one job: create a clear, low-friction next step—approve, request changes, or choose between options—without forcing the client to read the entire proposal inside an email thread. A useful working format is a short 3–2–1 message: 3 lines of personalisation, 2 tailored highlights, 1 explicit call to action.

Use Nowah to shape the itinerary logic behind your two highlights (see Nowah features). Prepare the proposal and send the cover email through your agency’s normal approved process.

What the cover email must achieve

Choose the email's highlights from the reviewed Nowah itinerary, not generic destination copy. The proposal introduction guide helps connect them to the brief.

What it must achieve

A strong cover email:

  • Reconnects to the client’s “why.” Reflect their stated priorities without assuming a particular decision.
  • Shows evidence of design. Two specifics that demonstrate you made intentional planning choices.
  • Directs attention. Tells them where to look in the proposal and what decision is needed.
  • Keeps commitments accurate. Availability, holds, changes, and refunds are governed by supplier terms and confirmation, and you should obtain client approval before taking payment.

If dates, budget or rooming remain undecided, identify them rather than implying final approval is possible. Keep detailed itinerary and supplier conditions in the attached proposal.

The 3–2–1 structure (use this every time)

Use Nowah to confirm the practical difference behind each of your two highlights. The itinerary tradeoff method keeps the message focused.

The “3”: three lines of personalisation

Your first three lines (maximum) establish alignment. They should include:

1) Goal/occasion (why the trip matters) 2) Constraint (pace, comfort, accessibility, number of moves) 3) Scope (what you’re sending)

Practical sentence starters:

  • “You said you want [goal] while avoiding [constraint].”
  • “I built the plan to prioritise [priority] and keep [comfort factor] in mind.”
  • “Attached is your proposal for [destination + duration + dates/season window].”

The “2”: two highlights that sell the fit

Choose exactly two highlights. Keep them as design decisions you can stand behind, rather than claims you can’t control.

A dependable pairing:

  • One stress reducer (logistics/pacing). Examples: fewer hotel moves, a reset day, reduced early starts, simplified transfer pattern.
  • One excitement builder (experience/choice). Examples: a special-night concept, a guided-day concept, a scenic segment, a clear A/B choice.

Good highlight wording:

  • “I kept you to two bases to reduce packing/unpacking.”
  • “I included one lighter day mid-trip to keep energy up.”
  • “I’ve left you an A/B choice for the ‘special night’ so you can pick the vibe before I prioritise availability checks.”

Avoid wording that implies certainty you don’t have (e.g., “I secured,” “locked in,” “guaranteed availability”).

The “1”: one next step (a reply they can type)

Give one action only. Make it reply-friendly.

Examples:

  • “Reply Direction agreed or Changes requested (with two specifics).”
  • “Reply Option A or Option B.”
  • “Reply with two time windows for a 10–15 minute review call.”

If you mention checking availability or holds, keep it conditional and accurate:

  • “A direction reply does not authorise purchase. I will send final component details, prices and supplier terms for your approval before payment.”

Use Nowah to extract two email-ready highlights (planning support)

The cover email is easier to write when your itinerary logic is crisp. Nowah helps because you can work conversationally through the brief, then shape an editable day-by-day outline before you choose the two highlights you’ll reference (see Nowah features).

A practical workflow:

  1. Draft or refine the itinerary in Nowah from your discovery notes (trip research + editable day itineraries).
  2. Ask Nowah to identify two design decisions (one pacing/logistics, one experience/choice).
  3. Review and correct anything that could be sensitive to seasonality, policy, availability, or traveller constraints.
  4. Write the 3–2–1 cover email referencing only what you can confidently deliver.
  5. Prepare the client-facing proposal in your normal tools and attach it to the email.

The point isn’t to outsource judgment; it’s to get a clean planning draft so your cover email can be short, specific, and decision-led.

Copyable Nowah planning prompt (fictional/anonymised)

Paste this into Nowah and edit the bracketed fields. (Use your agency’s approved data-handling process for real client info.)

You are assisting a travel adviser. Create a proposal-ready itinerary outline for a fictional client.

Trip: 10 nights in Costa Rica for a fictional family of four (2 adults, children aged 9 and 12), 10–20 July 2027. Origin London; arrival airport San José. Ground trip budget USD 8,000, excluding international flights and personal spending. Verify rather than invent transfer durations or seasonal conditions.

Requirements:

- Keep the pace family-friendly; avoid back-to-back very early starts.

- Flag transfer-heavy days; verify durations and any airport-to-base movement before describing the pace.

- Nature portion: 6 nights across exactly two bases/regions.

- Beach portion: 4 nights with downtime.

Output format:

1) Day-by-day outline with the intent of each day (arrive + settle, activity day, rest + pool, transfer day).

2) Identify two “design decisions” that make the itinerary easier for a family (write them as email-ready highlights).

3) Offer two different “special night” concepts (not brand-specific) that could fit naturally.

4) List 8 adviser check-questions to confirm with the client before booking.

What you should check before using the output

Generative tools can produce plausible but incorrect specifics, so treat output as a draft that needs evaluation (for general risks and the importance of review, see NIST’s overview: NIST’s generative AI risk profile).

Before you echo Nowah-derived points in a cover email, confirm:

  • Pacing math: early starts and transfer days align with the client’s tolerance.
  • Relevance: your two highlights map directly to what the client told you matters.
  • Promise discipline: you’re not implying guaranteed inventory, pricing, or outcomes.

Worked example: complete cover email (hypothetical)

Fictional brief (hypothetical):

Check the fictional cover email against the current Nowah planning direction and proposal. The proposal quality checklist helps catch mismatched versions before sending.

  • Travellers: two adults + two children (ages 9 and 12)
  • Trip shape: wildlife first, beach second
  • Priorities: kid-friendly pacing; one “special” evening; reduce packing/unpacking
  • Dates: 10–20 July 2027 (10 nights); nature stays 3 + 3 nights, beach stay 4 nights

Subject: Your 10‑night nature + beach proposal — paced for the kids

Hi Sarah and Tom,

You said the priority is strong wildlife experiences without the trip feeling rushed for the kids.

Attached is your 10‑night nature + beach proposal. I’ve kept the nature section to two bases (rather than moving every couple of nights) to reduce transfer fatigue.

Two highlights to look for:

  • A built-in reset day during the nature portion, so you’re not doing early starts every day.
  • A “special night” choice with two styles (a quieter, more private setting vs. a livelier, more social setting) so you can pick the vibe before I prioritise availability checks.

Next step: Please reply with either Direction agreed or Changes requested. If changes, tell me:

1) Do you want more nature time or more beach downtime? 2) Which “special night” style suits you best (private vs. social)?

This reply agrees the direction only. The proposal identifies estimates and unconfirmed items. I’ll send final prices, availability and relevant supplier terms for your approval before purchase.

Best regards,

Alex [Agency] [Phone] | [Time zone]

Why this example works (mechanically):

  • It reflects the brief immediately (wildlife strength + kid pacing).
  • It provides two defensible design decisions (two bases; reset day + choice).
  • It gives one next step with guided answers that reduce vague back-and-forth.
  • It stays accurate about supplier-controlled terms without derailing the email.

Copy/paste artifact: 3–2–1 cover email template

Standardise this template in your agency knowledge base.

Subject line (choose one):

  • Your [destination] proposal — built around [priority]
  • Proposal ready: [trip nickname] ([month/season window])
  • Two options for [destination] — [constraint]

Email body:

Hi [Client name],

You said you want [Priority #1] while avoiding [Constraint/Pain point], so I built the proposal around those.

Attached is your proposal for [Destination + duration]. The overall approach is: [one-sentence structure, e.g., “two bases + a lighter day mid-trip”].

Two highlights to look for:

  • [Highlight 1: stress reducer you can justify]
  • [Highlight 2: excitement builder or A/B choice]

Next step: Please reply with Direction agreed or Changes requested. If changes, tell me:

1) [One directional preference question] 2) [One comfort/pacing/rooming preference question]

Your reply agrees the planning direction only. Before purchase, I will confirm current availability and send the exact component details, prices and supplier terms for your approval.

Best regards,

[Your name] [Agency] [Phone] | [Time zone]

Pre-send checklist (fast enough to use every time)

Use this as a final gate before you send.

Check

Pass test

If not, fix by…

Personalisation is specific

First 1–2 lines reflect goal + constraint from the brief

Replace generic opener with the client’s words

Email stays an email

~150–250 words; short paragraphs

Delete everything except 2 highlights + CTA

Highlights are defensible

No “secured/guaranteed/locked in” language

Rephrase as intent/approach; move detail into the proposal

CTA is singular

Only one next step

Remove secondary asks; keep “Reply with…”

Supplier terms are accurate

No promises about holds/refunds/prices

Add one conditional supplier-terms sentence

Approval-before-payment is explicit

Client approval requested before payment

Add one sentence if missing

Put it into practice with Nowah

If you adopt 3–2–1 as your agency standard and use Nowah to draft/refine the itinerary logic that produces two strong highlights, you have a consistent structure for describing the planning direction and the decision required.

Build the itinerary outline in Nowah, ask it to surface two design decisions, then apply the pre-send checklist before you attach your proposal document. Check that the attachment matches the email: same version, duration and open choices. Send it through your agency’s normal channel; Nowah supports the planning work behind those two highlights.

Share this article