Admin Takeover and Smart Handoff
Overview
Admin Takeover lets a human team member pause AI replies for one conversation and continue the chat manually. It is designed for cases where a real person should step in, such as support escalations, sales questions, or sensitive requests that should not be handled only by AI.
The system in WPiko Chatbot Pro is session-based, ownership-aware, and built to avoid reply conflicts between multiple admins or agents.
What Takeover Does
When Takeover Starts
When an Administrator or WPiko Agent opens a conversation in the Mobile App, they can tap Take Over Conversation.
Once takeover is active:
- AI replies are paused for that conversation
- the conversation is marked as LIVE
- the admin who activated takeover becomes the owner of that live session
- only that owner can send human replies through the takeover flow
While takeover is active, WPiko intentionally skips the normal AI response for that conversation so the visitor is only speaking with the human agent.
When Takeover Ends
When the human chat is finished, the same admin can tap Release to AI.
Once released:
- human takeover is turned off for that conversation
- the owner lock is removed
- a release notice is saved in the transcript
- AI becomes available again for the next visitor message
What Smart Handoff Means
Handoff Is More Than Release
In WPiko Chatbot Pro, handoff does not only mean “the human stopped chatting.”
It also means the live-chat context is passed back to the AI so the assistant can continue the same conversation with memory of what happened during takeover.
When the Handoff Happens
After takeover is released, the AI does not immediately send a message on its own.
Instead, handoff happens on the next visitor message.
At that point, WPiko prepares an internal handoff note and includes it in the next AI request before the assistant replies.
How the AI Handoff Works
Which Messages Are Used
WPiko builds the handoff context from the messages exchanged while AI was paused.
More specifically, it looks at:
- user messages after the last synced assistant reply
- admin messages sent during takeover
System takeover notices such as “joined the conversation” and “AI assistant is back” are not used as handoff content.
Short Takeovers
If the live-chat session is short, WPiko sends a compact raw replay of the recent live-chat lines back to the AI.
This gives the assistant a direct view of what the visitor and admin said.
Longer Takeovers
If the live-chat session is longer, WPiko creates a structured summary instead of replaying every line.
That summary can include:
- important user updates shared during takeover
- key admin replies, clarifications, or promises
- open questions that still matter
- the most recent live-chat context before AI resumes
Internal Context Only
This handoff note is internal conversation memory for the AI.
It is used so the assistant can continue naturally and should not be treated as visitor-facing output.
Ownership and Conflict Rules
Single Owner Per Conversation
Each live conversation can have only one active takeover owner at a time.
If another admin opens the same conversation while takeover is already active:
- they can still view the conversation
- they cannot reply through takeover
- they see that the conversation is currently handled by the active owner
Only the Owner Can Release
The admin who activated takeover is also the only one who can release that conversation back to AI.
This prevents accidental release by another team member while a live support session is still in progress.
Conflict Prevention
If a second admin tries to take over or reply to a conversation that is already claimed, the Mobile App returns a conflict response and shows who currently owns the conversation.
Transcript Notices
Join Notice
When takeover starts, WPiko adds a system-style message to the conversation transcript, such as:
John joined the conversation.
Release Notice
When takeover ends, WPiko adds a release message, such as:
John left the conversation. AI assistant is back.
These notices help both admins and visitors understand when the conversation changed from AI to human support and when it returned to AI.
Why Smart Handoff Matters
The handoff system helps the assistant continue from the human conversation instead of starting over.
This allows the AI to:
- remember what the admin already discussed with the visitor
- avoid repeating questions that were already answered
- continue from commitments or clarifications made during takeover
- respond like part of the same conversation instead of a fresh chat
Customizable Takeover Text
The following takeover labels can be customized in the Mobile App settings:
- Header prefix
- Agent joined text
- Agent left text
This lets you match the live-chat wording to your brand voice.
What Visitors See
Header Status
During takeover, the chatbot header can show a live status such as:
Live chat with Maria
Human Identity
The takeover experience can use the admin’s WordPress profile details when available:
- Public display name
- Avatar from the WordPress avatar system
- Initial-based fallback if no avatar is available
Recommended Workflow
Best Practices
Use Clear Display Names
Give each admin or agent a clean public display name so visitors can clearly see who joined the chat.
Keep Human Replies Clear
Because WPiko can replay or summarize admin replies into the next AI request, clear human responses help the assistant continue more accurately after release.
Release Takeover Promptly
If an admin forgets to release takeover, AI will remain paused for that session. Make release part of your support workflow.
Use Takeover for Conversations That Need Human Judgment
Takeover works best when the team uses it intentionally for cases where a real person should step in, then hands the conversation back cleanly when live support is finished.
