Routing starts with readiness and then assigns ownership. A prospect can show interest without purchase intent.1 Sending every engaged record straight to a person turns an early signal into a workload decision. Prospecting aims to create interest and convert it into a sales meeting.2 The best prospectors set 2.7 times more meetings.3 Write the handoff rule first, then choose the ownership rule that fits the account, territory, queue, or flow. This keeps the list useful and leaves unready records available for later action.
Set the handoff gate
Decide when a record becomes eligible for assignment before deciding who gets it. This keeps the ownership rule separate from the readiness rule.
Keeping the Account Engagement prospect database separate lets marketers delay handing a record to sales until it is ready.4 You can hold a prospect that is not already in Salesforce for as long as you like and control when and how to assign it.5
Use a defined trigger for release. An event team's visitor rating can set follow-up priority for event leads.6 For other records, write down the behavior or condition that moves the record from hold to active routing.
Check three things:
- What must happen before assignment?
- Does this record show intent, or only interest?
- If it stays unready, where does it wait?
Write down the trigger and holding place before moving on.
Choose the routing basis
After a record passes the gate, choose the ownership rule in a fixed order. Start with account ownership, then check territory fit and shared-flow routing before creating an exception.
Confirm that the target account list exists and is assigned.7 For account-based matching, route leads according to existing company ownership.8 Use territory routing when the work includes customer visits in person.9 Territories can also fit inside sales, where teams may work patches far from their geographic location.10
Use round-robin assignment when owners share the same flow.11 Until you have a team, route leads automatically in order.12
Before you continue, check:
- Does this account already have an owner?
- Does geography change who can work it?
- Should this flow rotate evenly?
The normal rule and the exception rule should both be clear before you continue.
Make account and contact ownership explicit
An account rule can still leave contact ownership unclear. Resolve that ambiguity before the record reaches active work.
Assign each lead so the responsible sales rep knows which deals they are in charge of winning.13 Shared contacts appear at accounts across multiple deal states or teams.14 For each one, decide whether it belongs with an account executive, an SDR, marketing, another owner, or no one yet.15
Changing the primary rep can make that rep the owner of all contacts and give the new rep future commissions.16 Those checkbox choices apply only when changing the primary rep.17
Resolve these questions:
- Should contact ownership follow account ownership?
- Can different teams work the account?
- Who owns the next action when no person is ready?
Leave each contact with a defined owner, queue, or hold state.
Pick the assignment mechanism
Match the mechanism to the recipient pool and the amount of routing logic involved. Keep the default route easy to inspect, and give exceptions a visible place to go.
A completion action can select a specific user, while an automation or Engagement Studio can select a user based on prospect criteria.18 Queues can be set up for the lead object and linked to Account Engagement.19 Assignment options can be invoked from Automation Rules, Engagement Studios, and Completion Actions, which lets you combine strategies by segmentation or need.20
For campaign-based work, assign agent teams to the campaign.21 Then assign campaign operators.22 Use the Services and Campaigns, Assignments Tab for team assignment.23
Test the route with these questions:
- How does the rule behave when criteria match no user?
- What happens to a record that needs review?
- Can someone see why the record reached its current owner or queue?
Test both the default route and the exception route on a record before you continue.
Apply and audit the assignment
Apply ownership at creation or import, then inspect the result before the list enters active work. The audit should catch defaults, formatting errors, and records that need reassignment.
Manual lead creation can include an assignment choice.24 During import, add a column to the CSV and enter the user's name in each row, matching capitalization exactly.25 Bulk reassignment is available for multiple leads.26 A CRM can assign a lead created from its plus button to the person creating it by default.27
After the update, check whether every row resolved to the intended owner. Look for records that followed the creation default, failed to match the import value, or belong in a queue or hold state. Each record should have a clear next action, with the routing reason visible on the record.
What not to do
These mistakes can turn a workable routing rule into a source of silent backlog.
- Do not make direct assignment your default when the recipient pool is large; assigning to specific users is challenging to scale when there are many possible recipients.28
- Do not map every situation to the same routing approach; different situations call for different approaches.29
- Do not make current purchase activity the only handoff criterion; for most sellers, prospecting should not focus only on people currently looking to buy.30
Before the next list enters the CRM, write the readiness trigger, ownership rule, and exception path in the same operating note. Test it against an existing account, a shared contact, and a record that should wait, then check that each has a clear next action.