Hand off to your team
End an automated conversation with a team handoff, optional assignment, private note, and in-app notification.
On this page
Set up a handoff
Use a human handoff when the next step needs a person: a specific question, a qualified lead, or an answer your flow cannot handle. Add an End node and choose Hand off to human under End Type.
The handoff ends this flow and puts the conversation into human takeover in the Inbox. Bot replies stay off until a teammate turns them back on. Turning them back on does not resume the ended run.
Give your team context
All four options are optional; use the ones your team needs.
- Handoff Message — a message for the contact. Normal DM eligibility rules still apply, so do not promise a reply has been sent unless it can be delivered.
- Assign to — select an available teammate in this workspace. Keep current assignment leaves the existing assignment unchanged.
- Internal note — leave context in the conversation for your team, up to 4,000 characters. It is shown as a note from this flow and is never sent to the contact.
- Notify team in Ravela — send an in-app notification using your workspace’s notification recipients. This option sends no email or push notification and does not include the private note.
Inbox access must be on
A human handoff needs Inbox access. If it is off, an owner or admin must turn it on in Workspace settings before you publish a handoff. The node does not turn it on for you.
Ravela checks again when the node runs. If Inbox access is now off or the chosen teammate is no longer available, the handoff fails rather than silently claiming someone received it. Review the run’s reason and update the setup.