Take over from the AI, and hand it back

The badge at the top says who is answering right now, and one button moves the conversation between the AI and a person.

Quick start

  1. Open Inbox and click a conversation. Owners, admins and agents see this control.
  2. Read the badge at the top — it says who answers the customer's next message.
  3. Click Take over to answer as yourself. On the web, the chat is also assigned to you.
  4. Reply as usual. Your reply goes to the customer; the AI stays quiet while you hold it.
  5. Click Return to AI when you are finished — in the app, Hand to AI.

Watch out

  • AI replying describes this conversation only. The AI also needs the workspace's and the channel's AI switches to be on.
  • In the app, taking over does not assign the chat to you. On the web it does.
The AI replying badge, with Take over next to the AI agent picker.
Human replying after Take over, with Return to AI in its place.
Details

Getting here

Inbox → open a conversation → the badge and the button at the top. In the app: the button sits in the conversation header, and the same badge is in the bar just under it.

Before you start

  • An owner, admin or agent can move a conversation between the AI and a person. A viewer cannot.
  • Your access has to cover this conversation. If you cannot see it, you cannot take it over.
  • There is nothing to take over on a channel with no AI agent — the badge says so.

Fields

AI replying
The AI answers the next customer message, as long as the workspace's and the channel's AI switches are on.
AI is paused.
The AI stays quiet until a person replies or hands the conversation back, for example after the customer says they have paid and a person has to check it. The badge does not say why it stopped. A hand-off to a person reads Human replying instead.
AI paused by workflow
The AI stays quiet: a workflow's pause step is holding it. Nobody was alerted.
AI waiting — a person replied
The AI stays quiet for a while because a person answered on this conversation.
Human replying
A person owns the conversation: somebody took it over, or the customer, the AI or a workflow handed it to a person. The AI does not answer at all until somebody clicks Return to AI.
No AI on this channel
No AI agent is attached, so nothing automatic will answer.
Limits: The button is still there; pressing it only records that a person holds the conversation.
Owned by another app
Another connected app holds this conversation.
Limits: No button. Reclaiming it is done in that app, not here.

How it works

  • Take over hands the conversation to a person and stops the AI answering. On the web it also assigns the conversation to you and cancels any reply the AI was about to send; in the app it changes who answers only.
  • A line is added to the conversation — {name} took over from AI — so the history shows the handover.
  • Return to AI gives it back. It clears both pause reasons at once, whichever was showing, and adds {name} returned the conversation to AI.
  • Handing back also ends the quiet period a person's reply started. If the customer's last message is still unanswered and less than a day old, the AI then answers it. It stays quiet when a workflow is waiting on that message, when the message has no text for the AI to read, or when an AI switch or the messaging window stops the reply.
  • Resume AI is the same button under a different name. It appears when the badge says the AI is paused or waiting, because resuming is the useful move there.
  • When the customer asks for a person, when the AI's own answer hands them to one, or when a workflow's Escalate step runs, the conversation becomes a person's. The badge then reads Human replying, and the button Return to AI. AI is paused. is a hold the system sets, for example after a customer says they have paid; the badge does not say why.
  • When a person is asked for, whoever is notified sees it in up to three places. They are a push on the phone, a desktop notification if the browser has them turned on, and a row in Notifications that reads Escalated to a human. On the web, Notifications is the bell at the top of the screen, and its number counts the rows still under New; in the app it is the Notifications tab. Opening the row opens the conversation. A conversation handed to a person stays theirs until somebody clicks Return to AI; opening the row does not end it.
  • Inchat reminds the team when a conversation is waiting on a person and nobody has answered. One case is a conversation handed to a person, or held after a payment claim, that nobody has answered yet. Another is a conversation somebody was already told about, still unanswered. The third is a customer message during the quiet period after a teammate's reply, still unanswered once that period ends. The first reminder comes 30 minutes after the wait starts, then one every 60 minutes, at most 4 in all. Each one goes to every owner and admin, and to the person the conversation is assigned to if there is one, as a push and in Notifications. There a conversation's reminders share one row, which says which reminder it is and how long the customer has waited; archiving that row archives them all from your list. While the conversation is assigned and the assignee's own last reply is less than 4 hours old, only the assignee is reminded. A reply from anyone else does not narrow it: the whole team is still reminded. A person's reply, or handing the conversation back to the AI, ends the reminders. So does archiving one of its reminder rows, when the person the conversation is assigned to or an owner archives it; anyone else who archives their own row only clears it from their list. In a workspace with no owner, an admin's archive counts as an owner's. No reminder starts for a wait older than 24 hours. A conversation has one run of reminders at a time: a new message from the customer while it runs does not start another or restart the count. If nobody has answered after the last reminder, the workspace's owners alone are told again; if it has no owner, its admins are. They get a push and a row in Notifications that reads Customer still unanswered. It comes an hour after the last reminder, then every 24 hours counted from when the wait started, until the wait ends. An owner stops them by archiving the newest Customer still unanswered row; in a workspace with no owner, an admin does. When more than five conversations are waiting at once, the team gets one reminder that says how many, instead of one each.
  • AI paused by workflow starts when a workflow's Pause AI / Unassign step runs. Nobody is alerted for it.
  • On a conversation handed to a person, your reply keeps it yours: the AI does not answer again until somebody clicks Return to AI. On the payment hold, sending a reply clears AI is paused., and the AI then waits instead, because a person has spoken on the conversation.
  • On a conversation the AI still owns, after a person replies the AI waits 4 hours before answering again. Resume AI ends the wait immediately.
  • Taking a conversation over never clears a workflow's pause. Return to AI, Resume AI and picking a named AI agent do, on purpose.
  • Owned by another app shows no button. Reclaiming a conversation from another app is done in that app, not here.
  • The badge, the button and the composer all read the same state, so one click updates the whole conversation at once.
  • The composer has its own control, on the web and in the app. It is a Who replies menu, and its button shows who replies now: AI agent or My reply. While the AI is answering, a round stop button named Take over from AI sits beside it. My reply and the stop button do what Take over does. The other item gives the conversation back. On the web it reads Return to AI, or Resume AI when the AI is paused or waiting. In the app it is AI agent, with Return to AI or Resume AI under it.
  • The pause is per conversation. It says nothing about any other chat, and it does not switch the AI off anywhere else.
  • The workspace's AI switch is under Settings → AI Agent, and each channel has its own under Settings → Channels.
  • The agent's Let the AI read this contact's CRM details switch is off until you turn it on. With it on, the AI reads the contact's lifecycle stage, tags, custom fields, channel, assignee, marketing consent, last customer message time and source ad. It does this when it answers from the knowledge base, not on greeting turns. It reads no phone number, email or name from this. A contact's open deal is read only when the agent's deal action is on.
  • Which stages, fields and tags it may change is set on the agent's Actions page, not here.

When it fails

  • Could not update thread ownership. — nothing changed. The badge goes back to what it was, and the AI is in the same state as before.
  • Could not resume the AI. — the quiet period was not ended. The chat stays as it was.
  • A conversation owned by another app is refused outright; the badge stays Owned by another app.
  • A member whose access does not cover this conversation cannot change its owner, even from inside it.
  • On the web, a viewer sees no badge and no button at all. In the app a viewer sees who is answering, but gets no button.
  • When the channel has no AI agent, the badge reads No AI on this channel. The button is still there; pressing it marks the conversation as held by a person, and on the web assigns it to you — no AI was answering to be stopped.

Limits

  • Taking over does not stop a workflow that is running on this conversation. Stopping one is done from Active workflows.
  • Taking over does not close the conversation, and it does not tell the customer anything.
  • Pausing or resuming the AI here changes this one conversation. It is not a switch for the workspace, the channel or the AI agent.
  • Taking over is not a way to stop the AI everywhere. A workspace-wide or channel-wide stop is a setting, not this button.
  • Handing back clears the two pauses only. It does not change the assignee, so a chat a web takeover put in your name stays there.
  • The badge describes who answers, not who is assigned. A conversation can be assigned to you and still be answered by the AI.

Best practices

  • Read the badge before you type. A conversation that says AI replying may answer the customer a second time after you.
  • Take over before writing anything difficult, so the AI cannot speak over you mid-conversation.
  • Hand back when you are done. A conversation left in a person's hands stays quiet until somebody notices it.
  • A conversation handed to a person reads Human replying before anybody has answered. Treat the AI handoff view as a queue: its rows, marked Needs you, are waiting for a person.
  • If the badge says No AI on this channel and you expected an AI, the fix is in the channel's settings, not in this button.

Use cases

  • Sarah Chen asks something the AI keeps answering wrongly: take over, answer, hand back.
  • A customer types "agent please": the badge turns to Human replying, the conversation shows in AI handoff, and whoever is on shift picks it up.
  • A workflow paused the AI mid-flow and the customer has gone quiet: Resume AI puts it back on duty.
  • You answered one message on a conversation the AI owns: the badge reads AI waiting — a person replied, so the AI does not talk over you.
  • A complaint arrives at 9pm: take over, promise a reply in the morning, and leave it in your name overnight.

FAQ and troubleshooting

Why is the AI paused on this conversation?
One of three things: the customer says they have paid and a person has to check it, a workflow's pause step ran, or somebody replied by hand. A conversation handed to a person — by the customer, the AI's own answer or a workflow's Escalate step — is not paused but a person's, and reads Human replying. The badge names which.
How do I get the AI answering again?
Click Resume AI, or Return to AI when a person holds the conversation. Both clear the pause. If the customer's last message is still unanswered and less than a day old, the AI then answers it. It stays quiet when a workflow is waiting on that message, when the message has no text for the AI to read, or when an AI switch or the messaging window stops the reply.
Does taking over stop a workflow that is running?
No. A running workflow carries on. Stop it from Active workflows in the contact panel if it should not continue.
Does pausing the AI here switch it off for everyone?
No. It is one conversation. Every other chat keeps whatever it had.
Why does the composer not show the stop button?
The round Take over from AI button is shown only while the AI is the one answering. When a person already holds the conversation, or the AI is paused or waiting, there is nothing to stop. The Who replies menu and the badge at the top, with its own button, are still there.
I replied and now the badge says the AI is waiting. For how long?
4 hours from your reply, unless somebody ends it sooner with Resume AI.
Does taking over assign the conversation to me?
On the web, yes: taking over makes you the assignee as well. In the app it does not, so assign the chat separately if it should be yours. Handing back to the AI never changes the assignee.

Reading this with an AI assistant? Plain Markdown version.