Capabilities by vertical

/ What each vertical can do, and how it differs between the widget (native UI) and the API (signals you render).

At a glance

CapabilityWidgetAPILink
Product / room cards✓ NativeYou build it
Calendar picker✓ NativeYou build it
Live data✓ Built in✓ Built in
Payment redirect✓ CTAYou build it
Human Desk tickets
Cancellation / retention✓ NativeYou build it + webhookText only
Escalation✓ Webhook
Medical guardrail✓ Chip✓ Metadata✓ Text
Cross-session memory✓ Scale+✓ Scale+✓ Scale+

Retail & ecommerce

FeatureWidgetAPI
Product cardNative inline cardsuggestedProductId, you render it
Order statusLive, pulled when they askYou push order data to us first
Return ticketInline form, becomes a ticketescalate, then webhook + ticket
Discount revealCopyable chip in chatdiscountEligible in session context
Low stockInline urgency textInventory via live data

Digital services / SaaS

FeatureWidgetAPI
Plan contextBilling answers from live dataInject the plan from Stripe / Polar at start
Cancellation flowNative in-chat sequencecancellationIntent webhook
Upgrade CTAButton in chatintent === feature_blocked
Bug report formInline form, tagged ticketescalate webhook to Linear / Jira

Wellness

FeatureWidgetAPI
Class bookingInline picker and confirmbookingContext, you submit to Mindbody
Medical guardrailVisual chipmedicalTopic metadata
Membership freezeInline formWebhook to your membership system
Credit balanceShown in chatLive data

Hospitality

FeatureWidgetAPI
Availability calendarNative inlineYou build the UI from bookingContext
Room cardsPhoto, rate, amenitiesYou render from your PMS data
Payment redirectPre-filled checkout CTAYou own the payment flow
Emergency escalationHard escalation cardurgency critical webhook, first