Owner first
Route by account owner first, then territory, queue, or round robin.
More than a sales Chrome extension
One extension, your rules, every booking
SDRs book from Gmail, Salesforce, and HubSpot without picking an AE, and admins keep routing, CRM updates, and access in 1 workflow.
No more guessing whose calendar to book
SDRs stop clicking through bookmarked links and asking in Slack who's free. The extension runs your routing rules and shows only the right AE's open times.
Book live
Pick a time while the prospect is still on the call.
Send a link
Copy a routed booking link when they'd rather pick later.
Run SDR bookings through your inbound workflow
Add the Extension trigger to your inbound workflow, and every SDR booking checks Salesforce, HubSpot, and your other connected tools before it routes, then enriches and updates records after.
Reads your stack
Check ownership and open deals in your CRM and connected tools before picking the AE.
Waterfall enrichment and deep research
Fill thin records from multiple providers and research the account, all from 1 extension.
CRM updates
Update the contact, account, and deal without anyone copying data by hand.
Every handoff is credited and briefed
Each meeting records the SDR who booked it, and the AE walks in with context.
SDR credit
Workflows write who booked the meeting to your CRM.
AE brief
Send the AE a research brief on the account in Slack when the meeting books.
Booked by Me
Every meeting the SDR set, with Reassign, Reschedule, and No-show in the panel.
“It’s the control layer we’re using to run GTM from the same brain.”
Matt McGonegleDirector of GTM Operations @ Cortex
Why teams switch
One routing engine for inbound and outbound
- Shared queues
Forms and SDR bookings share queues and routing policies, so a territory change applies to both.
- Routing logs
See which rule or queue picked the AE for every booking.
- Queues and hosts
Book with yourself, a set of AEs, or a queue, with primary and required hosts.
- Included in your seats
Scheduling seats include it, and reps only see the workflows you share with them.
FAQ
Frequently asked questions
It opens as a side panel on any tab. It finds the lead on its own on an open Gmail thread, on Salesforce Lightning Lead and Contact pages, and on HubSpot contact pages and the Leads preview drawer. On any other page, type the lead's email.
Yes. It detects leads on Salesforce Lead and Contact pages and on HubSpot contacts, looks the record up in your CRM and in Default's data, and opens the CRM record in one click.
Yes. It is included in the Scheduling and Routing + Scheduling seats, with no extra add-on, and access follows your workspace permissions. Seat prices are on the pricing page.
An admin adds the Extension trigger to a workflow. It can be a new workflow or your inbound one, since a workflow can have more than 1 trigger, so SDR bookings follow the same routing rules as your forms. The Triggers docs cover the setup.
Yes, it is the most common use. The SDR clicks Book a meeting with, the workflow picks the AE, and the meeting lands on the AE's calendar with the SDR recorded as the booker. See SDR to AE handoff.
Meetings booked from the Default extension can run through your inbound workflow itself, so one set of routing rules covers both. The same workflow can enrich the lead, update Salesforce or HubSpot, and brief the AE. See Default vs Chili Piper.
Follow the install steps in the Chrome extension docs, then sign in from the side panel.
The marketing engine behind the best teams
One platform to manage workflows, enrich records, route leads, and schedule meetings.