← All tools

Assignment

Round robin and territory assignment for Salesforce and HubSpot

Assign records to owners by strategy, instead of by hand.

SalesforceHubSpotReversible

Records sitting on the wrong rep. Territories changed in January and the book did not. Accounts are owned by people who left, by the rep who happened to import them, or by an admin account nobody watches. An inbound lead lands on one of those accounts and sits there, routed to somebody who is not coming back, while the rep who should have it never learns it existed.

Assignment routes ownership by a policy you write down once, rather than by whoever is asked to fix it this quarter.

The configuration is the whole instruction. This is the one tool whose run carries no payload at all: the field it writes, the pools of reps, and the strategy are read at dispatch from the configuration you saved. A run says only which records to consider.

Strategies are the ones teams actually use. Round robin across a pool, or a rule that maps a field on the record to a named owner. The reps in a pool come from your CRM's own users.

How a pass runs

From scope to record.

  1. Configure once. The owner field, the pools, and the strategy are saved under Rules.
  2. Scope. A run names the records to consider, as a filter over your own fields.
  3. Resolve. At dispatch the pass reads the configuration and works out the owner each record should have.
  4. Write changed only. A record already owned by the right person is skipped.
  5. Record. Every ownership change is stored with the prior owner.

The detail

What it needs and what it does.

Object
Accounts, contacts and leads.
Configured in
Rules, under Assignment Rules. The run itself carries no payload.
What it writes
The owner field, and only where the resolved owner differs from the current one.
Who releases it
You choose when you create the run: write on dispatch, hold the whole run for approval, or queue one proposal per record.
Reversible
Yes. The prior owner is stored with every change and can be put back.
CRMs
Salesforce and HubSpot.

Speed to lead

A wrong owner does not slow the response down. It removes it.

The window where an inbound is worth something is short, and ownership decides whether anybody is inside it.

An inbound routes by whatever the record already says. If that owner left, or was never the right one, there is no slow response to measure. There is no response. The lead is not sitting in a queue somebody is working through: it is assigned, so to every report and every dashboard it is already somebody's problem, and that somebody is gone.

That is why routing belongs in infrastructure rather than in a quarterly cleanup. Ownership resolved from a policy that is current means the person who receives an inbound is the person who can act on it, on the day it arrives instead of at the next territory review.

For agents

The tools your agent calls.

Reads are free and need no permission to write. Anything that changes a record is a separate grant.

get_assignment_config the saved routing policy read
list_crm_users the reps a pool can name read
set_assignment_config change the policy write
create_assignment_run a run over a scope you name write
dispatch_run start it write
← All tools Job Change →

Where to start

Find out how many you have.

The readiness scan runs detection against your own CRM and reports what it finds, before anything is merged.

Run a readiness scan Request a demo