Confidential · © 2026 Space-O Technologies Inc. · Prepared exclusively for DMA. Please do not copy, save or share.

Section 10 · Human Sales Team Superpowers

10.1Live human takeover

Built in the POC
No.
10.1
DMA's reference
Decision Book p.22
Phase
Phase 1
Autonomy
L3 · Act within rules
DMA's decision
Yes

What DMA asked for · Decision Book p.22

A salesperson can jump into the chat with the full history, so the prospect never repeats themselves.

Why it matters to DMA: Hot leads must never feel dropped between the AI and a person.

In our words, from DMA's Product Decision Book v3, page 22.

How we do it

  • Live chats on the dashboard lists every open website chat: the page it started on, the latest line and a Join button. A hot-lead email carries a signed link that opens the same chat.
  • Joining shows the whole conversation so far, so the person picks up mid-conversation and the visitor never repeats themselves.
  • The moment someone joins, the AI stops replying to that visitor, and the visitor sees that a person from DMA has joined. Everything the person writes is stored in the same conversation.
  • When the visitor asks for a person, the chat says someone is joining and a case goes to the person on call on DMA's roster.

The flow

It plays on its own while it's on screen; hover or use the controls to pause or step through.

Live chatAI is talkingLive chatspage, latest line, JoinHot-lead emailsigned Join linkPerson joinssees the full historyAI pausesfor this visitorVisitor sees"a person has joined"
Step 1 of 5

A chat is live

The AI is talking to a visitor on DMA's site.

  • Screen
  • Person
  • Rule in code

Where the data goes

The same six stages on every page. Nothing reaches Nutshell except through the write gate.

  1. 1Website chat

    Source

    The visitor's messages, and now the person's.

  2. 2Sync

    Copies Nutshell changes into the bridge database

    Not involved.

  3. 3Bridge database

    A copy of the CRM data, plus what the AI works out

    One conversation: the AI's lines, then the person's; the takeover time is recorded.

  4. 4AI

    Claude models, only through DMA's own gateway

    Paused for this visitor from the moment a person joins.

  5. 5Write gate

    The only way back into Nutshell: checked, approved when needed, sent once

    The lead and summary go to Nutshell as usual.

  6. 6Nutshell

    The system of record

    The rep sees the whole conversation.

The tables behind it

Drawn from the POC's database catalogue: structure only, no data.

conv.conversationsPKiduuidchanneltextstagetextIDagent_version_iduuidhuman_takeover_attimestamplast_message_attimestamp+ 16 more columnsconv.participantsPKiduuidFKconversation_iduuidroletextuser_iduuidIDagent_iduuidcreated_attimestamp+ 2 more columnsconv.messagesPKiduuidFKconversation_iduuidseqintegerIDparticipant_iduuidsender_kindtextsent_attimestampIDdecision_iduuidIDagent_version_iduuid+ 13 more columns

PK primary keyFK reference the database enforces (solid line)ID reference kept by id (dashed line)

TableWhat it holdsColumns
conv.conversationsThe chat, including when a person took over.22
conv.participantsWho is in the chat: the visitor, the AI, and the person who joined.8
conv.messagesEvery line, from all three, encrypted.21
How the tables connect (7)
ColumnPoints toKept by
conv.conversations.agent_version_idagent.agent_versionsThe application (by id)
conv.participants.conversation_idconv.conversationsThe database (foreign key)
conv.participants.agent_idagent.agentsThe application (by id)
conv.messages.conversation_idconv.conversationsThe database (foreign key)
conv.messages.participant_idconv.participantsThe application (by id)
conv.messages.decision_idctrl.decision_logThe application (by id)
conv.messages.agent_version_idagent.agent_versionsThe application (by id)

Worked example

Synthetic demo data: every name, business and number is made up.

A takeover, screen by screen

1 / 3

What you see

1.Every open chat, with a Join button

The team sees the page each chat started on and its latest line.

localhost:13301/live-chats
Live chats: every open website chat.
Callout 3

What happens in the system

  • Bridge databaseconv.conversations

    Open website chats, read live from the bridge database.

A synthetic takeover on the BrightSmile Dental demo site.

What each side sees

MomentVisitorDMA's team
BeforeThe AI assistant, with "Talk to a person" always on screenThe chat on Live chats, with a Join button
Join"Josh from DMA has joined the chat"The full conversation so far
AfterJosh's replies in the same windowThe AI stays quiet for this visitor

In the running POC

localhost:13301/live-chats
Live chats: every open website chat.

1 / 3Live chats: every open website chat.

  1. 1The page the chat started on.
  2. 2The latest line.
  3. 3Join in one click; the AI pauses for that visitor.

Dashboard · Live chats. Captured from the running POC on September 25, 2026; synthetic data.

See it live

Opens the exact screen in the running POC, in a new tab.

OpenWhereWhat to try
Live chatsDMA AI dashboardOpen chats and the Join button.

Status

Built in the POC

Built in the POC. This capability runs in the POC today, on synthetic data, end to end.

10.1 Live human takeover · DMA AI proof