Skip to main content
Intempt
Coming soon

Inbound lead routing

Enriches and scores every inbound lead, then assigns it by named account, territory or round robin so nothing rots in an unassigned queue.

Authored by Sid Chaudhary

Founder & CEO at Intempt

Agentic workflow

Coming soon

3 steps Blu runs end to end. It drafts a plan and nothing runs until you approve it.

  1. 1

    Score the lead out of 100

    Coming soon

    Blu builds a step

  2. 2

    Assign it to the right rep

    Coming soon

    Blu builds a step

  3. 3

    Check the balance and the SLA

    Coming soon

    Blu builds a step

About this recipe

When to use it

The unglamorous failure mode isn't a bad lead, it's a good lead nobody claims. This enriches, scores, and assigns every inbound lead the moment it arrives, so nothing sits unassigned.

What it delivers

When a new inbound lead arrives via form, demo request, or signup, enriches and scores it, then assigns it to the right rep based on territory, round-robin, or named-account rules.

How you prompt this

Describe the outcome in your own words and Blu Agent maps it to this recipe, or run it by name. It drafts a plan first and nothing runs until you approve it.

Tell Blu Agent what you want

“Enriches and scores every inbound lead, then assigns it by named account, territory or round robin so nothing rots in an unassigned queue.”

recipe.md preview

Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.

Sign up to read the full recipe.md and run it with Blu Agent.

Sign up to see the full recipe

Inputs & outputs

What the recipe needs before it runs, and what it leaves in your workspace.

Inputs

  1. Nothing declared beyond an Intempt workspace. Blu asks for anything else it needs as it goes.

Outputs

    How the recipe runs

    Blu follows the steps in order and shows you each one before anything goes live.

    1. 01Score the lead out of 100Create an AI-derived attribute 'lead_score' on the User object. Composite: (a) ICP fit (firmographics match (industry, employee count, geo), 0-40 points; (b) intent signal) form type (demo > content > newsletter), pricing-page views, last-week product activity, 0-30 points; (c) buyer signal (title seniority + role relevance, 0-20 points; (d) brand engagement) prior touchpoints on this account, 0-10 points. Output: 0-100 score with tier label (hot 70+, warm 40-69, cold <40).
    2. 02Assign it to the right repCreate a workflow firing on Form submitted OR user_signed_up (where source != self-serve-only). Step sequence: (1) enrich the account (firmographics, technographics, decision-maker contacts); (2) compute lead_score; (3) apply routing rules in priority order: (i) named-account override (if account is on target-account list, route to assigned account owner); (ii) territory match (geography, industry, segment); (iii) round-robin within territory pool (preserves balanced rep load); (4) create task assigned to the determined rep with lead context, score, and routing reason explained; (5) post Slack notification to rep; (6) IF score = cold AND no named-account match, route to self-serve nurture journey instead of human queue. Use the result of "Score the lead out of 100".
    3. 03Check the balance and the SLACompose a lead routing performance dashboard: lead volume by tier (hot/warm/cold), routing distribution by rep (round-robin balance check: variance should be <15% rep-to-rep), median time from lead-arrival to first-touch (SLA: <2hr hot, <24hr warm), tier-conversion: hot-to-meeting / warm-to-meeting / cold-to-engaged rates. Flag any rep with significantly worse first-touch SLA than peers. Use the result of "Score the lead out of 100", "Assign it to the right rep".

    Install Intempt and run it

    1. 1

      Sign up

      Create a free Intempt workspace.

    2. 2

      Connect your data

      Add the sources this recipe reads from.

    3. 3

      Ask Blu

      Type /inbound-lead-routing in Blu once this recipe is live there.

    4. 4

      Review and approve

      Blu builds each step and waits for your OK before anything goes live.

    Related recipes

    Sid ChaudharyDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Sid ChaudharyPost demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Sid ChaudharyReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe

    More recipes by Sid Chaudhary

    Discovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Post demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Return rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe

    Got a play worth sharing?

    Publish it to the Intempt Collective Marketplace and earn when other teams run it.

    Submit a recipe