More than Salesforce lead assignment rules

Salesforce assignmentrules in 1 place

Default routes Salesforce leads with rules on CRM and enrichment data, then books the meeting.

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

Form submission

Each run starts when a visitor submits a short demo form on your site.

Enrich Data

Rules on enriched data

Route on company size or country from enrichment, without asking for them on the form.

Rules of Engagement

1 ruleset for every workflow

Change a territory once and every workflow that runs the ruleset follows.

Round-Robin

A catch-all queue

Leads that match no rule take the Else branch, where a catch-all queue picks the owner.

Display Scheduler

Book after assignment

The assigned rep's calendar opens right after the form.

Rule changes go liveonly when you publish

Rules of Engagement holds your rules in 1 ordered list, each with criteria, a queue or user to route to, and an optional fallback. Edits save as a draft, so live routing changes only when you publish a new version.

Rules of Engagement ruleset with ordered rules, each routing to a queue or a user

Rules of engagement

Ordered rules where the first match routes the lead to a queue or a user.

Territories

A rule chooses the territory team's queue, and that queue's policy picks the rep.

Matched rule in the logs

See which rule decided and why the rules above it didn't match.

Rules can use datathe form never asked for

Manage sources pulls in CRM fields, person and company enrichment, form answers, and booking answers. With an Enrich Data step first, you can route on headcount or industry from a form that only asks for an email.

Ruleset inputs drawing from Salesforce fields, enrichment, and a form

Enrichment providers

Default manages access to each provider, so there's no API key to paste.

Forms

The Pixel captures the forms already on your site and starts a workflow on each submit.

Qualified leads bookwith the assigned rep

Display Scheduler books the visitor with the rep the ruleset picked. Leads that shouldn't get a calendar can go to an SDR as a Slack message or an internal email instead.

Workflow branching from Rules of Engagement to a scheduler for qualified leads and a Slack alert for the rest

Calendar on the form

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

Slack messages

Message the rep or a channel with the lead's details and the rule that matched.

“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 assignment rules

  • In Default, you build them as a Rules of Engagement ruleset: declare inputs under Manage sources, add rules with criteria and a queue or user under Route to, and publish. Any workflow runs the ruleset with the Rules of Engagement node, and the first rule that matches decides.

  • Default's Rules of Engagement covers what teams usually need next: rules on enrichment data or the matched account's owner, and rules that hand the lead to a queue that takes turns with weights. Salesforce allows 1 active lead assignment rule at a time, so every source and territory has to share it.

  • Yes, every Default workflow with a Rules of Engagement node runs the latest published version of its ruleset, so publishing a change updates routing everywhere without editing a single workflow. Edits save as a draft first, so live routing changes only when you publish.

  • Your server calls a Default workflow's API trigger with the lead's email, then a Rules of Engagement or Round-Robin node picks the owner and Create Record or Update Record writes it as the Owner ID. Salesforce applies its own assignment rules to API-created leads based on request headers, which differ between the SOAP and REST APIs.

The marketing engine behind the best teams

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