Simulation — shows exactly what the scenario does with sample data

Lead Router Pro — Make.com scenario simulation

This page replays the exact module logic shipped in lead-router-pro.blueprint.json: webhook → normalise → score (0–100) → router → hot / warm / unqualified routes, plus the acknowledge callback and the 2-hour SLA watchdog. The scores below are computed live by the same rules the scenario uses, on the shipped sample leads. Nothing here calls a network.

active modulecompleted
action = ack score ≥ 70 40 ≤ score < 70 score < 40 always · sweep HOOK 1 Webhooklead intake VARS 2 Normaliselead VARS 3 Score lead3 axes VARS 4 Total score& band RTR 5 Router5 routes DATA 6 Get SLArecord DATA 7 Markacknowledged SLACK 8 Confirm in#sales-leads 200 9 Respondacknowledged DATA 10 Pick repleast-loaded DATA 11 Rotate+1 counter HTTP 12 CRM assignowner SLACK 13 DM lead cardto rep DATA 14 Open SLA2h timer HTTP 15 CRM tagnurture SLACK 16 Team FYI#sales-leads EMAIL 17 Auto-replypolite pass HTTP 18 CRMarchive DATA 19 Find overdueSLA records SLACK 20 Escalate tomanager DATA 21 Markescalated

Execution log — the real data at every hop

Simulation of the importable blueprint sold with this listing. In the real scenario the connections (Slack, email, CRM token) are yours, every weight and threshold is editable — scoring-model.md documents the table — and rotation + SLA state live in Make data stores.