#Hand the opportunity back to whoever holds the role (handoff)

In the Assignment automation's By role (handoff) mode, the opportunity goes to the agent who already holds the chosen role on that opportunity — not a fixed agent, not a draw. It's what solves the no-show: the meeting didn't happen, the opportunity moves back to the qualification stage and lands with the SDR who qualified that lead, whoever that is on each opportunity.

The new owner gets a notification with a link to the opportunity. The opportunity's roles and commissions don't change — the handoff changes who takes the next action, not who played each part.

Before you start

• Workspace role: owner, admin, or an agent with the coordinator subrole. Without it the automations screen is read-only. See what each role can do in the permissions table.
• The pipeline needs roles configured (Pipeline settings → Agents & Teams) and opportunities need someone recorded in the role — by manual assignment or by the Assignment automation itself (record the role from the automation).

#Steps

1. Open the pipeline and, on the stage that should hand opportunities back, click Create automation.
2. In the Type step, choose Assignment and click Continue.
3. Under How to assign, choose the By role (handoff) card.
4. In Role that receives the card, pick the role (for example SDR).
5. Optional: in If nobody holds the role, pick a backup agent.
6. Click Save.

From then on, every opportunity that enters that stage — moved by a stage trigger, created by external entry, or dragged by hand — goes to whoever holds the chosen role on it, and that person is notified.

#Example: a no-show hands back to the SDR

1. On the qualification stage, set the Assignment to By role pointing at SDR.
2. On the same stage, set a Stage trigger with the missed-meeting (no-show) event.
3. When the meeting falls through, the trigger moves the opportunity back to qualification — and the handoff delivers it to that opportunity's SDR, who gets notified.

#What happens in edge cases

When nothing is assigned, the automation logs the reason internally — the opportunity stays visible to anyone with broad pipeline visibility.

#Change or remove the automation

Each stage has one Assignment automation. When you open the tab with an automation already active, the card at the top shows which one it is — configuring and saving again replaces it. To turn it off without losing the configuration, use Deactivate; to delete it for good, Remove.

#Related

• Record the opportunity's SDR or Closer from the automation
• Draw the owner at random from agents you pick
• Agent assignment

#If it didn't work

• Save says the role is missing: By role mode requires picking which role receives — select one from the list.
• The role list is empty: the pipeline has no roles configured. Set them up in Pipeline settings → Agents & Teams.
• The opportunity entered the stage and nobody received it: check that someone holds the role on that opportunity (open it and look at the role assignments) and that this person still participates in the pipeline. Set a backup agent to cover these cases.
• The person received the opportunity but wasn't notified: the notification respects their notification preferences — ask them to check their account's notification preferences.
• You can't open the automation: your role can't edit automations — see what to do when you're missing permission.