Files
skills/public/routing-rules.md
zeekayandHanzo Dev 65c3b27843 160 marketing, growth and PM skills, on our own connectors
Four MIT collections ported — growthOS, openclaw-marketing-skills,
Marketing-Skills and pm-skills — as 160 skills, 12 agents and 45
commands, each naming its origin in its own frontmatter so the tree can
be checked against THIRD_PARTY_NOTICES rather than trusted. Sixteen names
appeared in more than one collection and none of the copies were
identical; the longest wins, which lands on the more developed text where
they genuinely diverge.

A fifth collection is deliberately absent. awesome-growth-hacking-skills
carries NO licence, which leaves its author every right by default — and
it is a list of links rather than a collection of skills, so there is
nothing in it to port and no permission to port it with. It is cited as a
directory to read.

THE CONNECTOR SKILLS ARE REWRITTEN, not ported. They arrived installing
vendor SDKs, running OAuth flows of their own, and ending with long-lived
credentials in JSON files under .agents/ and ~/.growthos/ at mode 600.
That is a secret on a disk with no rotation path, protected from other
users and not from the agent — and one auth implementation per skill.
Hanzo holds these connectors in Go, per user, sealed in KMS, so `connect`
is the one home for the flow and the platform skills defer to it by
provider id: google_ads, meta_ads, x. It is reachable as HTTP or as MCP
tools at api.hanzo.ai/v1/mcp — the same routes, typed once in Go, so a
tool and a curl cannot disagree.

Two had nothing real behind them and now say so. There is no
search_console provider, so that skill names what does answer the same
questions (google_analytics, google_bigquery) and states that the remedy
is a provider in hanzoai/cloud rather than a vendor SDK here. And
getxapi-connect was a wrapper around a paid reseller of X's public data
with the vendor's key in an env var; it is `listen` now, on our own x
connector — a skill named after a vendor makes the vendor the capability
and dies with it.

The skills referenced paths that only existed inside the source repo, so
the shared material they read is ported to reference/ and the paths
rewritten. Three skills need the growthOS APPLICATION rather than its
data; per the estate's own split an application belongs in hanzoai/ads,
social, email or sms as a cloud plugin, so those three say what they need
instead of carrying an import that resolves to nothing.

Third-party product names are out of our prose and kept in the notices,
which is where the licence requires them and the only place they belong.
A skill's persona names a role, not somebody else's product.


Co-authored-by: Hanzo Dev <[email protected]>
2026-09-15 01:27:26 -07:00

6.6 KiB

Lead Routing Rules

Decision trees, platform-specific configurations, territory routing, ABM routing, and speed-to-lead benchmarks.

Routing Decision Tree

Use this template to map your routing logic:

New Lead Arrives
│
├─ Is this a named/target account?
│  ├─ YES → Route to assigned account owner
│  └─ NO ↓
│
├─ Is ACV likely > $50K? (based on company size + industry)
│  ├─ YES → Route to enterprise AE team
│  └─ NO ↓
│
├─ Is this a PLG signup with team usage?
│  ├─ YES → Route to PLG sales specialist
│  └─ NO ↓
│
├─ Does lead match a territory?
│  ├─ YES → Route to territory owner
│  └─ NO ↓
│
└─ Default: Round-robin across available reps
   └─ If no rep available: Assign to team queue with 1-hour SLA

Customize this tree for your business. The key principle: route to the most specific match first, fall back to general.


Round-Robin Configuration

Basic Round-Robin Rules

  1. Distribute leads evenly across eligible reps
  2. Skip reps who are on PTO, at capacity, or have a full pipeline
  3. Weight by quota attainment (reps below quota get slight priority)
  4. Reset distribution count weekly or monthly
  5. Log every assignment for auditing

HubSpot Round-Robin Setup

Using HubSpot's rotation tool:

  • Navigate to Automation → Workflows
  • Trigger: Contact property "Lifecycle Stage" equals "MQL"
  • Action: Rotate contact owner among selected users
  • Options: Even distribution, skip unavailable owners
  • Add delay + task creation after assignment

Custom rotation with workflows:

  1. Create a custom property "Rotation Counter" (number)
  2. Workflow trigger: New MQL created
  3. Branch by rotation counter value (0, 1, 2... for each rep)
  4. Set contact owner to corresponding rep
  5. Increment counter (reset at max)
  6. Create follow-up task with SLA deadline

Salesforce Round-Robin Setup

Using Lead Assignment Rules:

  1. Setup → Feature Settings → Marketing → Lead Assignment Rules
  2. Create rule entries in priority order (most specific first)
  3. For round-robin: Use assignment rule + custom logic

Using Flow for advanced routing:

  1. Create a Record-Triggered Flow on Lead creation
  2. Get Records: Query a custom "Rep Queue" object for next available rep
  3. Decision element: Check rep availability, capacity, territory
  4. Update Records: Assign lead owner
  5. Create Task: Follow-up task with SLA
  6. Update "Rep Queue" to track last assignment

Territory Routing

By Geography

Territory Regions Assigned Team
West CA, WA, OR, NV, AZ, UT, CO, HI Team West
Central TX, IL, MN, MO, OH, MI, WI, IN Team Central
East NY, MA, PA, NJ, CT, VA, FL, GA Team East
International All non-US International team

By Company Size

Segment Company Size Team
SMB 1-50 employees Inside sales
Mid-market 51-500 employees Mid-market AEs
Enterprise 501-5000 employees Enterprise AEs
Strategic 5000+ employees Strategic account team

By Industry

Vertical Industries Specialist
Tech SaaS, IT services, hardware Tech vertical rep
Financial Banking, insurance, fintech Financial vertical rep
Healthcare Hospitals, pharma, healthtech Healthcare vertical rep
General All others General pool (round-robin)

Hybrid Territory Model

Combine multiple dimensions for precision:

Lead arrives
├─ Company size > 1000?
│  ├─ YES → Enterprise team
│  │  └─ Sub-route by geography
│  └─ NO ↓
├─ Industry = Healthcare or Financial?
│  ├─ YES → Vertical specialist
│  └─ NO ↓
└─ Round-robin across general pool
   └─ Weighted by geography preference

Named Account / ABM Routing

Setup

  1. Define target account list (typically 50-500 accounts)
  2. Assign account owners in CRM (1 rep per account)
  3. Match logic: Any lead from a target account domain routes to account owner
  4. Matching rules:
    • Email domain match (primary)
    • Company name fuzzy match (secondary, requires manual review)
    • IP-to-company resolution (tertiary, for anonymous visitors)

ABM Routing Rules

Tier Account Type Routing Response SLA
Tier 1 Top 20 strategic accounts Named owner, instant alert 1 hour
Tier 2 Top 100 target accounts Named owner, standard alert 4 hours
Tier 3 Target industry / size match Territory or round-robin Same business day

Multi-Contact Handling

When multiple contacts from the same account engage:

  • Route all contacts to the same account owner
  • Notify the owner of new contacts entering
  • Track account-level engagement score (sum of all contacts)
  • Trigger "buying committee" alert when 3+ contacts from one account engage

Speed-to-Lead Data

Response Time Impact on Conversion

Response Time Relative Qualification Rate Notes
Under 5 minutes 21x more likely to qualify Gold standard
5-10 minutes 10x more likely Still strong
10-30 minutes 4x more likely Acceptable for most
30 min - 1 hour 2x more likely Below best practice
1-24 hours Baseline Industry average
24+ hours 60% lower than baseline Lead is effectively cold

Source: Lead Connect, InsideSales.com

Implementing Speed-to-Lead

  1. Instant notification — Push notification + email to rep on MQL creation
  2. Auto-task with timer — Create task with 5-minute SLA countdown
  3. Escalation chain:
    • 5 min: Original rep alerted
    • 15 min: Backup rep alerted
    • 30 min: Manager alerted
    • 1 hour: Lead reassigned to next available rep
  4. Measure and report — Track actual response times weekly; recognize fast responders

Speed-to-Lead Automation

Trigger: New MQL created Actions:

  1. Assign to rep via routing rules (instant)
  2. Send push notification + email to rep
  3. Create task: "Contact [Lead Name] — 5 min SLA"
  4. Start SLA timer
  5. If no activity logged in 15 min → alert backup rep
  6. If no activity in 30 min → alert manager
  7. If no activity in 60 min → reassign via round-robin

Measuring Speed-to-Lead

Track these metrics weekly:

  • Average time to first contact (from MQL creation to first call/email)
  • Median time to first contact (less skewed by outliers)
  • % of leads contacted within SLA (target: 90%+)
  • Contact rate by time of day (identify coverage gaps)
  • Conversion rate by response time (prove the ROI of speed)