# Human Handoff

> Bring a person into any conversation. Take over from the Inbox, let the agent call a teammate into a live chat or call, or escalate with a ticket that always has an owner.

Source: https://docs.getlinkai.com/agents/human-handoff

Agents handle most conversations on their own. When a customer needs a person, a teammate is one step away, and they see everything said so far.

There are four ways a conversation reaches your team:

| Way | Who starts it | Use it when |
| --- | --- | --- |
| **Take over** | A teammate, from the Inbox | You want to reply yourself in any conversation. |
| **Member Handoff** | The agent, during a live chat or call | A person should join right now, like a buyer who is ready or a refund over your limit. |
| **Smart Tickets** | The agent | Nobody needs to join live, but someone must follow up. |
| **Connect Call** | A workflow | A new lead should be on the phone with a teammate within minutes. |

## Take over from the Inbox

Any teammate with access to a thread can reply as themselves.

### Open the thread
Open the conversation in the [Inbox](https://docs.getlinkai.com/products/inbox).

### Take over
Click **Take over** in the thread header or above the composer. The bar shows "You're talking as yourself" and the agent pauses.

### Reply
Write as yourself. On web chat the customer sees that you joined the conversation, with your first name and photo.

### Hand it back
Click **Hand to Agent** when you are done. The agent picks up with the full history.

Take over lasts for one thread. It ends on its own one hour after your last message, so a conversation is never left without an agent.

**Note:**
On WhatsApp, Instagram, and Messenger you can reply only inside the channel's 24-hour messaging window. When it has closed, the bar says so and offers other channels to reach the customer on.

## Member Handoff

With Member Handoff, the agent brings a teammate into a live chat or call. The agent keeps helping the customer while it looks for someone, and the teammate who accepts takes over the conversation.

### Turn it on

### Open the agent's Actions tab
Open an agent from **My Agents** and go to **Actions**. Find **Member Handoff** in the **Team** section.

### Say when to bring someone in
Under **When to bring a teammate in**, write the cases in plain words, for example "Refunds over $200, a customer ready to buy, anything the agent cannot answer." A customer asking for a person always counts.

### Pick the teammates
Select who can be offered the conversation. Leave everyone unselected to include every eligible teammate.

### Choose routing and timing
Pick a **Routing** mode and set the timers. See the table below.

### Choose channels
Turn on **Chats**, **Calls**, or both. Turn on **Respect working hours** to skip anyone who is off shift.

Changes save automatically.

| Setting | Options |
| --- | --- |
| **Routing** | **Sequential** offers teammates one at a time in order. **Round robin** rotates who goes first. **Everyone at once** offers chats to everyone together. Calls always ring one teammate at a time. |
| **Time per teammate (chat)** | 30 to 120 seconds. Default 60. |
| **Ring time (calls)** | 10 to 30 seconds. Default 20. |
| **Give up after** | 2 to 4 minutes. Default 3.5 minutes. |

### Who can be offered a conversation

- **Chats** go to members who can reply in that Inbox thread. Guests are not offered chats.
- **Calls** go to people with a verified phone number, guests included.
- With **Respect working hours** on, only people on shift are offered. If nobody is on shift, nobody is offered.

### What the customer sees

The agent says it is checking whether someone is available, without promising a time, and keeps helping. On web chat the widget shows "Finding a teammate...". When a teammate accepts, the widget shows that they joined, and their messages carry their first name.

On a call, the caller hears hold music while the agent looks for someone.

### What the teammate sees

The teammate gets an urgent notification, "*Customer* needs you in a conversation", with the reason the agent gave. In the app, a toast offers **Accept**, and the Inbox thread shows an offer bar with **Accept** and **Decline**. Accepting opens the thread already taken over. If the customer has no owner yet, they are assigned to you.

On calls, each teammate gets a phone call with a short spoken briefing. Press **1** to accept or **2** to decline. When someone accepts, the agent leaves the call.

If someone else accepted first, you see "Someone else took it."

### When nobody answers

A decline or a timeout passes the offer to the next teammate. If everyone declines, or **Give up after** runs out, the agent tells the customer in their language that nobody is free right now and keeps helping. If the agent has [Smart Tickets](https://docs.getlinkai.com/products/smart-tickets) or a form for callbacks, it offers one.

### Limits

- One search at a time per conversation.
- A 10-minute wait after a search nobody answered.
- Up to 3 searches per conversation per day.
- On Meta channels, no search starts after the messaging window has closed.

**Tip: Ask Ally**
Ally can list recent handoffs, show how many were answered, and accept one for you.

## Escalate with Smart Tickets

When a person must follow up but nobody needs to join live, the agent opens a ticket. Every ticket has an owner: the teammate you choose, otherwise the customer's owner, otherwise the workspace owner. The owner gets a reminder when the callback window passes, and owners and admins are told if the ticket is still open two days later. See [Smart Tickets](https://docs.getlinkai.com/products/smart-tickets).

## Connect a call from a workflow

The **Connect Call** workflow action calls your teammates one by one and connects the first who presses **1** with the customer. Use it to call every new lead within minutes. The action reports how the call ended in `{{customer_outcome}}`, such as `connected`, `no_answer`, or `voicemail`, so the next steps can branch on it. See [Workflows](https://docs.getlinkai.com/agents/workflows).

## How handoffs show in results

A conversation whose only result is a ticket or a follow-up form shows **Passed to team**. It changes to **Resolved** when the ticket is solved. A customer who asked for a person and did not get one lowers the conversation's score.

If submitting a form finishes what the customer came for, turn on **This form completes the request** in the form's settings so those conversations count as **Resolved**.

## Best practices

- **Write the handoff cases the way customers talk.** "Ready to buy today" works better than an internal code.
- **Turn on working hours.** Nobody gets offered a chat at 2 a.m.
- **Pair Member Handoff with Smart Tickets.** When nobody is free, the customer still leaves with a ticket and a callback.
- **Hand it back.** Click **Hand to Agent** when you finish so the agent covers the follow-up.

## Next steps

**[Inbox](https://docs.getlinkai.com/products/inbox)**:
Every call and message in one place.

**[Smart Tickets](https://docs.getlinkai.com/products/smart-tickets)**:
Escalations with an owner, a reminder, and an escalation.

**[Procedures](https://docs.getlinkai.com/agents/procedures)**:
Add approval steps where a person should decide.

**[Workflows](https://docs.getlinkai.com/agents/workflows)**:
Call new leads with Connect Call.
