WORKFLOW PRESENTATION · OPERATING BLUEPRINT

Lead routing

How an incoming lead gets one named owner instead of a shared inbox no one owns.

6 STAGESFINAL REVIEW
STAGE 101 / 06

The path

A lead arrives, a contact is created, and a routing rule decides who owns it. The whole question is what happens at that fork.

STAGE 101 / 06

The path

A lead arrives, a contact is created, and a routing rule decides who owns it. The whole question is what happens at that fork.

STAGE 202 / 06

The clean route

When a lead matches a rule, it routes to the right owner with the context attached and a direct owner ping.

STAGE 303 / 06

The orphan

The lead that matches no rule is the real risk. Without a fallback, it lands in shared ownership that belongs to no one.

STAGE 404 / 06

Where it stalls

An unowned lead waits while everyone assumes someone else has it. Shared ownership is no ownership.

STAGE 505 / 06

The catch-all

A default path gives unmatched leads a named owner, whether that is round-robin or founder catch-all.

STAGE 606 / 06

The write-back

Owner and route reason write back to HubSpot, so the operator can see who holds each lead and why it landed there.

FINAL REVIEW

Before vs after

Routing is not clever rules. It is making every lead resolve to a named owner, including the ones the rule set did not expect.

BEFORE

Unmatched leads sat in a shared inbox while everyone assumed someone else had them.

AFTER

Each lead resolves to a named owner with context, including the ones no rule expected.

SYSTEM LIBRARY

Related systems.