Outbound routing
Use outbound routing when a teammate is arranging a meeting for a prospect and Distro should choose the host. An allowed booker starts the handoff; an eligible host receives the meeting. They can be different people.
Start with your task
Set up a handoff for the sales team
Design questions and control who sees each answer
Arrange a meeting for a prospect
Let one or many prospects choose later
Put two to five proposed times in a message
Admins configure the handoff. Sellers complete it from Distro or a supported extension launch surface.
How a handoff works
The booker supplies prospect details using a published Outbound Form version. Distro resolves CRM identity, evaluates ownership rules, then distribution rules, then the mandatory fallback. The router uses a fixed event type.
The booker can confirm a meeting, share a dedicated link, or propose times when enabled. A reusable link lets each recipient supply their own identity and start a separate session. Viewing availability or sharing an offer does not reserve a host or time; eligibility and availability are checked again when booking.
Outbound routing and its sharing capabilities must be enabled for the workspace. A seller must be an allowed booker on an active router. If a handoff is missing, check both access and active status.
Review results
Workspace admins can use these pages under Outbound routing:
Are handoffs reaching an eligible route, and where are they getting stuck?
Which routed sessions turn into bookings, through which channels?
Routing Logs
What happened in this individual handoff: router, rule, status, assignee, launch surface, and booking channel?
Insight date ranges follow when the handoff started, not the scheduled meeting date. Compare routing and booking results using the same period and filters.
A session that has no eligible host or availability is a routing problem to investigate; it does not mean the prospect was disqualified.
Last updated