Handoff workflows
Route SDR bookings with the same workflow engine and rules as your inbound.
More than an SDR to AE handoff tool
Rules-based SDR to AE handoffs for outbound teams
Route, book, and credit every meeting an SDR hands to an AE, from Gmail, Salesforce, or HubSpot.
Chrome extension
Detect the lead and book from Gmail, Salesforce, or HubSpot.
Live booking
Book on the routed AE's calendar during the call, or copy a routed booking link.
Booker attribution
Every meeting records the SDR who booked it, ready to write to your CRM.
Book AE meetingsfrom Gmail, Salesforce, and HubSpot
The extension detects the lead, pulls the record, and books the routed AE's calendar from the tab the SDR is on.
Lead detection
Recognize the lead on a Gmail thread or a Salesforce or HubSpot record.
Record lookup
Record type, title, and mobile from your CRM and Default's data.
Built-in enrichment
Fill thin records with waterfall enrichment before routing.
Route handoffs with your inbound rules
Add the Extension trigger to your inbound workflow and govern SDR bookings with the same queues and policies.
Extension trigger
Run the same workflow from forms and the extension.
Assignment queues
Owner first, then territory, queue, or round robin across AEs.
Host selection
Book with yourself, a set of AEs, or a queue as the host.
Attribute and brief every handoff
Record the booker, update the CRM, and send the AE context the moment a meeting books.
Booker attribution
Write the SDR who booked each meeting to your CRM.
AE briefs
Send the AE a research brief on the account in Slack.
Reassign and no-shows
Reassign, reschedule, or mark a no-show from the panel.
“It’s the control layer we’re using to run GTM from the same brain.”
Matt McGonegleDirector of GTM Operations @ Cortex
FAQ
Questions about the SDR to AE handoff
It is the moment a sales development rep passes a qualified lead to an account executive, usually by booking the first AE meeting. A slow or wrong handoff is where outbound pipeline leaks.
An admin adds the Extension trigger to a workflow, often the same one inbound leads run through. When the SDR clicks Book a meeting with, that workflow routes the lead by owner, territory, queue, or round robin, then shows the AE's open times.
Yes. The meeting records the SDR as its booker, so it shows under Booked by Me, and a workflow can write the booker to a field in your CRM.
Yes. Copy a Booking Link runs the same routing and copies a link the prospect can use to pick a time, for up to 24 hours. A meeting booked from the link doesn't record the SDR as its booker.
The lead is detected automatically in Gmail, on Salesforce Lead and Contact pages, and on HubSpot contacts. On any other tab, the SDR types the lead's email.
No. The Chrome extension is included in the Scheduling and Routing + Scheduling seats, and access follows your workspace permissions. Seat prices are on the pricing page.
Reps install it and sign in by following the Chrome extension docs. An admin adds the Extension trigger to a workflow before the first handoff.
More use cases
Other motions teams run on Default
Meeting Scheduling
Branded calendars, routing queues, and group events.
Lead Routing
Route leads across territories and segments, with logs.
Outbound Automation
Prospect, enrich, and sequence on first-party signals.
The marketing engine behind the best teams
One platform to manage workflows, enrich records, route leads, and schedule meetings.