Email Merge Tags

Merge tags are placeholders wrapped in double curly braces — for example, {{client_first_name}} — that auto-fill with real client, trip, and booking data when an email is sent. Write them directly into your email template body or subject line, or insert them from the Merge Fields picker (the { } button). The picker is available in the template editor and in the compose window when you email a client or trip traveler — click Merge Fields next to the Insert row and the tag drops in at your cursor.

Available Tags

Client

Tag	What it fills
`{{client_name}}`	Client's full name
`{{client_first_name}}`	First name
`{{client_last_name}}`	Last name
`{{client_preferred_name}}`	Preferred / nickname, if set
`{{client_names}}`	Everyone on the client's household, e.g. "John & Jane"
`{{client_email}}`	Client's email address
`{{client_phone}}`	Client's phone number

Trip

Tag	What it fills
`{{trip_name}}`	Name of the trip
`{{destination}}`	Destination
`{{start_date}}`	Trip start date
`{{end_date}}`	Trip end date
`{{departure_date}}`	Departure date
`{{return_date}}`	Return date
`{{total_price}}`	Total trip price
`{{deposit_amount}}`	Deposit amount

Payment

Tag	What it fills
`{{amount}}`	Amount currently due
`{{balance_due}}`	Remaining balance
`{{due_date}}`	Payment due date
`{{payment_type}}`	Type of payment (deposit, final payment, etc.)
`{{deposit_due_date}}`	Deposit due date
`{{final_payment_date}}`	Final payment due date

Booking

Tag	What it fills
`{{booking_supplier}}`	Supplier or cruise line
`{{booking_confirmation}}`	Confirmation or reservation number
`{{booking_type}}`	Type of booking (flight, hotel, cruise, etc.)

Cruise

Tag	What it fills
`{{ship_name}}`	Name of the ship (e.g., "Wonder of the Seas")
`{{stateroom_category}}`	Stateroom category (e.g., "Balcony", "Ocean View")
`{{stateroom_number}}`	Assigned cabin number
`{{embarkation_port}}`	Port of departure
`{{disembarkation_port}}`	Port of arrival / turnaround
`{{cruise_length}}`	Length of the sailing (e.g., "7 nights")

Agent & Agency

Tag	What it fills
`{{agent_name}}`	Your full name
`{{agent_email}}`	Your email address
`{{agent_phone}}`	Your phone number
`{{agent_title}}`	Your title or role
`{{agency_name}}`	Your agency's name
`{{agency_phone}}`	Your agency's phone number
`{{website}}`	Your agency's website URL
`{{clia_number}}`	Your agency's CLIA number

Links

Tag	What it fills
`{{portal_url}}`	Personalized link to the client's travel portal
`{{form_link:<form>}}`	Personalized link to one of your forms — see below
`{{documents_list}}`	Links to the trip's documents, opened through the client's portal. Internal files and files narrowed to other travelers are left out

Sending a Form With an Email

You don't have to send a form as its own separate message. Any email you write can carry a form, so your note about Disney dining and the form that collects dining requests arrive together.

Two ways to add one:

Insert → Form puts a branded button in the body ("Open Form →"). This is the one most advisors want.
Merge Fields → Forms drops the raw {{form_link:...}} tag at your cursor, for when you'd rather write your own sentence: "you can fill in your dining requests here".

Both work in the compose window (from a client, a trip, or the inbox), in saved email templates, and in automation and journey steps.

Every recipient gets their own link. Email three travelers and each one gets a distinct URL, so their answers come back attached to the right person, prefill what you already know about them, and file against the trip the email came from — exactly as they would if you'd used Send on the Forms page.

A few things worth knowing:

Preview shows the plain form link, not a personalized one. Opening a preview never records a send.
You can add more than one form to the same email.
If the form has been deleted, the send is refused with an error rather than quietly dropping the button. Delete the button and insert a current form.
In a campaign the link is the same for everyone. A blast is one message to a whole audience, so there is no per-recipient link to mint — the answers arrive, but without the personalization above.

Cruise Details

The six cruise tags — {{ship_name}}, {{stateroom_category}}, {{stateroom_number}}, {{embarkation_port}}, {{disembarkation_port}}, and {{cruise_length}} — pull from the cruise booking attached to the trip.

For reservation number, sailing date, and cruise line, use the standard tags {{booking_confirmation}}, {{start_date}} / {{departure_date}}, and {{booking_supplier}} respectively — these already resolve from the booking record.

Populating the data

Cruise tags only fill when the underlying booking has cruise-specific data. There are two ways to populate it:

AI import (recommended): Open the trip and use Import Booking to paste or upload a cruise confirmation. JourneyFuse extracts ship name, stateroom category, cabin number, embarkation port, and disembarkation port automatically from the confirmation document. Cruise length is derived from the sailing dates.

Manual entry: Open the booking, scroll to the cruise section of the booking form, and fill in:

Ship Name
Stateroom Category
Cabin Number
Embarkation Port
Disembarkation Port

Cruise length is calculated automatically from the booking's start and end dates — no separate field needed.

Where Merge Tags Work

Merge tags resolve at send time in all of these places:

One-off compose emails — from a client, lead, or trip, insert tags with the Merge Fields picker (or type them). They fill from that client and trip when the email sends, so a saved template isn't required for basic personalization.
Saved email templates — tags fill when the template is loaded into a compose window tied to a client and trip.
Automated emails — tags fill at send time from the trip and booking context attached to the automation step.

Writing to a couple, or the whole family

{{client_names}} fills with everyone on the client's household, so "Hi ," reaches a couple as "Hi John & Jane," without you typing the second name. Three or four people list out in full ("John, Jane & Emma"), and a household of five or more collapses to "John & family" so a greeting never turns into a roster.

It fills from the Travelers tab on the client record, so add the partner there (Add Traveler) for their name to appear. Anyone you haven't added yet, or a client who travels alone, simply gets their own name, exactly as {{client_preferred_name}} would fill it. That makes the tag safe to put in a shared template that goes to solo clients and couples alike.

When you email several trip travelers at once, client tags such as {{client_first_name}} fill with the trip's lead client for everyone on the send — the greeting is personalized to the booking, not to each individual recipient.

Cruise tags need cruise data on the booking to fill, so they work best from a trip-linked compose, template, or automation. A tag with no data — for example {{ship_name}} on a non-cruise trip, or a field that was never filled in — renders as empty rather than showing the raw {{tag}} text to the client.

Sending Emails — compose and send emails from your inbox
Automations — set up automations that send emails automatically
Email Campaigns — send bulk emails to client segments