Human handoff
A human handoff moves a website conversation from the bot to a person on your team. The bot or an agent can offer a person, but the visitor always chooses to connect. After that, the bot stops answering and your team replies from the Conversations inbox.
Before you start
- Human handoff works on website channels: Chat bubble, Help page, and Center stage.
- For the bot to offer a person, turn on the Live chat action and allow it on the channel. Without it, the bot never offers a person, even after failed answers.
- For visitors to switch to a person themselves, make the Human conversation type available in the Chat bubble channel’s Display tab, under Capabilities.
- At least one team member who can reply (Owner, Team Admin, Bot Admin, Bot Editor, or Chat Agent) needs access to the bot. See Teams and members.
How a handoff works
| Stage | What happens |
|---|---|
| 1. Offer | The visitor sees an option to reach your team. See Ways a visitor reaches a person. |
| 2. Visitor connects | The visitor selects Switch to support, or switches the conversation type to Human. The widget shows “Connecting you to our team…“. |
| 3. Visitor writes to your team | The chat shows “Human support started” and “AI is paused. New messages go to the support team.” The conversation appears in the inbox as Pending, and agents for that bot are notified. |
| 4. Agent replies | The conversation becomes Unresolved and is assigned to the agent who replied, if nobody had it. |
| 5. Agent resolves | The conversation becomes Resolved. If the visitor writes again, an agent can still reply, which reopens it. |
If a visitor switches to Human but never sends a message to your team, FluentChat cancels that pending handoff once it’s more than 30 minutes old, so it drops out of the active inbox.
Ways a visitor reaches a person
| Path | How it works |
|---|---|
| Live chat action | When the visitor asks for a person, the bot shows an offer to continue with your support team. The bot keeps helping until the visitor accepts. |
| Offer a human after failed answers | Shows a connection option after this many missed answers in a row, from 0 to 10. 0 turns it off. A thumbs-down on an answer counts as a missed answer. Needs the Live chat action. |
| Let visitors switch between AI and Human | Adds a conversation-type control to the widget header, so visitors can switch any time. |
| Invite to live chat | An agent sends the offer from the inbox while the bot is handling the conversation. |
| Human only | Under Visitors can chat with, make Human the only type. Every conversation goes to your team, and the bot doesn’t answer. |
The offer and display settings live in the Chat bubble channel’s Display tab, under Capabilities. See Chat bubble.
The bot’s offers don’t appear while nobody on your team is available, unless Offer a human while the team is offline is on. They also don’t appear when the visitor is already talking to your team.
Take over a conversation
-
Watch the inbox. Open Conversations in the main sidebar. Set Conversation scope to Human escalated or Unassigned to see who’s waiting.
-
Open a pending conversation. Pending conversations have a blue indicator.
-
Reply. Type on the Reply tab and send. You’re now the assigned agent.
-
Resolve. When the visitor has what they need, select Mark as resolved.
If the bot is still handling a conversation, you can’t reply yet. The composer reads “The bot is handling this conversation”. Select Invite to live chat to offer the visitor a person.
Availability and notifications
Each agent sets their own availability in Settings > Availability. The widget shows your team as online if at least one agent for that bot is available. Visitors can still send messages when nobody is online, if Offer a human while the team is offline is on.
Agents choose when to get browser and push notifications in Settings > Notification:
- A new handoff notifies every eligible agent for that bot.
- A new visitor message notifies the assigned agent, or every eligible agent if nobody is assigned.
- Assigning a conversation notifies the new assignee.
See Profile and preferences for the settings, and Agent profiles for what visitors see.
If agents don’t reply in time, Auto-reply when agents are slow can post a holding message after the delay you set in Send after (minutes).
Limitations
- Handoff is text chat only. There’s no phone or video transfer.
- There’s no automatic routing. FluentChat doesn’t assign by skill or round-robin. The first agent to reply takes the conversation, and admins can reassign it.
- API and Fluent Support conversations can’t be handed off from the inbox. They have no widget visitor to receive an invite.
- Only the assigned agent, Owners, and Team Admins can reply to an assigned conversation. Other agents see it but can’t take it over.
Troubleshooting
Visitors never see an offer to reach a person
Possible cause: The Live chat action isn’t enabled for the channel, nobody on the team is available and Offer a human while the team is offline is off, or Offer a human after failed answers is 0.
Solution: Check the Live chat action, your agents’ availability, and the Chat bubble channel’s Capabilities settings.
The bot keeps answering after the visitor asked for a person
Possible cause: The visitor saw the offer but didn’t accept it, or switched back to the AI.
Solution: The visitor must select Switch to support and send a message. From the inbox, you can also select Invite to live chat.
Nobody on the team gets notified
Possible cause: No agent with access to that bot has notifications allowed, or browser permission is blocked.
Solution: Each agent checks Settings > Notification and sends a test notification. An admin confirms agents have access to the bot in Settings > Members.