Take over a conversation and return it to AI
Understand queued, human-active, and AI-active states, reply safely, and end an operator takeover explicitly.
Humind makes conversation ownership explicit. A thread can be queued for a human, human-active during an operator takeover, or AI-active for Agent handling. The current operator reply flow can perform an implicit takeover when the customer-facing message is accepted.
This guide explains the state transitions, permission and policy gates, internal-note behavior, and the confirmed hand-back action. It is intended for operators and supervisors who need a predictable live-support routine.
How this fits into Humind
Inbox is the operational record of customer conversations. It combines message history, shopper and product context, internal collaboration, human-handoff state, tags, and tickets. Customer replies and internal notes have deliberately different visibility.
A consistent team routine matters more than any individual filter. Agree when to take over, when to leave an internal note, when to create a ticket, and when to return a conversation to the AI so ownership remains clear to every operator.
Before you start
Access: Inbox write is required to reply. Inbox handoff write is required for accepting, stepping in, and resolving. Built-in operator, supervisor, and admin roles include these permissions by default.
- Human handoff is configured when the workflow begins from a queue.
- The operator is signed in to the correct company and has reviewed their availability.
- Read the latest shopper message, collected handoff information, notes, and ticket state.
Step-by-step workflow
Identify the current ownership state
Queued indicates a visitor has asked for a human and no operator has taken over. Human-active indicates a live operator takeover. AI-active indicates the Agent is responsible for future messages. The Inbox list, timeline dividers, composer status, and live events help the interface stay synchronized.
Do not assume that opening a thread claims it. Ownership changes through the handoff actions or a successful customer-facing reply according to the current policy.
Review before replying
Read the pre-handoff answers and recent conversation, check whether another operator is present, and decide whether the shopper needs a reply, an internal investigation, or a ticket. Use an internal note when coordination should remain invisible to the shopper.
If the thread is AI-active, confirm that operator step-in is allowed. A strict configuration rejects unauthorized step-in rather than silently bypassing the rule.
Take over with a customer reply
Choose Reply, write or insert the reviewed response, add any relevant product context, and send. For a queued or permitted AI-active thread, the backend atomically moves ownership to human-active when the reply lands, and the interface mirrors that state immediately.
If sending fails, do not assume the shopper received the message or that takeover succeeded. Resolve the connection, access, or policy error first.
Collaborate during takeover
Use Note for internal context and mentions. Continue customer replies in Reply mode. Update tags and the primary ticket as the issue develops. Other operators can see handoff dividers and ownership context in the timeline.
Keep internal reasoning out of customer replies. If editing an existing operator message or note, confirm the composer restored the correct mode before saving.
Return the conversation to AI
Use the hand-back control in the operator status area. Humind asks for confirmation before changing the thread to AI-active. The send menu can also send and hand back; when a primary ticket exists, the customer-facing label can combine sending with closing the ticket.
After hand-back, verify the timeline divider and state. Future shopper messages can then be handled by the Agent unless a new handoff condition is triggered.
Permissions and important caveats
- Opening a thread and taking it over are separate actions.
- A note never reaches the widget and does not take over the conversation.
- AI-active step-in can return an explicit forbidden error when disabled.
- Send-and-close can affect both conversation ownership and the primary ticket, so review the menu label carefully.
Verify the result
Use this checklist before considering the work complete:
- The operator knew the state and existing owner before sending.
- The successful reply changed the thread to human-active when intended.
- Internal notes remained private and customer replies were visible.
- Hand-back or send-and-close produced the intended AI and ticket states.
Troubleshooting
Step-in is forbidden
Ask an Agent administrator to review Escalation, operator step-in, and your Inbox handoff permission. Do not bypass the policy with another action.
The thread looks human-active for the wrong operator
Refresh the live state, check timeline handoff events and presence, and coordinate through an internal note. Avoid duplicate customer replies until ownership is clear.
Hand-back does not complete
Confirm the action dialog, live connection, and handoff permission. Reload the thread and check whether it is AI-active before retrying or escalating the operational issue.