How to Use the Transfer Bot Action in Conversation AI

By Sparkforge Support Team ·Last reviewed May 3, 2026

The Transfer Bot Action in Sparkforge Conversation AI hands off a chat to a live agent, another bot, a workflow, or a specific user. Configure it inside Bot Goals with optional fallbacks.

The Transfer Bot Action in Sparkforge Conversation AI hands a conversation off to a live agent, another bot, a workflow, or a specific user or team. It keeps chat history intact and lets you set fallbacks if the primary destination isn't available.

Transfer Destinations

  • Live Chat — route to a human via the Conversations inbox.
  • Another Bot — switch to a more specialized bot (e.g., sales handoff to support).
  • Workflow — fire an automation to book, follow up, or update records.
  • Agent — assign to a specific user or team.

How to Configure a Transfer Bot Action

  1. From your sub-account, open AI Agents in the left sidebar.
  2. Select Conversation AI > AI Agents and pick the bot to edit.
  3. Open Bot Goals and click Transfer Bot.
  4. Choose a transfer type from the dropdown.
  5. (Optional) Add tags before transfer or set fallback actions.
  6. Click Save.

Transfer to Live Chat

Moves the conversation from the bot to a human via the Live Chat interface. The chat appears in the Conversations tab so the agent can respond manually.

Example: A user asks for billing help and the bot routes them to the billing team.

Transfer to Another Bot

Hand off to a different published bot. Useful for splitting responsibilities by topic (sales vs. support) or language. Always confirm the destination bot is published and tested before going live.

Transfer to Workflow

Fires a workflow tied to the contact's current context. Common uses:

  • Booking appointments
  • Sending follow-up emails
  • Updating contact records
  • Triggering internal alerts

Transfer to Agent

Assigns the chat to a specific user or team. Useful for tier-based support, regional routing, or named-rep ownership. You can require the agent to be online or set a fallback if no one is available.

Routing Tips

  • Use a Condition Step before the transfer to gate it on tags, responses, or contact attributes.
  • Insert a Wait Step before the transfer if you want a built-in delay.
  • Always set a fallback so off-hours conversations don't dead-end.

Frequently Asked Questions

What happens if no live agent is online?
Configure a fallback — fall back to another bot step, leave a message, or retry after a delay.
Can I delay a transfer?
Yes. Add a Wait Step before the Transfer step to delay by a set amount of time.
Is the chat history preserved?
Yes. The full transcript is retained and visible to bots and agents on either side of the handoff.
Can transfers be conditional?
Yes. Use a Condition Step before the Transfer to fire only on specific tags, responses, or contact attributes.
Is the Transfer Bot Action available in every plan?
The action is available, though access to certain destinations like Workflows or Live Chat may depend on plan-level features.

Was this article helpful?