Lead detection
Recognize the lead on a Gmail thread or a Salesforce or HubSpot record.
More than an SDR to AE handoff tool
Fast, fair, and auditable SDR to AE handoffs
A routing workflow picks the AE, and the meeting records the SDR who booked it.
Extension
Extension trigger
The workflow starts when an SDR books a lead from a Gmail thread in the Chrome extension.
Match Record
Lead matching
Match the lead on the page to its Salesforce record by email.
Round-Robin
Account executive round robin
Hand each SDR booking to the next account executive in the same queue your inbound leads use.
Display Scheduler
Live booking
The SDR picks a time on the routed AE's calendar and books the intro call.
Update Record
Booker attribution
The SDR who booked each meeting is recorded on the Lead, next to its new owner.
Book AE meetingsfrom Gmail, Salesforce, and HubSpot
The extension loads the lead from Gmail, Salesforce, or HubSpot, then opens the routed AE's calendar to book.
Record lookup
Show the lead's 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
On a booked meeting, a workflow writes the booker to your CRM and sends the AE context in Slack.
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 (SDR) passes a qualified lead to an account executive (AE), usually by booking the AE's first meeting with the lead. In Default, the SDR books it from the Chrome extension and a routing workflow picks the AE.
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 Chrome extension detects the lead 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.