Route to the Right Rep

Outcome: every lead assigned to a named owner within seconds, with existing accounts respected, a fallback that always fires, and a notification that reaches someone who will act.

Surface: Sync GTM app
Level: Advanced
Uses: Formula columns · CRM integration · Slack
Credits: 0
Prerequisite: Lesson 06's scored leads

Rules in priority order

Routing is a cascade. The first matching rule wins, and the order matters more than the rules themselves.

Existing account owner

If the company already exists in the CRM with an owner, it goes to them. Always first, no exceptions — a lead from an account someone else is working is theirs.

Open opportunity owner

Where a deal is live at that company, the deal owner takes it even if the account owner differs.

Named account assignment

Target accounts with a pre-assigned rep.

Territory

Geography, usually. Straightforward when defined, and it needs a rule for ambiguous or missing country data.

Segment

Company size or industry, where teams are specialized.

Round robin

The fallback for everything else. Weighted by capacity, skipping people who are out.

Default owner

A named human who receives anything that matched nothing. This rule must always fire.

Skipping the existing-account check is the routing failure with real consequences: a rep receives a lead from a company another rep has been working for months, contacts them, and the customer sees two people from the same vendor with different conversations. Check account ownership before anything else, every time.

Matching to existing accounts

The check depends on a reliable match key.

Match on	Notes
Normalized root domain	Primary, and the reason lesson 02 normalized it
Company LinkedIn URL	Good fallback
Company name	Only as a flag for review — never an automatic match

Subsidiaries and regional entities need a decision: is acme-uk.com the same account as acme.com? Whatever you decide, write it down, because routing and reporting both depend on it.

Round robin that works

A naive rotation sends leads to people who are on holiday, at capacity, or unable to serve that segment.


eligible = active
       AND not out of office
       AND current_open_leads < capacity
       AND qualified for this segment

assign to eligible rep with the fewest leads this week

And log the assignment reason. “Round robin, position 4” is enough to answer the question that eventually gets asked.

The fallback must always fire

Every routing system needs a terminal rule that cannot fail to match. A lead assigned to nobody sits unowned, unworked and invisible.

The default owner should be a named person — a manager, a team lead — not a queue nobody watches. And the count of leads hitting the default should be monitored: a rising number means your routing rules have a gap.

Notify someone who will act

Assignment without notification is just a database field.

Channel	Use
Slack DM to the owner	Fastest, and it is where people are
Slack channel for the team	Good for visibility and for high-priority leads
CRM task	Durable, but slow — nobody watches it in real time
Email	Slowest, gets buried

Include what they need to act: name, company, what they asked for, the score, and the enriched context. A notification that requires opening two other tools will be actioned late.

Do this now

Write the cascade in order

Seven rules, ending in a default owner.

Build the existing-account match

On normalized domain.

Decide the subsidiary rule

And write it down.

Build eligibility-aware round robin

Name the default owner

A person, not a queue.

Log the assignment reason per lead

Wire the notification

With enough context to act.

Test each rule

One lead per rule, confirming it lands where you expect.

Check your work

Existing account ownership is checked first
Round robin respects capacity and availability
A named default owner catches everything unmatched
The assignment reason is logged
Notifications carry enough context to act without opening another tool
You tested every rule in the cascade

Where this breaks

Round robin without capacity checks routes to whoever is next, including someone on leave for two weeks. The lead sits assigned and untouched, which is worse than unassigned — an unassigned lead shows up in a gap report, an assigned one looks handled. Check availability, and add an unactioned-lead alert that fires after a few hours regardless of who owns it.

Further automation

Track time-to-first-touch by owner, not just in aggregate. Routing that is technically correct still fails if a particular rep takes a day to respond — and that is a coaching problem the pipeline can surface but not fix. Lesson 09 builds the monitoring.

Next lesson

08 — Automated follow-up, the first response that references what they actually asked for.

Reference for this lesson: CRM integrations, Slack, Workspace integrations, Webhooks.