Home / Demos / Lead router

Watch a lead route itself.

Most brokerages lose deals in the gap between a form submission and a human noticing it. This is what closing that gap looks like. Play the buyer, send an inquiry, and watch the rules pick the right agent and fire the alert while you are still on the page.

Demo

Live demo. Simulated agents and data. Nothing is sent or stored. Every agent below is fictional. The form does not submit anywhere, there is no server, no SMS, and no database. Everything you see runs in your own browser and disappears when you close the tab.

Northgate Property Group Fictional brokerage · demo only
You are the buyer Step 1

Nothing leaves your browser. Try changing the zip to 04101 or the type to Land and send it again to watch a different rule win.

Routing rules, in order Step 2
0.00s Waiting for a lead

Send the inquiry and the engine evaluates five rules top to bottom, stopping at the first assignment.

The clock is a simulated dispatch time. Evaluating these rules takes well under a millisecond, so the demo paces the steps out on purpose to make them readable.

The agent's phone Step 3
9:41am
Simulated device
Messages now

New lead assigned

Slide to call back

No alerts

Assigned to
Nobody yet
Waiting for an inquiry
✓SMS alert to the assigned agent
✓Lead written to the CRM board
✓Follow-up task created

Fictional agents, fictional phone, fictional numbers. No message is sent.

Team board Step 4

Simulated CRM columns. Scroll sideways to see the whole team.

What this would do in production

The demo is the honest half of it.

Everything above is the logic layer, running where you can see it. A real build keeps the same rule table and wires it to the systems that actually move a deal forward.

Real dispatch

SMS and email fire to the assigned agent within seconds of the form hitting the server, with the lead detail in the message body and a one-tap callback number.

CRM write, not a mockup

The lead is created in the CRM you already pay for, deduped against existing contacts, with source, rule path, and timestamp stored on the record.

Round robin and fallback

Territory and tier rules first, then even distribution inside a pod. If nobody claims the lead inside a set window, it escalates to the next agent and then to the desk.

After hours routing

A separate on-call table for nights, weekends, and vacation coverage, so a 10pm inquiry still reaches a human instead of waiting for Monday.

Speed to lead, measured

Real timestamps on every step, so response time becomes a number you can manage instead of a story everyone tells differently.

Rules you can edit

The rule table lives somewhere the broker can change it without a developer. New territory, new price tier, new agent, same afternoon.

Have a process that leaks like this?

Lead routing is one example. The same approach works on intake, scheduling, onboarding, and every handoff where something gets dropped between two people.

Tell me what's broken See what else I build