More than Salesforce lead routing

Route Salesforce leadsand book the meeting

Default sends each lead to its account owner first and routes the rest by rules and round robin.

WorkOS
Air
Cortex
Dust
Decagon
Owner
Airbyte
Listen Labs
Profound
Wispr Flow
fal ai
Perplexity
Rillet
New Form Submission

Form submission

The workflow starts when a visitor submits the demo form on your site.

Match Record

Account owners first

Match Record finds the account by email domain, so a lead from an owned account goes to its owner.

Rules of Engagement

Rules, then round robin

The ruleset checks the account owner first, then routes other leads by company size and region to a round robin.

Display Scheduler

Book with the routed rep

The lead picks a time on the routed rep's calendar right after the form.

Create Record

Owner assignment

Create the Lead in Salesforce with the routed rep as its owner.

Leads from owned accountsgo to the owner first

Match Record finds the account by email domain and sends the lead to its owner. Leads with no owned account go through Rules of Engagement or a round robin queue, and Update Record writes the Owner ID.

Workflow matching a Salesforce lead to its account, then routing unowned leads through a queue

Lead to account matching

Domain matching, with tiebreakers when several accounts match.

Rules of engagement

Route each lead to its account owner or a territory queue from 1 ruleset.

Round robin queues

Default picks the next rep from the queue, using each rep's weight and skipping paused reps.

The rep's calendaropens on the same page

Default starts the Salesforce lookup and enrichment when the visitor leaves the email field, so routing is ready by the time they submit. Display Scheduler then shows the assigned rep's calendar over your page.

Demo form submission opening the assigned rep's calendar on the same page

Calendar on the form

The calendar opens over your page, with no second form to fill in.

Booked and not booked branches

Branch on whether the lead booked, with a fallback host for reps who are out or unavailable.

Follow up on unbooked leads

Alert the owner in Slack or add the lead to a sequence when nobody books.

Every assignment comes with a reason

The Reasoning card shows each assignment with every rep's score and the tiebreaker that applied. Workflow errors post to the Slack channel your admin picks.

Assignment detail with scored members, the tiebreaker applied, and the determined member

Error alerts in Slack

Send workflow errors to a Slack channel or straight to an admin.

Salesforce setup

The managed package and the user mapping that let Default write the Owner ID.

“It’s the control layer we’re using to run GTM from the same brain.”
Matt McGonegleDirector of GTM Operations @ Cortex
FAQ

Questions about Salesforce lead routing

  • Default assigns Salesforce leads in a workflow: Match Record checks for an account owner, a Round-Robin or Rules of Engagement node picks a rep when there is none, and Update Record writes the Owner ID. Salesforce's own assignment rules give each lead to the first rule entry that matches.

  • Default routes Salesforce leads by account owner, rules, and round robin, then books the meeting with the assigned rep in the same workflow. Look for a tool that routes all 3 ways and writes the owner back to Salesforce, so reps never wait on a separate scheduling tool.

  • Default automates it with a workflow that starts when a lead is created in Salesforce or a form is submitted. A Round-Robin or Rules of Engagement node picks the owner, Update Record writes it, and Default selects the Change Data Capture objects the trigger needs when you publish.

  • Default does both in 1 workflow. Routing decides which team or rep owns a lead, using rules like territory or account ownership, and distribution spreads leads across that team with a round robin queue so each rep gets a fair share.

  • Yes. Default's Display Scheduler node opens the routed rep's calendar on the same page after the form is submitted, and the workflow continues on a Booked or Not booked branch.

  • Default uses Change Data Capture only for workflows that start from a Salesforce record change, and each object they watch takes 1 of the objects your org can select. If your org is at that limit, a trigger on a new object can fail to fire even though the workflow publishes.

The marketing engine behind the best teams

One platform to manage workflows, enrich records, route leads, and schedule meetings.