> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dialtu.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Transfers in Salesflow

> Agent filters after a transfer, the Agent transferred event, and entry points for the receiving agent

Transfers feed Salesflow on **WhatsApp** and **SMS (Lumina)**. Messenger has no Salesflow, so transfers there don't move anyone.

## A conversation belongs to every agent that took part

After a transfer, the conversation counts for **every AI agent that took part in it** — the one that started it and each one it was transferred to.

That's why a transition or a stage event filtered **by agent** still matches after a transfer: a filter on the toll-tag agent keeps matching a conversation that the toll-tag agent handed to the tyres agent.

## The "Agent transferred" event

Static transitions can react to a transfer **the instant it happens**, instead of waiting for the conversation to end.

<Steps>
  <Step title="Open the transition" icon="arrow-right-arrow-left">
    In the Flow view, click the transition line between two stages, then the round button that appears on it, to open **Configure Transition**. Choose **Static**.
  </Step>

  <Step title="Pick the channel tab" icon="comments">
    **WhatsApp Chat** or **SMS Chat**.
  </Step>

  <Step title="Choose the event" icon="bolt">
    In **Event**, select **Agent transferred**. As the field explains: *"When set, this transition is evaluated only when the event happens (instantly)."*
  </Step>

  <Step title="Optionally narrow it down" icon="filter">
    Two selectors appear: **From agent** and **To agent**. Leave both empty for any transfer.

    *"Optional: only transfers from or to these AI agents. Leave empty for any agent."* On the SMS tab the hint adds *"Only Lumina SMS agents can transfer."*
  </Step>
</Steps>

<Frame caption="A static transition listening for Agent transferred, from one agent to another">
  <img src="https://mintcdn.com/dialtu-0be120d3/tksmwmFP8pONiCuz/images/en/agent-transfer/salesflow-agent-transferred.png?fit=max&auto=format&n=tksmwmFP8pONiCuz&q=85&s=e2befed895b7691a093303aa8130f6c4" alt="Configure Transition panel open over the Flow view, on the WhatsApp Chat tab, with Event set to Agent transferred, From agent set to Ventas Llantas and To agent set to Peajes TAG, above the Match Mode buttons." width="2880" height="1800" data-path="images/en/agent-transfer/salesflow-agent-transferred.png" />
</Frame>

| Setting | Default | What it does |
| - | - | - |
| **Event → Agent transferred** | Off | Evaluates the transition when a transfer happens, for a customer in the source stage |
| **From agent** | Empty (any) | Only transfers made **by** these agents |
| **To agent** | Empty (any) | Only transfers made **to** these agents |

<Warning>
  **Only committed transfers fire the event.** A failed transfer (topic mismatch, limit, inactive destination) fires nothing. A transfer that was later reverted already fired when it was committed.
</Warning>

<Note>
  The event goes in the **Event** field next to **Template sent**, **Customer replied** and **Advisor replied, claimed or was assigned**. Once an event is set, the transition no longer runs when the conversation closes.
</Note>

## The receiving agent's entry points

A transfer also counts as a **conversation start for the new agent**. If the receiving agent feeds a pipeline through an entry point that triggers on conversation start, the customer enters that pipeline at the moment of the transfer — the same as if they had written to that agent directly.

<Tip>
  This is how you build "specialist" pipelines: a tyres pipeline fed by the tyres agent picks up customers who started on the toll-tag agent and were transferred.
</Tip>

## What doesn't exist

* **Salesflow on Messenger.**
* **An "Agent transferred" trigger for stage events** — it's a transition event only.
* **A transfer event for failed or reverted attempts.**

## Next step

<Card title="Troubleshooting" icon="wrench" href="/en/agent-transfer/troubleshooting">
  When a transfer doesn't do what you expected.
</Card>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.