AEGIS OS™ decides & guards
Intelligence, reviewer recommendation, next-best action and governance checks. Suggestions arrive as internal notes a person approves. Never sees the confirmation reference; never messages travelers.
Module core.post-booking-benefit-recovery · v1.0.0 · 2026-10-05
Post-Booking Benefit Recovery
A reusable Travel OS CRM™ capability for travelers who have already booked and want a person to check whether the supplier currently publishes a benefit that applies. The cruise configuration follows the OdysseySoul Cruise Credit pattern; hotel, resort, package and theme-park configurations reuse the same model. A review never guarantees a benefit, and nothing is ever changed on a reservation automatically.
Travel OS CRM™ executes
Pipeline, intake, transactional messages, tasks, reminders, internal notes, referrals and the relationship history.
GoHighLevel runs underneath
The CRM and automation infrastructure the snapshot is installed on: OS HQ → OS AEGIS MASTER TEMPLATE → member sub-accounts.
Pipeline
Eight stages, careful wording
Each stage carries the exact traveler-facing message the module sends. None promises an outcome.
Stage 1
New Request
Intake submitted; acknowledgement sent; owner alerted.
“We received your request. A person will review it — no outcome is decided yet.”
Stage 2
Pending Review
Assigned to a reviewer; SLA clock running.
“Your request is in the review queue.”
Stage 3
In Review
Reviewer is comparing the booking against what the supplier currently publishes.
“A reviewer is looking at your booking details.”
Stage 4
Supplier/Agency Check
Reviewer is asking the supplier or host agency through their official channel.
Only when the booking was made through an agent or the supplier must be asked.
“We are checking with the supplier or agency. Their answer controls.”
Stage 5
Follow-Up Needed
Information missing or traveler action required.
“We need one more detail from you before review can continue.”
Stage 6
Eligible/Offer Available
The supplier currently publishes a benefit that appears to apply; the traveler decides and acts through the supplier or agent.
“A currently published offer appears to apply. Any change is made only by you, through the supplier or your agent — never automatically.”
Stage 7
Not Eligible/No Current Benefit
No currently published benefit applies.
“We did not find a current benefit that applies to this booking. This can change; we have not changed your reservation.”
Stage 8
Closed
Resolved, withdrawn, or retention period reached.
“Your request is closed. Thank you.”
Intake
Already-booked traveler intake
Fields installed as custom fields in the template. The confirmation reference is confidential.
| Field | Key | Type | Rules |
|---|---|---|---|
| Provider / cruise line * | pbr_provider | text | |
| Confirmation reference * | pbr_confirmation_ref | text | Confidential. Confidential. Excluded from marketing, AI enrichment, exports and logs. |
| Booking date * | pbr_booking_date | date | |
| Departure date * | pbr_departure_date | date | |
| Return date * | pbr_return_date | date | |
| Ship / product * | pbr_product | text | |
| Destination / itinerary * | pbr_itinerary | text | |
| Booked through an agent? * | pbr_booked_through_agent | select (Yes / No / Unsure) | |
| Payment status * | pbr_payment_status | select (Fully paid / Still paying) | |
| First name * | first_name | text | |
| Last name * | last_name | text | |
| Email * | |||
| Phone (optional) | phone | phone | |
| Service consent: contact me about this request only * | pbr_service_consent | checkbox | Service-only. Never sets newsletter or marketing consent. |
| Referral code (prefilled from link) | pbr_referral_code | text |
Cruise
Cruise line · Ship
Configured (cruise-first)
Hotel / resort
Hotel brand or resort · Property / room type
Template — extend before use
Vacation package
Tour operator · Package name
Template — extend before use
Theme park
Park operator · Ticket / package
Template — extend before use
Synthetic dashboard
Privacy-safe reporting, with made-up requests
Every row below is fictional. Shared dashboards show aggregates only and never display confirmation references.
OdysseySoul example: 48 business hours. The update SLA promises an update, not an outcome. Each deployment sets its own value.
Open requests
6
Past update SLA
1
From referrals (all)
3
| ID | Traveler | Provider | Stage | Age (h) | Source | Paid | Agent |
|---|---|---|---|---|---|---|---|
| PBR-1001 | Sample Traveler A | Example Cruise Line | Pending Review | 6 | direct | Still paying | Yes |
| PBR-1002 | Sample Traveler B | Demo Seas | In Review | 30 | referral | Fully paid | No |
| PBR-1003 | Sample Traveler C | Example Cruise Line | Supplier/Agency Check | 44 | direct | Still paying | Yes |
| PBR-1004 | Sample Traveler D | Fictional River Co. | Follow-Up Needed | 52 | referral | Fully paid | Unsure |
| PBR-1005 | Sample Traveler E | Demo Seas | Not Eligible/No Current Benefit | 20 | direct | Fully paid | No |
| PBR-1006 | Sample Traveler F | Example Cruise Line | New Request | 1 | referral | Still paying | Yes |
KPIs: Request volume by week · Aging and SLA attainment · Source (direct / referral) · Provider · Payment status mix · Booked-through-agent mix · Outcome mix · Referral → request conversion.
Automation map
Triggers, actions and stop conditions
PBR-01 Intake → acknowledgement
Travel OS CRMTrigger: Intake form submitted with service consent
- Create/update contact (no marketing tags)
- Create opportunity in New Request
- Send transactional acknowledgement email
- Send owner alert (no confirmation reference in body)
Stop: Service consent missing → do not create opportunity
PBR-02 Routing
Travel OS CRMTrigger: Opportunity created in New Request
- Hand off to AEGIS for reviewer recommendation
- Assign reviewer
- Move to Pending Review
- Create review task due at SLA
Stop: Reviewer assigned manually
PBR-03 Next-best action
AEGIS OSTrigger: Stage change or new note
- AEGIS evaluates governed sources and suggests next step
- Suggestion written as internal note — human approves
Stop: Never sees confirmation reference; Never sends traveler messages directly
PBR-04 SLA reminder
Travel OS CRMTrigger: Task due in 8 business hours / overdue
- Remind reviewer
- Add pbr:sla:breached tag when overdue
- Escalate to owner
Stop: Stage leaves Pending/In Review/Supplier Check
PBR-05 Follow-up needed
Travel OS CRMTrigger: Stage = Follow-Up Needed
- Send transactional request-for-info email
- Wait 2 business days, one reminder
Stop: Traveler replies; Stage changes; Second reminder never sent
PBR-06 Outcome notice
Travel OS CRMTrigger: Stage = Offer Available or No Current Benefit
- Send outcome email with non-guarantee language
- Offer one-time referral link
Stop: No reservation change is ever performed by automation
PBR-07 Referral
Travel OS CRMTrigger: Traveler accepts referral offer
- Generate personal code
- Send one transactional email with link
- SMS only via compliant provider with recorded consent; otherwise native share sheet
Stop: One send per referral — no sequence, no marketing subscription
PBR-08 Close & retain
Travel OS CRMTrigger: Stage = Closed
- Clear confirmation reference after retention window
- Keep de-identified outcome for reporting
Tags: pbr:request, pbr:vertical:cruise, pbr:agent:yes|no|unsure, pbr:paid:full|in_progress, pbr:sla:breached, pbr:source:referral, pbr:outcome:offer|none|withdrawn, pbr:referrer
Governance
Permissions, privacy and retention
- Owner: All stages, reporting, retention settings, referral reporting
- Reviewer: Assigned requests, notes, tasks, stage moves; sees confirmation reference
- Member advisor: Own sub-account requests only
- AEGIS OS: Read de-identified fields; write internal-note suggestions; no traveler sends
- Confirmation reference stored in one restricted field; never in notes, tags, email bodies, SMS, logs, exports or AI prompts.
- Service consent and marketing consent are separate fields; this module never sets marketing consent.
- No automatic reservation transfer, rebooking or change — ever.
- Retention: confirmation reference cleared at Closed + configurable window (default 90 days); de-identified outcomes kept for KPIs.
- Dashboards aggregate only; no individual traveler shown in shared reports.
Snapshot
GoHighLevel snapshot mapping
OS HQ
Module definition, version, changelog
OS AEGIS MASTER TEMPLATE
Pipeline, custom fields, tags, forms, workflows, email templates, dashboards
Member sub-accounts
Loaded from snapshot; local SLA, reviewer and branding settings
Never included in the snapshot: Live contacts, Conversations, Appointments, Stripe / payments, Any production data.
Benefits, credits and eligibility belong to each supplier and change over time; their published terms always control. This module describes a review process, not a promise. Back to the Product Tour