Table of Contents

Human takeover block

Jonathan Goodfellow Updated by Jonathan Goodfellow

The Human takeover block hands the conversation from your agent to a person on your team. When a team member is online, the chat is assigned to them, the agent stops, and the visitor talks to that person from then on. When no team member is available, the agent carries on through the block's output, so the visitor still gets an answer.

Prefer watching? The Academy video tutorial walks through the Human takeover block step by step.

How to set up the Human takeover block

To set up the Human takeover block, add it from Inbox & Builder tools in the block menu, choose which team members can take the chat, and connect its output to what the agent says when nobody is available.

Human takeover panel with its team member list, next to a flow where the block's red output leads to an Ask for an email block.

The Human takeover panel has one setting and the block has one output:

● Select the team members to assign: tick the team members who can take chats from this agent. With none ticked, the chat goes to one of all the available team members, starting with whoever has the fewest conversations.

● The red output: the path the conversation follows when no team member is available. Connect it to a message or a question, such as one asking for the visitor's email. With nothing connected, a visitor who asked for a person gets no answer at all.

A short message right before the Human takeover block, such as "Let me find someone from our team for you", tells visitors what's happening while the chat is assigned.

What happens when a team member is online?

When a team member is online, the Human takeover block assigns the chat to them and the agent stops there. The blocks after the Human takeover block don't run, and everything the visitor writes goes to the team member in the Inbox.

In this example, a plant shop agent, Leafy Corner, offers a Talk to a person button that leads to the message "Let me find someone from our team for you 🌿" and then to the Human takeover block. With a team member online, the Leafy Corner chat changes in three ways:

● Assignation message: "πŸ‘‹ jon just joined the conversation!", with the name of the team member who took the chat.

● Header: the team member's name and avatar, with "A human at" and your company name underneath.

● Text box: the visitor can type freely, even when the agent only offered buttons before.

Web chat after a human takeover, with the team member's name in the header, a "just joined the conversation" line and a text box.

The visitor sees these changes as soon as the chat is assigned, before the team member writes anything. When the team member replies from the Inbox, each reply shows the team member's avatar instead of the agent's.

How to change the texts visitors see during a takeover

To change the texts visitors see when a team member takes over, open the agent's Settings > Custom System Messages and expand Human takeover:

● Assignation message: "@agent just joined the conversation!" by default. @agent is the name of the team member who took the chat.

● Agent profile text: "A human at @brand" by default, shown under the team member's name in the header. @brand is your company name.

Custom System Messages settings showing the Human takeover texts "@agent just joined the conversation!" and "A human at @brand".

What happens when no team member is available?

When no team member is online, the Human takeover block doesn't assign the chat, and the conversation follows the block's red output straight away. Team members who are Busy or Offline don't count as available.

In the Leafy Corner example, the red output leads to an Ask for an email block, so visitors who asked for a person still leave a way to reach them:

● Ask for an email: "Our plant experts are away right now. Leave your email and we'll write back within one working day."

● Goodbye message: "Thanks! We'll write to @email within one working day. Happy planting! 🌱"

Web chat where no team member is available, so the agent asks for the visitor's email and confirms it will write back.
To let your team know a visitor is waiting, whatever their status, place a Send an email or Slack block right before the Human takeover block.

How do team member statuses affect the Human takeover block?

A team member's status decides whether the Human takeover block can assign them a chat. Each team member changes their own status from the avatar menu at the bottom left of the app, with Set Busy and Set Online.

● Online: the Human takeover block assigns new chats to them automatically.

● Busy or Offline: the Human takeover block doesn't assign them new chats. Busy and Offline work the same way for the Human takeover block, and unassigned chats wait in the Inbox until someone assigns them.

What happens when a team member closes the chat?

When a team member ends a chat with End in the Inbox, the visitor's text box disappears and the header goes back to the agent's own title and avatar. The visitor can no longer write to the team member in that chat. The Inbox close and pause options explain what End and Pause do.

How to assign a chat to another team member

To assign a chat by hand, open it in the Inbox and pick a team member from Assign to team member at the top of the chat. Unassign team member, at the bottom of the same list, sends the chat back to Unassigned.

Inbox chat with the Assign to team member list open and an Unassign team member button.
A chat already assigned to one team member stays with them. For another team member to reply, assign the chat to that team member first.

A conversation also becomes a live chat when a team member writes to the visitor from the Inbox, at any point and without a Human takeover block. The Inbox guide explains how to manage chats once they're assigned.

What happens to assigned chats when a team member goes offline?

The rule for chats assigned to a team member who goes offline is set in Settings > Preferences > Assignation, under Assignation rules for team members:

● No status check: the chats stay with the team member, whatever their status.

● Unassign chats: the chats go back to unassigned, and you can assign them by hand to another online team member.

● Reassign chats to online agents: the chats move to the other online team members, depending on how many chats each one handles. With nobody online, the chats stay unassigned.

Assignation settings with the Autoassign option and the rules No status check, Unassign chats and Reassign chats to online team members.

FAQ

Why has my agent stopped after the Human takeover block?

Your agent stops after the Human takeover block because a team member took the chat. Once the Human takeover block assigns the conversation, the blocks after it don't run and the team member answers from the Inbox. The agent only carries on through the red output when no team member is available.

For WhatsApp

The Human takeover block works on WhatsApp the same way as on Web. WhatsApp shows the chat in its own app, so the header, avatar and text box look the same as before the takeover.

For Facebook Messenger

The Human takeover block works on Facebook Messenger the same way as on Web. Messenger shows the chat in its own app, so the header, avatar and text box look the same as before the takeover.

Was this article helpful?

Inbox Section Guide