Choose a business job, then open the replay that shows the operator move and the expected impact. Live channel setup, consent, permissions, and provider readiness remain explicit where they matter.
◎Grounded answers
Answer from your business, not a generic script
Use your pages, products, campaigns, and verified order history. When a private record is not verified, ask for another identifier instead of guessing.
Proof: Source citations, private-record checks, and a safe handover when the source is not enough
See the grounded-answer demo →
↗Leads, bookings, and handover
Move interest to a booking or a prepared person
Capture a lead in the conversation, guide availability and booking, or give staff the context and SLA they need to take over. An explicitly enabled public mode can also answer first-time visitors within tenant-wide and per-user caps.
Proof: Lead capture, availability, shared queue, ownership, SLA-aware handover, and capped public replies
See the booking and handover demo →
↳Chat commerce and checkout
Turn “I want it” into a confirmed order
Recommend the right product, read back the basket, verify masked details, and take the customer to an exact-amount checkout in the conversation. The public replay uses Stripe test mode; tenant-owned payment adapters can be enabled after credential and readiness checks, with the paid state returned to the ledger.
Proof: Catalog matching, basket integrity, Stripe test checkout, payment-provider readiness, and payment-state confirmation
See the chat-checkout demo →
▤Unified ledger and analytics
Give chat, online, and counter sales one record
Connect Shopify, chat orders, and in-store/POS sales so staff spend less time reconciling and can measure the outcome of each action.
Proof: Draft import and publish review, one sales ledger, and outcome Stats
See the unified-ledger demo →
↻Retention, campaigns, and loyalty
Give the next visit a reason to happen
Find the next opportunity from purchase, visit, response, and member context. Consent, quiet hours, and frequency are checked before approval; stale offers and duplicate coupon use are blocked.
Proof: Follow-up drafts, campaign expiry, consent/frequency gates, member context, and coupon records
See the repeat-visit demo →
◌Photos, receipts, and voice
Let customers ask in the way they actually do
Turn photos, receipts, and voice notes into a useful next action. When confidence is low, ask or hand over instead of inventing an answer.
Proof: Catalog matching, receipt draft, voice transcription, and issue handover
See the multimodal demo →
☑Operator control and AI governance
Give staff one safe move after every suggestion
Use guided setup, capability-level enable/disable and history, then keep the AI brief, ownership, approval, close summary, and outcome in one operating loop.
Proof: Capability state, change history, shared inbox, assignment, approval, close summary, and Stats
See the operator-console demo →
✦Your knowledge, your AI, your creative
Turn business knowledge into work staff can run
Bring in website knowledge, use the standard AI or your own endpoint, and review product or marketing creative before anything is published.
Proof: URL ingestion, source review, BYOAI connection, and reviewed creative publish gates
See the AI-features demo →
◎Instagram DMs
Bring another customer door into the same decision loop
Instagram DMs use the grounded answer and human-handover flow. The public simulator sends nothing; live use needs a professional account, Meta permissions, webhook setup, and the 24-hour window. Rich content falls back to text.
Proof: Instagram-style DM replay, shared answer engine, handover preview, and an explicit live-readiness boundary
Try the safe Instagram DM simulator →