Does it email the prospect?

Outbound sends stay with a person by default and open only on your decision. The agent qualifies, routes and briefs; a human owns the first message unless you decide otherwise.

How does it handle our territory and account rules?

As configuration rather than judgement. The rules are stated, applied and logged, and where two of them conflict the lead goes to a person instead of to whichever rule happened to run first.

Lead qualification and routing in minutes

Routing fails at the handoff more often than at the scoring

Today

Assigned by whoever notices first

Form submissions land in a shared inbox.
The routing spreadsheet that decides who owns what has not been touched since the last territory change, so leads get assigned by whoever notices first.
A rep researches a name before responding, which is work repeated for every lead that was never going to qualify.
And when somebody asks why a lead was called qualified, there is no record of the reason.

With agents

Context arrives with the lead, and the unclear one gets decided

Qualification becomes inspectable.
The owner receives context rather than a name.
The unclear lead gets decided by a person.

How an agent runs it

Routing fails at the handoff more often than at the scoring, so the workflow is built around what arrives with the lead and what happens to the one the criteria cannot place.

01

Capture with source recorded

Captures inbound from the channels you run and records where each lead came from.

02

Enrichment from your sources

Enriches the record from the sources you already have access to.

03

Scoring against written criteria

Scores against qualification criteria that are written down rather than carried in someone's head.

04

Routing by the rule that decided

Routes to the owner your territory and segment rules name, and records which rule made the call.

05

First-touch brief

Assembles a first-touch brief from the record and the account activity, so the owner starts with context instead of a name.

06

Human gate

Routes anything the criteria cannot decide to a person for a judgement call, rather than letting a default rule absorb it.

07

Decision logged with its reason

Logs the decision and its reason against the record, so a disputed routing can be inspected afterwards.

Results

What changes when the handoff carries context

Qualification you can inspect

The criteria are written down, so a routing decision can be reviewed against them instead of defended from memory.

Context, not just a name

The brief is assembled from the record by the same step that does the routing.

The unclear lead gets a person

The gate sends it to somebody with the authority to judge it, which is what a silent default rule takes away.

Where this fits

Workflow / Automate a Workflow

Tier 1 through the Automate a Workflow door. Inbound handling is a manageable first workflow to scope because it has a clear start, a clear finish, and an owner who already feels the gap. It extends toward a sales operations role that carries more of the funnel, named as a path of extension rather than a forecast.

Automate a Workflow explains the door this enters through; How It Works explains the gates and decision logs.

Tier 1 / Prove

How It Works

Questions, answered

Writing them down becomes the first scoped task, usually alongside the person who has been applying them from memory. That is the readiness question, and it is answerable before you commit to anything.