Handoff
What happens when the AI agent hands a conversation to your team, on every channel: live chat, what the AI agent tells the customer, the live chat timeout, contact details asked for first, and replies after the handoff.
When the AI agent hands a conversation to your team, it tells the customer what happens next. All of that is set per business in Settings -> Automation -> Handoff, or through Copilot.
Where the team replies
Octocom decides this; you can't change it per conversation.
| The conversation is on | And | The team replies |
|---|---|---|
| Web chat | Live chat is on and an agent is available now | In the chat (live chat) |
| Web chat | Live chat is off, or nobody is available | By email |
| By email | ||
| WhatsApp, Messenger, Instagram | In the same channel |
An agent counts as available when they're marked available, within their working hours (if your organization uses working hours) and active in the dashboard (if it uses dashboard activity). If an assignment rule sends the conversation to a team or person, only they count. See Live chat for how a chat moves between the widget and email afterwards.
If the business hands off to an external help desk (Ticket Routing), its settings decide instead: live chat runs through that provider during its support hours, or handoffs create tickets there.
Live chat
- Live chat: whether a team member can join web chats after a handoff. It applies to every web chat configuration of the business.
- Expected response time: how long customers usually wait, in minutes. The AI agent tells them. Empty means "as soon as possible".
- What to tell the customer: guidance for the AI agent when an agent will join the chat.
- Move to email after: how long a waiting chat stays on web chat before the customer is told the team will reply by email. Only for customers with an email address; the chat isn't closed. Empty means 10 minutes.
- Customer waiting alert: notifies your team once when a live chat customer is still waiting. See Notifications.
When live chat runs through an external provider such as LiveChat, the response time, instructions and timeout still apply (the timeout until an agent joins there), but the customer waiting alert doesn't; use the provider's own alerts.
The page shows whether live chat would be offered right now and how many agents are available.
When the team replies later
What to tell the customer guides the AI agent whenever no agent joins the chat: from web chat when the reply goes by email, and on email, WhatsApp, Messenger and Instagram. Use it for expectations, such as "we reply within 24 hours on weekdays". Empty means the AI agent says the team will reply as soon as possible.
The instructions are guidance
Both instruction fields guide the AI agent; they aren't sent word for word. It writes the message itself, in the customer's language, and always states where the team will reply. If your instructions give a different response time than the setting above, it follows your instructions.
Before handoff
- Ask for an email address: the AI agent asks for one before handing off, so the team can reply. Applies to web chat, email and social channels. WhatsApp uses the phone number.
- Also ask for a phone number: web chat only, and only when asking for an email address.
After handoff
What the AI agent does when the customer writes again in web chat before an agent has replied:
- Stay silent (default): it doesn't reply.
- Keep answering: it keeps helping with new questions, knowing the handed-off request is with the team.
Either way, the chat shows the customer a status above the message box until an agent replies: "Waiting for an agent · Usually replies within N min", "Our team will reply by email", or "Passed to our team" when there's no email address to reply to. The response time comes from Expected response time above. See Live chat.
The older acknowledge value, which sent an automatic reply, is accepted on every interface and saved as silent.
With Copilot, MCP and the API
Ask Copilot, for example: "Turn on live chat and tell customers we usually reply within 5 minutes".
- MCP:
get_handoff_settingsandupdate_handoff_settings. Only the fields you send change;nullresets a field to its default. - REST:
GET /rest/v1/handoff-settings?businessSlug=...andPATCH /rest/v1/handoff-settings, with the same fields. Reading needs thehandoff:readscope and changing needshandoff:write. Roles and API keys that can edit bot settings (bot:write) havehandoff:writetoo, andbot:readorchannels:readgivehandoff:read. The live chat fields that web chat configurations still accept (enableLiveChat,liveChatResponseTime,liveChatTimeout) also needhandoff:write.
Every change is recorded in the configuration history, from every interface.
The older fields still work and save here: enableLiveChat, liveChatResponseTime and liveChatTimeout on a web chat configuration, and postHandoffWebReplies on the bot configuration.