The playbook
Lead Routing: Template and Field Guide
This lead routing template turns a broad task into a record another person can use. It captures lead type, rule, owner, then connects that information to a decision. Copy the table into your working document or system and create a separate record for each item in scope.
Put the task in context
Specify territory, service, account ownership, availability, and fallback rules in priority order. Test a lead matching two rules and a lead matching none. A monitored exception queue is preferable to an apparently successful assignment to an unavailable user.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| lead type | Record the lead type associated with this customer or opportunity record. Use a stable reference so later updates can be matched. |
| rule | Record the rule associated with this customer or opportunity record. Keep the value specific enough for another owner to interpret. |
| owner | Record the owner associated with this customer or opportunity record. Keep the value specific enough for another owner to interpret. |
| fallback | Record the fallback associated with this customer or opportunity record. Keep the value specific enough for another owner to interpret. |
| Decision field | Entry instructions |
|---|---|
| Observed problem | Describe the actual condition and where it was observed. |
| Recommended action | State the smallest action that resolves the documented problem. |
| Evidence | Link to the record, observation, or test supporting the action. |
| Owner and next review | Name the accountable person and when the decision should be revisited. |
How to complete the worksheet
Begin with lead type. Use the same reference throughout the record so notes are not attached to the wrong item. Then define routing rules by need territory and ownership. This establishes the information required before the worksheet becomes a request for action.
Next, provide a fallback when the preferred owner is unavailable. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as assigning leads to an inactive user without an alert, rather than a broad instruction to “improve performance.”
Finally, test duplicate and incomplete submissions. Put use monitored fallback queues and reassignment rules in the action field only when it addresses the observed condition. If the problem is different, change the action. The template is a structure for judgment, not a reason to apply the same fix everywhere.
Illustrative completed decision
| Part | Illustrative entry |
|---|---|
| Problem | Assigning leads to an inactive user without an alert |
| Action | Use monitored fallback queues and reassignment rules |
| First check | Define routing rules by need territory and ownership |
| Follow-up check | Test duplicate and incomplete submissions |
| Outcome to define | unassigned eligible inquiries |
Adapt the fields without losing meaning
You can add fields required by your team, but each should change a decision or preserve necessary context. Keep factual observations separate from recommendations. If rule changes, record the new value and its effective date instead of silently rewriting the context of an earlier decision.
Use the record in a handoff
Ask the receiving owner to explain the next action using only the worksheet. Missing context becomes visible quickly during that exercise. Repair the record before applying the structure to a larger batch. Keep unassigned eligible inquiries connected to the item so the team can later assess whether the action was useful.
Make communication preferences and conversation status visible to the responsible owner. An automated action should not continue blindly after a meaningful reply or a request to stop. Route uncertain cases to a person.
Skip the manual steps. Let AgentixCRM run this for every client.
Start now