Module 6 · Live across all 15 verticals

The widget on every page. The brain underneath.

Most chat widgets are a separate channel — a different inbox, a different customer record, a different conversation that dies when the visitor closes the tab. Orbit Chat shares memory with Voice + Recall + Stars. And when the visitor leaves before resolving, Chat hands the thread off to Recall via SMS — so the conversation continues on the customer's terms.

Book a demo → Watch the brain live

Verticals deployed

15 / 15

Same widget engine. Vertical-specific prompt + brand.

First response

~1.5s

Haiku, streamed. Visitor sees typing indicator within 400ms.

Web → SMS handoff

< 8s

From "leave intent" detected to outbound SMS arriving.

Cost per session

~$0.01

Haiku + cached system prompt. Included with + bizbot.

The handoff that nobody else does

The visitor closes the tab. The conversation doesn't.

Watch the same conversation move from web chat to SMS without missing a beat — because the customer record is the same record, not a separate ticket.

Web chat (T+0:00)

siteline.bizbottech.com

Hi, I'm the AI assistant for Davis Roofing. What can I help with?

looking for a quote on a roof inspection. how does it work?

Inspections are $195 (waived if you book the work with us). Takes about 45 min on-site. Can I grab your zip + the best phone for follow-up?

15217 — 412-555-0143

Got it. We service 15217. Want to keep going here, or finish via text? You'll get a confirmation either way.

→ Visitor closes the tab without replying.

SMS thread (T+0:08)

+1 (555) 555-0142 · "Davis Roofing"

Hi, this is Davis Roofing — picking up where we left off online. We can do an inspection at your zip (15217). Best 3 windows this week:
• Wed 9am
• Thu 1pm
• Sat 10am
Reply with one and I'll book it.

sat 10am works

Perfect — Saturday May 11, 10:00am. Address?

412 Linden Ave

Booked. Dave will text 30 min before he's en route. Reply CANCEL anytime if plans change.

→ Same customer record. Same conversation context. Different channel.

What Chat shares with the rest of Orbit.

Most chat widgets are isolated by design — a separate vendor, a separate inbox, a separate customer record. Chat is wired to the same brain everything else uses.

Shared memory reads

Customer profile via phone match if provided, IP/cookie heuristic otherwise. Returning visitor sees: "Welcome back — last time we talked about the roof inspection."
Last interaction across Voice/Recall/Stars/Confirm. Chat doesn't ask for info the brain already has.
Vertical-specific context — SiteLine pulls service catalog + pricing, AgentEdge pulls active listings, etc.

Shared memory writes

Every message appends to customer_profiles.interactions with channel=chat.
Lead capture (phone, email, intent) updates the same row Voice + Recall use — no merge later.
Emits Chat.SessionEnded with the parsed intent for the orchestrator to chain.

Handoff rules

Visitor closes tab with unresolved intent → Chat.SendFollowup action → SMS within 8s.
Visitor explicitly asks to text → immediate SMS handoff, web session pauses (resumes if visitor returns).
Owner is online (in dashboard) → soft transfer with full conversation context, no "let me start over."
1–3★ sentiment detected mid-chat → owner gets a Slack ping with the transcript, not just an end-of-session digest.

Live on every vertical · included with the + bizbot add-on

The widget you already have. Now it remembers.

Chat is included in the + bizbot add-on across all 15 verticals — turn it on once, the brain picks up from there. The widget already lives on every public-facing site we ship. See pricing →

Browse all 15 verticals See Recall (the SMS handoff target) →