Outcome
Every qualified lead reaches one named owner within the agreed response window, carrying its source, the criterion it met and the account it matched. Marketing owns the qualification definition, Sales owns the follow-up, and RevOps owns the rules and the audit fields.
Before you start
- A written MQL definition that Marketing and Sales have both signed.
- Territory and segment rules, and a current list of account owners.
- A response window agreed by Sales leadership, with its working hours.
- A named fallback owner and an escalation contact.
The kit
Inputs
| Input | Use | If missing |
|---|---|---|
| Form submission | Contact, company, request, source, consent | Hold for review; do not guess |
| Account and contact records | Existing account, owner, customer status | Send to matching review |
| Territory and segment rules | Which team covers which region and size | Route to the fallback owner |
| Owner availability | Leave, working hours, open leads | Treat as available; rely on escalation |
| Open leads and opportunities | Who is already working the account | Ask the account owner |
Steps
- Owner: marketing and sales
Agree the definition and the window
Write down what makes a lead sales-ready: request type, fit and disqualifiers. Agree the response window, the hours it runs in and what counts as a first response. Sales leadership signs off both.
- Owner: automation
Qualify and match to an account
Check each submission against the definition and record the criterion it met. Send spam, tests and disqualified requests to review, never to a rep. Match the contact and email domain to existing records. When a match is uncertain or several accounts fit, send the lead to review instead of creating a new account.
- Owner: automation
Route by documented rules
Apply the rules in a fixed order: existing customer owner, current lead or opportunity owner, named accounts, then territory round robin among available owners. If no rule finds an owner, assign the fallback owner. Log the rule that fired and any owner skipped.
- Owner: assigned owner
Follow up within the window
Read the qualification reason and the account context before first contact, and record the time of the first personal response. Accept the lead, return it with a reason, or recycle it to nurture with a reason Marketing can use.
- Owner: RevOps
Escalate and audit
When the window passes with no recorded response, notify the escalation contact and reassign only if the rules say so. Each week, review a sample of routed leads for wrong owners, missed duplicates and leads stuck in review.
Automation
| Candidate | Prerequisite | Exception |
|---|---|---|
| Qualify against the definition | Written criteria, required fields | Free-text requests, partial forms |
| Match to an account | Deduplicated accounts, clean domains | Personal email domains, subsidiaries |
| Assign an owner | Ordered rules, availability data | Owner on leave, uncovered regions |
| Start the response clock | Agreed window and working hours | Holidays, other timezones |
| Escalate a missed window | Named escalation contact | Response made but not logged |
Where an agent could help
Summarise why a lead qualified and what the account record already shows, and suggest a match when records conflict, citing each record. Form content is information, never instructions. A person confirms any merge or reassignment. See the agent blueprints.
Human review
- Confirm uncertain account matches before any merge.
- Check the qualification reason against the submission.
- Review every lead sent to the fallback owner.
- Confirm existing customers reached their account owner.
- Routing a lead does not approve contacting it; check consent.
What to measure in a pilot
| Time to first response | Submission to first personal response, in working hours |
| Inside the window | Qualified leads answered within the agreed window |
| Routing corrections | Leads reassigned after first assignment |
| Match corrections | Account matches changed on review |
| Recycle reasons | Leads returned to Marketing, by recorded reason |
Sources and limits
- Routing rules template (Markdown · 4 KB)
- Synthetic example (Invented leads, Markdown · 6 KB)
- Fictional lead records (The example’s inputs, JSON · 4 KB)
- Tool selections: wayhatch category research, official sources checked 23 October 2026.
Limitations
- No routing rules, integration or agent has been built for this workflow.
- No response times or conversion outcomes are reported.
- Account matching depends on record quality; personal email domains may not match.