Travel & Hospitality AI agent · Ancillary
Upsell & Ancillary-Offer AI Agent
Draft ancillary offers from the set your commercial team publishes, show the price and terms with the offer, and let the guest's yes be the only thing that adds a charge.
- Typical delivery
- 4–6 weeks
- Deployment
- Your stack
- Owner releases
- Opt-in only
- After launch
- Agent Care
What this agent does
Offers proposed, nothing added
In
- 01
Where an offer starts, ingest the booking, the rate or fare rules and the published offer set.
- 02
When source fields differ, normalise them so each offer carries the record it was drawn from.
Reason
- 03
Where a guest is eligible, draft an offer from the published set, with its price and its terms.
- 04
When the offer is shown, the amount, what it covers and whether it refunds are shown with it.
- 05
Where the journey includes air, the offer is marked as one that may not appear pre-selected.
Decide
- 06
When a charge cannot reasonably be avoided, flag it as mandatory, whatever the label on it says.
- 07
Where a saving or a was-price is implied, refuse it unless a real prior price substantiates it.
Out
- 08
When a guest accepts, record that acceptance per item, with the words and the price they saw.
- 09
Where a write is needed, execute only inside the approval boundaries agreed during implementation.
Product statement
The agent proposes an offer; the guest's own yes is what adds anything, and the operator stays the one charging.
Example workflow
One offer, booking to acceptance
- 1Booking receivedReservation, PNR, folio or a commerce session in progress
- 2Eligibility assembledRate or fare rules, inventory, the published offer set and what the guest already holds
- 3Offer draftedOffer, price shown, terms, confidence
- 4Controls appliedOpt-in checks, avoidability checks, reference-price substantiation and confidence threshold
No human action required
Stages 1 to 4 run unaided, and nothing is shown or charged at any of them — the agent is drafting, and the owner's lane opens at the confidence gate.
Goes to the offer owner to release.
Adds a pricing-lead read first.
Owner releases
The offer is held with its price, its terms, its flagged lines and the confidence.
Release · Adjust · Send to pricing review
Released — the guest chooses
- 6Commerce systems updatedOnly where write access and approval policy allow it
- 7Outcome evaluatedAdjustment distance, flagged-offer outcomes, opt-in quality and post-sale refunds
Adjustments
Every owner adjustment is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required
8 items
- Adding a charge to a booking the guest did not choose.
- Pre-selecting or defaulting any optional item.
- Deciding whether a fee is mandatory or optional.
- Publishing a was-price, a saving or a discount claim.
Automation boundary
Agent acts unaided
- ✓Draft an offer from the published set for a single booking into the review queue.
- ✓Show the amount, what it covers and its terms, at the offer for the named owner.
- ✓Record an acceptance per item, in the words the guest saw.
- ✓Flag what a person must weigh, and hold the offer for them.
Any write happens inside the boundaries agreed at implementation, never ahead of approval.
- Setting which items may be sold, and at what price.
- Bundling an air service into a booking on its own.
- Explaining what a fee covers or whether it refunds.
- Changes to offer, disclosure or acceptance rules.
Example output
One offer, annotated
Everything the agent offers is attached to the published item it was drawn from.
Ancillary offer output · single booking
Illustrative example- Booking
- Two-night stay
- Offer shown
- Late checkout, refundable until the night before arrival
- Price at offer
- $45.00
- Source of record
- Published offer set
- Confidence
- 90%
- Attribution
- Property and offer owner
As received
Taken from the published offer set and the rate rules on file — nothing on this side is written by the agent.
Records used
- Published offer set
- Rate rules on file
- Prior sold price
Why this wording
It carries the price and the terms at the offer, not at the payment screen.
What the score decides
Below the configured threshold the offer picks up a pricing read before the owner sees it.
Action
ReleaseAdjustSend to pricing reviewValue
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value lands
Value 01 – 04
Every booking
From the published set
Offer from the published set
Draw on the rate and fare rules on file and the offer set your commercial team already publishes.
Offer it, never pre-select it
Routine bookings arrive with an eligible offer already drafted and already priced.
Report opt-in quality, not attach rate
The page reports how many acceptances were affirmative and taken item by item, because an attach rate says nothing about how the yes was obtained.
Build an evidence trail
The offer, the price shown with it and the guest's own acceptance stay on the record.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Booking and commerce
- Opera Cloud
- SynXis
- Amadeus
- Sabre
- Shopify
Payments
- Adyen
- Stripe
- Braintree
- Worldpay
Merchandising
- Plusgrade
- Nuvola
- Offer and upsell engines
Agent
Upsell & ancillary offers
- Reads the booking
- Drafts the offer
- Holds for release
Messaging and CRM
- Braze
- Salesforce
- Twilio
- Iterable
Observability & evaluation
- OpenTelemetry
- Langfuse
- Supported monitoring/evaluation sources
Integration availability depends on the client's existing systems and API access.
Agent controls
Six layers between the model and the guest
The layers sit one inside the next. What none of them catches is in the map below.
L6 · Outermost — last line of defence
Inward → L1 · closest to the model
- L1 – L2
- Test whether an offer may stand
- L3
- Puts the display in an owner's hands
- L4 – L5
- Keep the offer and the price shown with it
- L6
- Falls back to the published offer set when signals degrade
How Nestack evaluates it
Evaluate the offering workflow — not only the line the guest taps.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — the offer the guest sees
- E1Final-output evaluationDid the offer carry its price, its terms and nothing pre-selected?
- E2Step-level evaluationDid the agent read the right booking, rate rules and published offer set?
- E3Tool evaluationDid it read and write the correct booking and the correct item?
- E4Confidence calibrationDo low-confidence offers actually attract more owner adjustments?
- E5Slice evaluationHow does performance change across specific offer types?
- E6Business outcomeHow many offers needed an adjustment or a refund after the sale?
Floor — the charge the operator answers for
Failure modes
Where each failure originates in the agent
Seven ways an offer goes wrong, placed at its stage.
Agent lifecycle
Direction of processing →
01 · Retrieval
1 mode
- CO-03
Superseded offer set
An offer is drawn from a set the commercial team has replaced.
Stage gathers
Bookings, rate rules, inventory and the offer set
02 · Reasoning
2 modes
- CO-04
Unsubstantiated saving
A comparison is written that no prior price supports.
- CO-06
Mandatory sold as optional
A charge the guest cannot avoid is offered as a choice.
Stage proposes
The offer the guest reads and accepts
03 · Tool / write
2 modes
- CO-02
Item added without a yes
A charge reaches the folio with no acceptance behind it.
- CO-05
Terms held back to checkout
Price and terms appear only once payment is reached.
Stage writes
Only where write access and approval policy allow it
04 · Output
1 mode
- CO-01
Pre-selected optional item
An optional item is presented to a guest already ticked.
Stage returns
The offer the owner releases and guests see
05 · Change / Version
1 mode
- CO-07
Silent offer regression
A model or rule change widens what the agent will offer.
Stage tracks
Model, prompt, offer set and disclosure config
- Sev-1 · a charge lands without a yes
- Sev-2 · a wrong price reaches a guest
- Sev-3 · offer set degrades, offer to review
Affected slices
Overall quality can hide one bad cohort
A lift figure means little without the base rate underneath it. The baseline here is a single-item room offer The cohorts that carry it are named, not averaged away Nestack reports it by slice rather than in aggregate..
Slice performance — reported separately, not only in aggregate
Illustrative example| Slice | Failure rate | Lift | Lift vs. threshold | Status |
|---|---|---|---|---|
| Air-inclusive itineraries | 3.5% | 3.2× | Review | |
| Recurring and renewing add-ons | 2.6% | 2.4× | Review | |
| Comparison and saving claims | 2.1% | 1.9× | Watch | |
| Single-item room offers | 0.8% | 0.7× | Normal |
Bar: owner-adjustment-rate lift vs. single-item-offer baseline · scale 0–4.0× · tick marks the 2.0× review threshold
2 of 4 slices over threshold
Evidence-linked improvement
The cycle closes on a case, not a call
The cycle ends in a regression case, not in a meeting about what happened. That suite is what the next offer shown to a guest is measured against.
Improvement cycle · five stages
Switchback — the path turns at Improve and returns at Learn
- 01
Detect
Owner-adjustment rate rises in an offer slice.
- 02
Diagnose
Read the offers that were charged against the ones that were declined, until the cause narrows to one.
- 03
Improve
Every change is versioned against the offers that exposed it.
- 04
Verify
A failing case holds the release back.
- 05
Learn
The case joins the suite for good, and the offer rules are revisited.
Learn → Detect
The return edge. What comes next is tested against a suite that grew.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, offering workflow, evaluation, integration, then production validation and handover.
Workstream
Week 1Week 2Week 3Week 4Week 5Week 6
- 01Offer and acceptance workflow discovery and boundaries.Week 1
- 02Booking, commerce and payment assessment.Week 1, Week 2
- 03Offer-set, disclosure and jurisdiction rule mapping.Week 1, Week 2
- 04Booking ingestion and normalisation.Week 2
- 05Offer logic and published-set binding.Week 2, Week 3
- 06Confidence scoring and acceptance routing.Week 3
- 07Offer-owner release workflow.Week 3, Week 4
- 08Commerce and payment integration.Week 5
- 09Opt-in and disclosure cases.Week 4, Week 5
- 10Guardrails and acceptance controls.Week 4
- 11Offer-trail instrumentation.Week 5, Week 6
- 12Deployment, documentation and Agent Care handover.Week 6
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel
Final scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
| Capability✓ in scope · — not at this tier | PilotOne property, one channel | ProductionProduction commerce systems | AdvancedMultiple markets / brands |
|---|---|---|---|
| Introduced at Pilot | |||
| Offers from your published set | ✓ | ✓ | ✓ |
| Owner release | ✓ | ✓ | ✓ |
| Offer-quality baseline | ✓ | ✓ | ✓ |
| Introduced at Production | |||
| Reporting by offer type | — | ✓ | ✓ |
| Approval workflow in your systems | — | ✓ | ✓ |
| Approved write-back | — | ✓ | ✓ |
| Commerce-platform integration | — | ✓ | ✓ |
| Introduced at Advanced | |||
| Multi-market disclosure rules | — | — | ✓ |
| Multi-stage commercial approvals | — | — | ✓ |
| High offer volume | — | — | ✓ |
| Multi-market offer controls | — | — | ✓ |
| Build price | From $5,000 | From $8,000 | Custom quote |
- Final build price
- Confirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.
- Separate from build
- Build pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bring
We build with it
01Your published offer set and its prices
→Booking ingestion and offer-set mapping
Week 102Offers you have already sold
→Offer baseline, eligibility logic and published-set binding
Week 203Your disclosure rules and what may be offered
→Offer-set, disclosure and jurisdiction rule mapping
Week 104Access to relevant APIs, feeds or exports
→Booking, commerce and payment assessment, then integration setup
Week 205Offers you would not want charged
→Opt-in cases and the evaluation suite
Week 406What no offer may add on its own
→Confidence scoring, offer routing, guardrails and acceptance controls
Week 307Named offer owners to release offers
→Acceptance workflow, then pilot and production validation
Weeks 5–6
Nothing else is required
Deployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
The bands follow the real work, which is why evaluation and pilot share the fifth week.
Phase
W1
W2
W3
W4
W5
W6
- DiscoveryW1
- BuildW2 – W3
- EvaluateW4 – W5
- Pilot & LaunchW5 – W6
Week focus
W1Offer workflow discovery, disclosure mapping and the automation boundary
W2Source integration and the offer baseline
W3Offering workflow, confidence logic and acceptance controls
W4Opt-in cases, disclosure guardrails and failure-mode testing
W5Commerce-platform integration, pilot offers and targeted corrections
W6One selling period run under the commercial team, then handover
- Reading the band
- A bar covers the weeks its work is named in, and nothing else. The week 5 overlap is real, not padding.
- At the end of W6
- The period closes validation and Agent Care assumes monitoring.
- Duration
- Six-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Travel & Hospitality AI agent
Build an upsell agent that offers, and lets the guest be the one who adds.
The vacatur everyone cites struck a rule on a procedural ground and left the statute, the older rule and the general deception authority exactly where they were — and in air transport an opt-out ancillary charge is a violation on its face. Send us your offer set, your disclosure rules and the markets you sell into, and we will tell you which of your current defaults has to go before anything ships. Then we build the boundary around what is left.
- Typical delivery
- 4–6 weeks
- Deployment
- Your offer set
- Owner releases
- Opt-in only
- After launch
- Agent Care available
Nestack Agents · Upsell and ancillary
AGT-TH-08 · Agent Care available after launch