# Human handoff

Let automations answer the easy, repeated questions. Let your team answer when a customer needs a real person.

In Tuku, a person takes over a chat simply by replying. There is no separate "take over" step.

## How a chat reaches your team

| Way | What happens |
| --- | --- |
| **A Human Handoff step in the flow** | The flow reaches a [Human Handoff](/automations/flow-nodes#human-handoff) step, often after the customer taps a button like `คุยกับแอดมิน`. The automation stops, automation is paused for the chat, and the status becomes **Open**. |
| **An AI Expert hands off** | The customer asks an [AI Expert](/ai/expert-conversations) for a person. The flow goes down the **Wants a person** branch, which should end in a Human Handoff step. |
| **A teammate replies** | Anyone on the team opens a chat in the inbox and sends a reply. Automation pauses for that chat right away, even if a flow or an AI Expert was in the middle of answering. |

### What the Human Handoff step can do

In the automation editor, the **Human Handoff** step has three optional settings:

- **Handoff Message**: a message sent to the customer first, for example "Let me connect you with our team!"
- **Assign To** (Pro): the teammate who gets the chat.
- **Auto-add Labels** (Pro): labels added to the chat, for example `needs-admin`.

After this step, the flow ends.

:::tip
Find every handed-off chat with the **Filter** button: set **Status** to **Open** and **Automation** to **Paused**. Handed-off chats also show in **Needs reply** whenever the customer sent the last message.
:::

## Reply to take over

1. Open the chat in the [inbox](/inbox/overview).
2. Type your reply and press **Enter**.

Sending a reply does all of this at once:

- Stops any flow or AI Expert that was running in this chat.
- Pauses automation, so no new automation starts here.
- Sets the status to **Pending**.
- Assigns the chat to you, if nobody was assigned.

Before you send, the line above the reply box warns you: **Sending a reply pauses automation for this chat.** If a flow is running at that moment, it says **A flow is replying here. Sending a reply pauses it.**

## The automation control

The button in the thread header shows who answers this chat next. Click it to see details.

*Screenshot: The automation control in a conversation header, open on Automation paused with the Resume automation button*

| It shows | Meaning |
| --- | --- |
| **Automation running** | A flow is replying in this chat right now. The pop-up shows the automation's name and its current step. |
| **AI answering** | An AI Expert is answering in this chat right now. |
| **Automation on** | No flow is running. A new comment or keyword can start one in this chat. |
| **Automation paused** | Your team is handling this chat. Automations won't start here until you resume them. |

On a narrow screen the button shortens to **Running**, **AI**, **On** or **Paused**.

### Pause without replying

Click the control, then **Pause automation**. Any running flow stops. Use this when you want to read the chat and reply later, without a flow sending more messages.

### Give the chat back to automation

Click the control, then **Resume automation**. New comments and keywords can start automations in this chat again.

:::note
**Resume automation** does not restart a flow that was stopped. The next automation starts only when the customer triggers one again, for example with a new comment or keyword.
:::

## Conversation statuses

The status menu in the thread header shows where the work stands. Choose **Open**, **Pending** or **Resolved**.

| Status | Meaning | How it is set |
| --- | --- | --- |
| **New** | The customer has not written in this chat yet, for example a chat an automation started from a comment. | Set by Tuku. You can't choose it. |
| **Open** | Your team needs to act. | When a customer sends a message, and by a Human Handoff step. |
| **Pending** | You replied and are waiting for the customer. | When you send a reply. |
| **Resolved** | The work is done. | You choose it. |

When the customer writes again, a **Pending** or **Resolved** chat goes back to **Open** and shows as unread.

Choosing **Resolved** also stops any running flow and turns automation back on for that chat. Automation is not paused anymore, so a new comment or keyword can start an automation again.

Choose **Resolved** when:

- the customer has placed an order (see [Attribution](/attribution)),
- the customer has stopped replying, or
- the chat is spam or a mistake.

Resolving a chat does not lower your [Monthly Active Contacts](/settings/billing#monthly-active-contacts). Those are counted per month, not per chat. But it keeps your inbox tidy.

## Assign a chat (Pro)

1. Open the chat.
2. Open the contact panel (person icon in the header).
3. Under **This conversation**, choose a teammate in **Assigned to**.

To see your own chats, click **Filter** and set **Assignee** to **Assigned to me**. Choose **Unassigned** to find chats nobody owns yet.

On the Free plan, the panel shows that assigning is a Pro feature. See [Plans and pricing](/discover/plans-and-pricing).

## What automations do while paused

While a chat is paused:

- No new automation starts in the chat, even if a comment or keyword would match.
- If the customer comments on your post again and TikTok flags the comment as high intent, a comment automation can still post its public reply under the comment. It does not send a DM.
- The customer writing again does not resume automation. Only **Resume automation** or **Resolved** does.

:::caution
TikTok only lets you reply within **48 hours** of the customer's last message, with a few follow-ups after that. Answer handed-off chats quickly. Watch the **Expiring** tab. See [Messaging limits](/inbox/messaging-limits).
:::