Take over a conversation from the AI
Pause automated replies so a staff member can handle a customer’s request.
In this article
Before you begin
Open Inbox and check that you are in the correct workspace. Select the conversation and review its latest customer message before taking an action.
Step by step
- 1
Read the latest request
Review the customer’s problem, previous AI answer and any provided contact details. Confirm you are in the intended conversation.
- 2
Choose Takeover
Use the Takeover button in the conversation header. Check the resulting status so you know staff control is active.
- 3
Reply as staff
Write a clear response, ask only for information needed for the task and send it. Verify the reply appears in the timeline.
- 4
Choose the next owner
Assign the conversation if another teammate should continue. When finished, deliberately close it or Resume the AI as appropriate.
Take over a chat—and resume the bot when the work is done.
Staff handoff lets visitors ask for a person and gives your team a live workspace to answer them. When a staff member takes control, the AI response is paused for that conversation so customers never receive competing replies.
For semantic escalation, open the bot’s Actions & Tools and enable “Allow external Jev triage after privacy review” after reviewing your organisation’s processing requirements. Jev also needs a server API key. In active mode it assesses intent and sentiment; your saved active rules still determine the staff button, contact form and priority. Uncertain or unavailable evaluations fall back to local recognition. Jev does not submit a staff request for the visitor.
Open the bot’s Jev log tab to inspect the latest 100 evaluations, confidence, matched rule, local or Jev source, latency and estimated input cost. Use Refresh after a test message and check the key, approval and mode indicators. Shadow mode records assessments without applying them. The log contains no message text; recorded rule advice can still be suppressed by contact or self-service checks.
Do not forget to resume: a taken-over conversation stays staff-handled until a team member explicitly resumes it. If no staff member is available, configure the offline copy and contact options in Appearance so the visitor receives a clear fallback.
- Enable the workflow: Turn on Staff Console takeover in Experimental settings when you want the visitor-facing CTA/form and automatic routing. A manual take-over from Staff Console always overrides this setting for the current conversation.
- Define when a human should help: In the bot editor, create rules for intents, sentiment, custom keywords, minimum message length and business-hour-only handling. Configure the CTA, immediate form opening, priority and internal tag.
- Be available: Set your live chat name and photo under Settings → My profile, then manage presence and working hours under Settings → Live support. Visitors see availability messaging based on configured staff state and the bot’s custom text.
- Take over in Staff Console: Open the session, review the history and visitor context, then take over. The conversation now belongs to the staff member and the bot stops answering.
- Resume deliberately: When the human work is complete, use Resume in the session. The bot’s normal response path returns and the visitor sees the configured resume notice.
Good to know
Taking over prevents the AI from competing with your response in that support session. Closing the page is not the same as resuming the AI.
Check the result
Check the conversation status and timeline after the action. When testing, use a separate visitor browser so you can see both sides.
Questions & troubleshooting
The AI does not answer after my reply
Check whether staff control is still active. Use Resume only when you want automated support to continue.
Rate this guide on this device. Ratings are not sent to Corthex.