---
lang: en
---

# Handoffs

A handoff passes a conversation to a person on the team when a visitor asks for one, when Cactus decides the team must answer, or when a teammate escalates it. Team replies reach the visitor by email, a teammate can claim, resolve or reopen the conversation, and a visitor can cancel a request that still waits.

> Verified against the product on 2026-11-20

## Ways a conversation reaches the team

A conversation reaches the team when a visitor asks for a person, when Cactus hands it over, or when a teammate escalates it.

### A visitor asks for a person

In the Messenger or on the help site, a visitor presses **Talk to a human**. The conversation goes to the team at once, and the card under the press says where the reply reaches them.

If the visitor left an address, it is kept on the conversation before the handoff, and the card says the reply reaches them by email.

A handoff tested in the Messenger preview tells nobody on the team and draws no card.

### Cactus hands it over

The assistant hands a conversation to the team itself when the visitor wants to reach someone on the team, in any words, or needs something only the team can do.

Once a handoff waits, the assistant does not hand the conversation over again.

The team's notice gives Cactus's reason for the handoff.

### A teammate escalates it

In the Inbox, a teammate selects **Escalate** on a conversation no one on the team holds. The conversation is then handed over as the team's own.

Only a member of the product's team can act on a conversation.

## What the team sees

A handed-off conversation waits until someone claims it. Select **Claim** on the thread to take it.

Claiming marks the conversation as claimed and names you as its holder. Claim works only on an escalated conversation. If someone else holds it, the screen says "_Name_ already claimed this conversation."

On a Slack or Discord handoff card, the buttons depend on the state the card shows.

| Card state | Buttons |
| --- | --- |
| Waiting, answered or joined, and nobody has claimed it | **Claim**, **Reply…**, **Resolve** |
| Waiting, answered or joined, and claimed | **Reply…**, **Resolve** |
| Canceled by the visitor | **Reply…** |
| Resolved | **Reopen**, **Reply…** |

Every member of the product's team gets an email when a conversation is handed over, whoever started it. It shows the conversation so far and a **View the entire conversation** button, and its subject is "New escalation from" the visitor's name and the product. A handoff that is already open sends no second notice.

Addresses added on the Escalations page under [Deploy](https://cactus.heycactus.ai/znbe9h-deploy) get the same email.

If a handoff is still unclaimed and unanswered two hours after the notice, the team gets one reminder.

When the visitor writes again while the team holds the conversation, the team gets one email five minutes after their last message. It goes to the teammate who claimed it, or to the whole team if none has. A teammate's reply withdraws a follow-up that is still waiting.

If the visitor leaves an address after the handoff, the team gets a mail on the notice's own thread.

## Replying to the visitor

In the conversation, what you send to the visitor goes as a reply, and what you send to the team goes as a note.

If conversations are translated, the reply reaches the visitor in their language. Set the languages on the [Translation](https://cactus.heycactus.ai/pkg3jf-translation) page.

A reply also appears in the handoff's Slack or Discord thread.

The visitor gets the team's replies by email five minutes after the last one, and only when they left an address. That email carries the team's replies, not the visitor's words. A reply to it goes to the team's first address.

## Resolving and reopening

Select **Mark resolved** on the thread. The conversation becomes resolved, and the visitor gets a mail saying "{product} resolved this" if they left an address.

The closing mail also carries any reply still waiting in the five-minute window.

On a resolved conversation, select **Reopen**. It returns to escalated if a handoff had been made, and to open if not, and its claim is cleared.

## When the visitor cancels

While a handoff waits, the visitor can cancel it from the card on the Messenger or the help site. Cancelling gives the conversation back to Cactus, which carries on.

Only a handoff the visitor or Cactus started, on the Messenger or the help site, shows a Cancel. A handoff a teammate started from the Inbox does not.

Once a teammate has replied, the visitor can no longer cancel the handoff.

If a teammate replies to a cancelled conversation, it becomes a handoff again.

## Handoff states

A handoff is in one of these states at a time, and it moves when someone presses a control.

*The states a handoff moves between, and the press that moves it.*

Open · Escalated · Claimed · Canceled by the visitor · Resolved

- Open › Talk to a human › Escalated
- Open › Escalate › Escalated
- Escalated › Claim › Claimed
- Escalated › Cancel › Canceled by the visitor
- Claimed › Cancel › Canceled by the visitor
- Escalated › Mark resolved › Resolved
- Claimed › Mark resolved › Resolved
- Resolved › Reopen › Escalated
- Resolved › Reopen › Open
- Canceled by the visitor › A teammate replies › Escalated

> **Note:** The states are drawn from the words the card and the Inbox show, and each move is one of the presses above.

[figure: handoff states]

| What the visitor's card says | What it means |
| --- | --- |
| **Waiting for a reply** | The team has the conversation and no one has replied, so Cactus keeps helping and the visitor can cancel. |
| **Claimed** by a teammate's name | A teammate has claimed the conversation and not yet replied. |
| **Answered** | A teammate has replied. It also shows when a teammate joined a conversation that was never handed over. |
| **Canceled by the visitor** | The visitor gave the conversation back, and Cactus carries on. |
| **Resolved** | The team marked the conversation done. |

## If something goes wrong

| What you see | What it means | What to do |
| --- | --- | --- |
| "Couldn’t reach the team. Try again in a moment." | The team's service did not take the handoff. | Try again in a moment. |
| "Couldn’t reach the team. Try again in a moment." on a cancel | The team's service did not take the cancel. | Try again in a moment. |
| "Too many requests to reach the team right now. Try again later." | Too many handoffs reached the team at once from this visitor or product. | Try again later. |
| "Cactus couldn’t escalate this conversation. Try again." | Escalate in the Inbox did not go through. | Select **Escalate** again. |
| "_Name_ already claimed this conversation." | Another teammate holds it. | The conversation stays with that teammate. |
| "Only an escalated conversation can be claimed." | The conversation is not waiting for the team. | Reply to it, or reopen it if it was resolved. |
| "Couldn’t send that. Try again." | A reply or note did not send. | Send it again. |
| No team email arrives | A mail the email service cannot take yet waits and is tried again, and is dropped after 48 hours. | Check the conversation in the Inbox. |

> **Tip:** Open the conversation from the card's **Open in Cactus** button to go straight to its thread.
