Talk track

1. The generic shape underneath this scenario is 'a customer is waiting on something, it completes on a date, and there's a paid option to make it happen sooner' — it's the storefront half of a pair with scenario 2, which is the same proactive posture applied to something going wrong instead of something being sped up. Naming that pairing out loud is what turns two demos into one platform story.
2. Watch apply_shipping_upgrade: it only ever fires after the customer has explicitly and verbally agreed to the upgrade and its price, gated by a Workflow node. That's the first place in the whole kit to point at when a buyer asks how a paid, irreversible action is controlled — every later scenario's gate (rebooking, card freeze, safeguarding escalation) is the same pattern.
3. The reusability proof lives in the vertical switcher, not in a slide: flip from Northwind Outdoors (retail parcel) to Kestrel Comms (telco SIM activation) live, using the same schema, the same agent config, and the same three tools — lookup_order, get_shipping_upgrades, apply_shipping_upgrade. The activity panel keeps logging the same event types under the new skin, which is the tell that nothing but data changed.
4. The value story is deflected contact plus attached upgrade revenue, both live from value_rules for whichever vertical is on screen — call out that it's two different buyer conversations in one number: a support-cost conversation and a revenue-attach conversation, and GTM enablement is what makes a seller comfortable running both without switching decks.

Discovery questions

• How many 'where is my order' or 'where is my delivery' contacts do you handle today, and through which channel — phone, chat, app?
• Do you already offer a paid express/priority option at this stage of the journey, and if so, what's your current attach rate?
• Where in your business would a paid, customer-facing action need an explicit, auditable 'yes' before it fires — and how is that enforced today?
• If the same underlying order/case data had to serve two different brands or business lines, is that a realistic need for you, or a single-brand problem?

Objection handling

If a tool call fails or times out

1. lookup_order returns no match or times out: don't let the agent guess or invent an order — have it say it's having trouble finding the order and offer to check the reference again, while you confirm live in the storefront/admin view that the case actually exists for whatever reference was used.
2. get_shipping_upgrades comes back empty: this is a valid state (some orders genuinely have no upgrade available), not a bug — say so plainly rather than treating it as something broken, and if it's clearly the wrong case for the demo, reset and pick a case known to have an upgrade available.
3. apply_shipping_upgrade fails after the customer has already said yes: don't have the agent re-ask for confirmation — that's the one thing that must not repeat. Acknowledge the delay, retry once, and if it still fails, apply the upgrade from the admin panel and tell the room plainly that's what just happened rather than pretending the call succeeded.