π Prerequisites
Features
What you get with this outcome
Communication That Never Sleeps
From booking confirmation to pre-departure updates, your customers expect timely, branded communications at every touchpoint. Kaptio's email automation replaces disconnected Outlook templates and manual processes with a unified system: create templates once, trigger automatically based on booking events, and track delivery without leaving Salesforce. Bunnik Tours consolidated their entire communication workflowβconfirmations, supplier instructions, and registration formsβinto automated, traceable emails.
Visual coming soon
email-template-diagram
Email Template Engine
Create beautiful, branded email templates using Kaptio's template editor. Merge fields dynamically populate customer names, booking details, and itinerary information. Templates support HTML formatting, conditional content based on channel or product, and multi-language variants.
- βDrag-and-drop template editor
- βDynamic merge field personalization
- βConditional content by channel/product
- βMulti-language template variants
Visual coming soon
email-trigger-diagram
Automated Triggers
Configure triggers to dispatch emails automatically when booking events occur. Booking confirmations on status change, payment receipts on transaction, pre-departure reminders at X days before travelβall without manual intervention. Link triggers to specific channels and booking stages.
- βEvent-based automatic dispatch
- βStage-linked communication rules
- βChannel-specific trigger configuration
- βConditional logic for smart routing
Visual coming soon
Supplier Notifications
Supplier Notifications
Automate supplier communications with booking confirmations and amendment notifications. Templates include booking details, passenger lists, and service requirements. Suppliers receive the right information at the right time without ops team intervention.
- βAutomatic supplier booking alerts
- βAmendment notifications
- βPassenger list inclusion
- βService-specific content
Visual coming soon
Delivery Tracking
Delivery Tracking
Monitor email delivery status, opens, and bounces directly in Salesforce. Activity records link communications to bookings and contacts for complete audit trails. Identify delivery issues before they impact customer experience.
- βDelivery status monitoring
- βActivity logging on records
- βBounce handling and alerts
- βComplete communication audit trail
User Journey
Step-by-step flow from start to finish
πΊοΈUser Journey Flow
Follow the steps from start to finish
Implementation Plan
How to implement this outcome
π Project Overview
Template Design
Week 1- β’ Gather brand assets and copy
- β’ Create booking confirmation template
- β’ Create payment receipt template
Automation Setup
Week 2- β’ Configure email triggers
- β’ Link triggers to stages
- β’ Set up delivery tracking
Validation
Week 3- β’ Execute UAT scenarios
- β’ Train reservation team
Resources
Configs, tools, and documentation to help you
βοΈ Golden Configs
Booking Confirmation Template
Standard template with itinerary summary, pricing, and payment details
Payment Receipt Template
Transaction confirmation with payment breakdown and balance due
Pre-Departure Email
Travel documents, final instructions, and emergency contacts
Supplier Booking Notification
Supplier-facing template with service details and passenger requirements
Email Template Architecture
Kaptio email templates are configured at the Channel level and linked to specific booking stages. This ensures customers in different channels receive appropriately branded and formatted communications.
Template Hierarchy
Channel (e.g., Direct Sales)
βββ Stage (e.g., Booking Confirmed)
βββ Email Template
βββ Subject Line (with merge fields)
βββ Body Content (HTML/Text)
βββ Merge Fields (dynamic data)
βββ Attachments (optional)
Key Template Types
| Template | Trigger Event | Key Content |
|---|---|---|
| Quote/Proposal | Quote created | Itinerary summary, pricing, CTA |
| Booking Confirmation | Payment received | Full details, payment confirmation |
| Payment Receipt | Transaction complete | Amount, method, balance |
| Pre-Departure | X days before travel | Documents, instructions, contacts |
| Amendment Notice | Itinerary modified | Changes summary, new pricing |
| Supplier Notification | Line confirmed | Service details, passengers |
Merge Field Reference
Templates support dynamic content using merge fields that pull data from Salesforce records:
Common Merge Fields
| Field | Description | Example |
|---|---|---|
{!Contact.FirstName} | Customer first name | βSarahβ |
{!Itinerary.Name} | Booking reference | βBT-2025-1234β |
{!Itinerary.TravelStartDate} | Departure date | βMarch 15, 2025β |
{!Itinerary.TotalPrice} | Booking total | β$4,500.00β |
{!Package.Name} | Tour name | βJapan Discoveryβ |
{!Passenger.FullName} | Traveler name | βSarah Johnsonβ |
Conditional Content
Show or hide content based on booking attributes:
{!IF(Itinerary.Channel = 'Agent',
'Your travel agent will provide further details.',
'Please contact us directly with questions.'
)}
Trigger Configuration
Event-Based Triggers
Configure automatic dispatch based on Salesforce events:
| Event | Trigger Point | Template |
|---|---|---|
| Status Change | Booking Confirmed | Confirmation Email |
| Payment Made | Transaction Created | Payment Receipt |
| Date Relative | 30 days before travel | Pre-Departure |
| Record Update | Amendment saved | Amendment Notice |
Stage-Linked Actions
Each booking stage can have associated email actions:
Quote Stage
βββ Available Actions: Send Quote, Decline Quote
βββ Email Template: Quote Proposal
βββ Next Stage: Booking Confirmed
Booking Confirmed Stage
βββ Available Actions: Send Confirmation, Request Documents
βββ Email Template: Booking Confirmation
βββ Auto-Send: On stage entry
Supplier Communication
Booking Confirmation to Suppliers
Automatically notify suppliers when bookings are confirmed:
- Service details and dates
- Passenger names and requirements
- Special requests (dietary, accessibility)
- Confirmation request with response options
Amendment Notifications
When bookings change, suppliers receive:
- Change summary (added/removed/modified services)
- Updated passenger list
- New dates if applicable
- Reconfirmation request
Delivery Tracking
Activity Records
Every sent email creates an Activity record linked to:
- Contact (recipient)
- Itinerary (booking)
- Template used
- Timestamp
- Delivery status
Monitoring Bounces
Configure bounce handling workflows:
- Email bounces β Activity marked βFailedβ
- Flow triggers β Task created for ops team
- Team reviews β Updates contact email
- Resend β Manual or automatic retry
Best Practices
Template Design
- β Use responsive HTML for mobile compatibility
- β Include plain text fallback for email clients
- β Test merge fields with missing data scenarios
- β Keep subject lines under 50 characters
Automation Rules
- β Set prerequisites (e.g., payment before confirmation)
- β Use sandbox testing before production activation
- β Document trigger logic for team reference
- β Monitor delivery rates after go-live
Compliance
- β Include unsubscribe option for marketing emails
- β Store consent records on Contact
- β Respect communication preferences by channel
- β Comply with regional email regulations (GDPR, CAN-SPAM)
Bunnik Implementation Example
Bunnik Tours consolidated their communication workflow:Before: Outlook templates, manual sends, no tracking After: Automated triggers, branded templates, full audit trail### Key Templates Implemented1. 7-Day Quote Option - Full itinerary for sales conversion 2. Booking Confirmation - Post-deposit confirmation with payment summary 3. Supplier Confirmation - Service details for vendor coordination 4. Receipt for Direct Bookings - Transaction confirmation 5. Sales Invoice - Tax invoice for finance requirements### Automation Results- 80% reduction in manual email sends
- Zero missed confirmations
- Complete communication history on every booking
Common Pitfalls
Avoid these implementation mistakes
Don't send from personal emailsβuse shared mailboxes for consistency and continuity
Test merge fields with edge casesβmissing data causes embarrassing blank placeholders
Configure bounce handlingβundeliverable emails need follow-up workflows
Set stage prerequisitesβbooking confirmations shouldn't send before payment
Plan template versioningβchanging live templates affects in-flight bookings
Test across email clientsβHTML rendering varies between Outlook, Gmail, mobile