Straight answer
A valid reservation requires deposit, advance payment, direct billing, third-party authorization, failed-payment recovery, fraud verification, release, or refund action.
Best fit
Hotels, inns, resorts, motels, and comparable transient lodging operators.
Conditional fit
Only after the authoritative project, service, account, and exception records reconcile.
Main tradeoff
Automated emergency, accessibility-rights, medical, trafficking, criminal, fraud, liability, chargeback, or legal decisions.
Industry Context And Next Action
Subject
Payment action for reservation {{reservation_reference}}Hi {{guest_or_payer_contact}},
Reservation {{reservation_reference}} at {{property_name}} has payment status {{payment_status}}.
Named guest, verified booker, payer or company, relationship and authorization, stay dates, reservation source, rate-plan owner, billing contact, and identity-verification state: {{party_authority_summary}}
Deposit, advance payment, room and tax, incidentals, security or damage authorization, amount or calculation basis, currency, due or authorization time, successful or failed state, and transaction reference without full card data: {{payment_obligation_summary}}
Charges the payer authorizes, charges excluded, guest responsibility, routing instructions, tax-exemption or direct-bill review, folio delivery, authorization-release timing controlled by issuer, and refund state: {{billing_scope_summary}}
Secure link or approved form, independent callback path, fraud warning, failed-payment options, booking-hold deadline, and responsible owner: {{secure_action_summary}}
Pay or authorize securely, verify, correct, choose another method, contact us, or report concern: {{payment_link}}
Never send card numbers, security codes, passwords, or identity documents by ordinary email. A hotel authorization and a bank's final release or posting are separate states.
{{payment_owner}} · {{phone_number}}
{{company_name}}
Best For
- Hotels, inns, resorts, motels, and comparable transient lodging operators.
- Properties able to synchronize reservations, accessible room inventory, payments, arrival, room readiness, keys, incidents, lost property, and folios.
- Direct and third-party bookings with governed source reconciliation.
Not Best For
- Automated emergency, accessibility-rights, medical, trafficking, criminal, fraud, liability, chargeback, or legal decisions.
- Messages that expose card data, identity documents, room numbers, access credentials, incident evidence, or private stay details.
- Properties unable to distinguish confirmed inventory and features from preferences.
Variable Tokens
When To Send This Email
Trigger
A valid reservation requires deposit, advance payment, direct billing, third-party authorization, failed-payment recovery, fraud verification, release, or refund action.
Timing
Only after the authoritative project, service, account, and exception records reconcile.
Frequency
Once per valid event or record version; reminders must retain the same verified obligation or decision.
Timing note
Use only a real operational deadline, safety escalation, weather window, or live allocation window.
Why This Email Works
Personalization Notes
- Use current property, reservation source, guest authority, room and feature inventory, total price, terms, payment state, arrival, key, maintenance, incident, property custody, folio, refund, and owner records.
- Use minimum necessary disability, health, identity, room, travel, incident, and payment information; keep card data, identity documents, room numbers, and access credentials out of ordinary email.
- Pause for active emergency, fire, medical event, violence, abuse or trafficking concern, inaccessible arrival without safe accommodation, fraud or compromise, responder activity, privacy complaint, chargeback, legal hold, or manager control.
Platform Setup Steps
Trigger
A valid reservation requires deposit, advance payment, direct billing, third-party authorization, failed-payment recovery, fraud verification, release, or refund action.
Segment
Verified guest, booker, traveler, group contact, payer, authorized representative, travel advisor, or responsible hotel contact for one current lodging record.
Delay
Send after the record is reconciled and before the next dependent operational action.
Reply owner: Payment owner responsible for payer authority, exact obligation and billing scope, secure channel, transaction reference, fraud routing, reservation hold, refund state, and issuer boundary.
- Verify property, reservation or stay, guest and recipient authority, source channel, room and feature state, price and policy version, payment or incident state, owner, and timing.
- Send minimum necessary facts with one controlled confirmation, secure payment, arrival, handoff, option, report, dispute, or manager action.
- Record disposition and evidence; suppress superseded automation; update CRM, PMS, central reservation, inventory, payment, key, housekeeping, maintenance, incident, lost-property, folio, loyalty, and accounting systems.
Stop conditions
- Valid disposition, superseding reservation or stay record, cancellation, reply, or live handling.
- Guest, authority, dates, room type, accessible feature, rate, fee, tax, payment, arrival, occupancy, key, maintenance, incident, folio, refund, or privacy change.
- Active emergency, fire or life-safety event, violence, trafficking or abuse concern, medical event, inaccessible arrival without safe accommodation, suspected fraud or account compromise, law-enforcement contact, privacy complaint, chargeback, legal hold, or qualified manager control.
Before You Send
Note: there are laws and regulations around this. Please make sure you follow any applicable rules before sending.
Subject Line Variations
- Payment action for reservation {{reservation_reference}}
References the actual operating record or decision.
- Deposit, Payment Authorization, And Fraud Control: {{reference_number}}
Direct operational alternative.
- Update from {{company_name}} about {{reference_number}}
Use with a recognized business and valid reference.
Mistakes To Avoid
- Treating a room preference or generic accessible label as a confirmed feature
A specific room feature may determine whether the stay is usable.
Use instead: Describe, verify, block, and hand off the exact reserved feature.
- Combining hotel and bank payment states
Authorization, capture, refund initiation, processor acceptance, and issuer posting are different.
Use instead: Name the amount, transaction state, reference, timestamp, and responsible party.
Sequence Placement
Use only for the verified lodging record represented by the current property system; suppress when stale, superseded, cancelled, disputed, unsafe, compromised, under active incident response, or controlled by manager, payment, accessibility, responder, privacy, insurer, legal, or qualified human review.
Related Email Platform Guidance
teams running behavior-based nurture with branching, scoring, and segmentation
Not best for: teams whose requirements stop at newsletters and a short welcome series
View ActiveCampaignPaid linkagencies standardizing lead-response systems across multiple accounts
Not best for: teams expecting a native field-service or legal practice-management system
View GoHighLevelPaid linkB2B organizations aligning marketing, sales, and service around shared CRM data
Not best for: small teams needing only broadcasts and a simple welcome sequence
View HubSpot
Disclosure
Some platform links on this page are paid links. If you choose a platform through one of them, EmailCampaigns.io may earn a commission. That does not change our recommendations. We include best for and not best for notes so you can decide based on fit, not payout.