AI automation · Lead routing

ProspectRoute — lead scoring & routing

Every enquiry captured, scored and assigned to the right rep within minutes — with a clock on it, so nothing goes cold.

Typical build 3–8 weeksPeople in the loop for anything uncertainYour tools stay where they are

The workflow

  1. Lead arrivesForm, email, call notes
  2. QualificationCompany, need, size, region
  3. ScoringFit, intent and timing — with reasons
  4. RoutingTerritory first, then capacity
  5. CRMContact and deal created
  6. SalespersonNotified with context and a deadline
  7. Follow-upEscalates if the clock runs out

01 The problem

You know this one.

The pattern, what it costs you, and what changes once it is built.

What happens today
An enquiry arrives on Friday afternoon, sits in a shared inbox over the weekend, and is assigned on Tuesday to whoever is free rather than whoever is right.
Why it matters
By then the person who sent it has spoken to someone else — and nobody can say how many good leads went the same way.
What changes
Every enquiry is scored and assigned within minutes of arriving, with a deadline attached, so none can quietly go stale.
What improves
Faster first contact, fairer workloads across your team, and a pipeline you can actually see.

02 Watch one run

Follow one enquiry from form to follow-up.

Scroll and the pipeline moves with you. On a phone it plays by itself — tap it, or a stage name, to take control.

Illustrative interface · example data
  1. Capture

    Website forms, email, call notes your team logs, and bulk lists from an event you exhibited at. All of it into one queue, so no source depends on a particular person remembering to check it.

  2. Enrich

    Before anything else, the enquiry is checked against your CRM. An existing contact gets merged rather than duplicated. What is missing — company, rough size, sector, region — is filled in, so the person picking it up already knows who they are talking to.

  3. Score

    A score built from three things you define: how well they fit, how much intent they have shown, and whether the timing is real. The breakdown is always visible, because a score a rep cannot interrogate is a score they will quietly ignore.

  4. Route

    Assignment respects territory first and current workload second, so a strong lead does not land on the desk of someone already fourteen deep. Low scorers are not discarded — they go to a nurture sequence and stay warm.

  5. Follow up

    The lead is written to your CRM with an owner, a call task, and an acknowledgement already sent to the person who enquired. An SLA runs against it, and if nobody touches it in time it escalates rather than expiring quietly.

03 The engagement

What you get, and what it takes.

A fixed price is agreed in a written scope before anything is built. The discovery call that comes first is free.

What you get

  • Lead-source audit
  • Scoring model tuned to your criteria, with visible reasoning
  • Assignment rules for territory, capacity and escalation
  • Pipeline visibility dashboard

What we need from you

  • Your lead sources and CRM access
  • What a good customer looks like to you
  • Territories, capacity and escalation rules

Timeline

3–8 weeks

From signed scope to running in your systems, with working software shown to you at every milestone.

How an engagement runs

Connects to tools like these. Anything else with an API or export is confirmed during assessment

  • Web forms
  • Your enquiries inbox
  • HubSpot
  • Salesforce
  • Zoho CRM
  • Spreadsheets

04 Questions

Before you automate lead routing.

Can salespeople see why a lead scored the way it did?

Always. The score shows its working — fit, intent and timing — so a rep can disagree with it for a reason.

What happens to low-scoring leads?

They are not discarded. They go to a nurture sequence and stay warm.

Do we need a CRM?

It works best with one, and we connect to the common ones. If you run on spreadsheets today, we will tell you honestly whether a CRM should come first.

05 Often combined

Most engagements use two or three.

The five automations share one engineering spine, so they combine cleanly — and feed the same data into SolmiriX if you use it.

  • DocTrace

    Invoices, forms and delivery notes get read, checked and posted into the systems that own them — instead of retyped by hand. DocTrace

  • SupportRoute

    Email, web forms and helpdesk tickets sorted the moment they land — so the urgent one reaches a person while it still matters. SupportRoute

  • UnifyCore

    Two systems that cannot talk, connected in both directions — with retries, a review queue and an alert instead of silence. UnifyCore

  • KnowledgeAssist

    An assistant that answers from your own handbook in plain language — and cites the section it came from. KnowledgeAssist

Compare all five

Want to see ProspectRoute on your own process?

Tell us how the work gets done today. We will tell you plainly whether this is the right fit — and what it would take.