Every departure,
briefed.
Prepare tour content before document generation — day narratives, hotel assignments, images, and inclusions — all written back to Salesforce and ready for Edge Docs.
The content gap
Tour operators have rich content — but getting it into Salesforce objects so documents can render it is the bottleneck.
Scattered content
Tour narratives live in spreadsheets, websites, PDFs, and email threads. No single source of truth for what a departure actually contains.
Manual wiring
Someone has to manually enter day descriptions, hotel names, images, and inclusions into Salesforce objects — for every single departure.
No visibility
No way to see which departures are ready for document generation and which still have gaps — until a customer opens a blank proposal.
Brief is not a CMS
Brief is an outcome-oriented operator tool. The outcome is “this departure is briefed and ready for document generation.” It writes to Salesforce objects — it doesn't replace your content management system.
From scattered content to briefed departures
Brief sits between your content sources and Salesforce. It gives operators a focused UI to prepare departure content, then writes it back to the objects Edge Docs reads from.
Sources
Where content comes from
Edge Brief
Content preparation UI
Output
Where content goes
Three layers of tour content
Understanding what's shared and what's unique is the key to efficient content management across hundreds of departures.
Package
Tour ProductJapan Discovery
- Tour Highlights (23 items)
- Inclusions + Details (4 categories)
- Not Included (6 items)
Departure Template
Day-by-Day StoryJapan Discovery Template (16 days)
- Day 1: Depart Australia
- Day 2: Arrive Tokyo
- Day 3: Imperial Palace, Ginza and Shibuya
- ...13 more days with narratives, highlights, meals
Departure
This Specific Run12 Nov 2026 Japan Discovery
- Grand Prince Hotel Takanawa (Nights 1-3, Confirmed)
- Hakone Yunohana Prince Hotel (Night 4, Confirmed)
- Lead Guide: TBD
Edit once, render everywhere
Day content lives on the template. When you improve Day 3's narrative, every departure using that template gets the improvement. No manual sync across departure dates.
Hotels are per-departure
Even if Bunnik uses the same hotel for every Japan Discovery run, each departure has its own hotel assignments. Swap a hotel for one run without affecting the others.
Two readiness bars, two workflows
Option Ready checks shared content (template + package articles). Final Docs Ready checks per-departure operations (confirmed hotels with addresses, assigned guides). Different teams, different timelines.
How do I handle variation?
Templates are the unit of variation. Here's how to think about it.
Same story for all departures?
Use one template. Edit it from the package Brief. All departures share the same day narratives automatically.
Seasonal variation?
Create a second template. Assign spring departures to one, autumn to the other. Each template has its own day content — cherry blossom vs autumn leaves.
One-off change for a single departure?
Clone the shared template, modify the clone, assign it to just that departure. Every other departure keeps using the original.
Rich content per day
Each day of the itinerary gets its own narrative, highlights, images, and location — ready to flow into any Edge Docs template.
- Senso-ji temple visit
- Nakamise shopping street
- Akihabara electronics district
- Shibuya crossing photo op
Named hotels per departure
Assign specific hotels to each departure and track confirmation status. Writes to Departure_Service_Assignment__c so documents show the real hotels, not placeholders.
| Night | Hotel | Location | Status |
|---|---|---|---|
| 1–3 | Grand Prince Hotel Takanawa | Tokyo | Confirmed |
| 4 | Hakone Yunohana Prince Hotel | Hakone | Confirmed |
| 5–6 | Hida Hotel Plaza | Takayama | Confirmed |
| 7–9 | Umekoji Potel Kyoto | Kyoto | Confirmed |
| 10–11 | Sheraton Grand Hotel Hiroshima | Hiroshima | Tentative |
| 12–13 | Sheraton Miyako Hotel | Osaka | Confirmed |
Adapter compatible
No need to migrate all content into Salesforce. Brief can pull from any API source and selectively persist what you need.
Website CMS
Pull tour descriptions, images, and highlights from your existing website CMS via REST API
Partner API
Receive tour operator content feeds — hotel descriptions, excursion details, supplier notes
AI Brief Generator
Generate day narratives from package metadata, previous departures, and tour descriptions
Readiness visible in Salesforce
Operators see content readiness right in Salesforce — no context switching needed. Canvas components show which departures are ready and which need attention.
| Departure | Days | Hotels | Incl. | Overall |
|---|---|---|---|---|
| 10 Oct 2026 | 78% | |||
| 24 Oct 2026 | 65% | |||
| 7 Nov 2026 | 45% | |||
| 21 Nov 2026 | 22% |
Canvas components embed inside Salesforce Lightning pages — operators see content readiness without leaving their workflow.