Lead Router Pro

What it does & who it's for

Speed to lead is the cheapest sales win there is: answer inside five minutes and your contact rate roughly triples. Lead Router Pro is a production-ready Make.com scenario that makes the five-minute answer automatic — and then does the thing most routers skip: it checks that a human actually acted. Every lead that hits the webhook is normalised (email lower-cased, budget strings like "$36,000" parsed to numbers, company-size selects reduced to a comparable figure), scored 0-100 on three documented axes (company size, budget band, source weighting), and routed. Hot leads (70+) are assigned to a rep by catch-up round-robin, written to your CRM with the owner set, and DMed to that rep as a Slack lead card — with a one-click acknowledge link and a 2-hour SLA timer. Warm leads (40-69) are tagged for your nurture sequence with a team FYI. Unqualified leads (under 40) get a genuinely polite auto-reply and a tidy CRM archive, so nobody wastes a call and nothing is deleted. The scoring is deliberately explainable: three axes, one table, maximum 100. The exact weights ship in scoring-model.md with worked examples and a tuning guide, and the rep's DM shows the breakdown ("24 size + 32 budget + 30 source"), because reps stop trusting a black-box number the first time it is wrong. Rotation is catch-up round-robin done properly — rep state lives in a Make data store, assignment picks the least-loaded active rep, so someone returning from leave naturally catches up instead of being buried, and reps are paused with a single boolean. The scenario ships with sequential processing ON so the read-increment-write rotation is race-safe when two leads arrive in the same second. The SLA watchdog is the part your sales manager will actually feel. Assignment opens an SLA record with a 2-hour deadline; the rep's acknowledge link closes it via the same webhook (with a proper confirmation page); and an always-on sweep route escalates any lead still unacknowledged past its deadline — straight to the manager's DMs, exactly once per breach. Make cannot sleep a scenario for two hours, so the watchdog uses the honest pattern: every incoming event sweeps, and a free 15-minute cron ping guarantees the promise on quiet days. The setup guide includes it, and the demo simulates the whole breach path. Everything is the real Make blueprint export format: 21 typed modules across five filtered routes — gateway:CustomWebHook, three util:SetVariables mapper steps carrying the scoring formulas, builtin:BasicRouter with filter conditions on every branch, six datastore modules for rotation and SLA state, slack:CreateMessage for DMs and channel posts, email:ActionSendEmail for the auto-reply, and gateway:WebhookRespond for the ack page. The three CRM touches are HTTP modules calling HubSpot's batch-upsert endpoint (upsert on email = no duplicate contacts, ever), with the full Pipedrive swap documented — one blueprint, either CRM. Connections and tokens are named placeholders you attach once after import. You could wire this yourself — the difference is the edge-case work already done: currency-string and "51-200" select parsing, guard filters so a control ping can never email an empty address or touch your CRM, escalations that fire exactly once, a router route order that handles ack callbacks before lead logic, and documentation that explains every threshold in four places that must agree. Try the interactive demo first: it runs the same scoring rules in-page on the three shipped sample leads, animates every module hop with the real transformed data, and includes the SLA-breach run.

Version history

1. v1.0Latest1 Aug 2026

Licence & terms

These terms are snapshotted at purchase — what you see here is what applies to your order.

Reviews