Available for Pearl Text only.
Itās the text-chat equivalent of transferring a call to a live agent. A hand-off only stops Pearl from replying, it does not close or end the conversation. The customer can keep writing, and their messages wait for you in Human Takeover.

When it triggers
There are two ways to reach the Hand-Off node. Use either, or both together.| Trigger | How it works | Best for |
|---|---|---|
| From a previous node | Connect a transition from any node to the Hand-Off node. The hand-off runs when the flow follows that transition. | A fixed step in your flow, e.g. right after a āTalk to salesā choice. |
| With a condition | In the When to trigger field, describe in plain language when Pearl should hand off (e.g. āIf the client asks to speak to a human.ā). Pearl evaluates it throughout the conversation. Up to 250 characters. | Catching intent that can come up at any point. |
How to configure
Say (optional)
Have Pearl send one last message before it stops replying, for example to let the customer know a human is taking over. Up to 500 characters, and you can insert variables. Leave it empty for a silent hand-off.
Notify your team
Alert your team so someone picks the conversation up quickly. Set up notifications across three channels and add up to 3 of each, mix them freely.

Notification channels
- SMS
- Email
- API
| Field | Description |
|---|---|
| To | One or more phone numbers to text. |
| Content | The message to send. Up to 1,000 characters; supports variables. |
Up to 3 notifications per channel, so up to 3 SMS, 3 emails, and 3 API calls. Use the + button to add another within a channel.

