What should a CRM lead-routing implementation brief include?
Direct answer. Write five decisions before implementing CRM lead routing: the record to assign, matching criteria, owner, fallback and evidence of the next action. An imported contact, an assigned owner and a notified salesperson are three separate outcomes; test each one you actually need.
Commissioning work now? Compare the Zoho CRM setup and onboarding scope, or send the project details for a scope check.
Define the business event that starts the work
“Put our leads in a CRM” is too broad to implement reliably. A website enquiry, a purchased contact list, a manually created contact and an existing customer asking for support may need different treatment. Start with the source and event: a new quote request arrives through the named website form, or a labelled batch of existing contacts is imported. Say which events are outside the first phase.
Then name the destination record and its owner. A contact is a person; a deal represents an opportunity in a pipeline. Your chosen CRM may distinguish leads, contacts and deals differently. Have the implementer show the intended records and relationships using a small sample. Avoid creating a fresh deal for every repeat form submission unless that is an explicit business decision.
Write the routing worksheet before creating automation
The original worksheet below uses five decisions that a sales manager can approve without learning the automation editor. Fill a row for each meaningful branch. Keep the first phase small enough that you can explain every route and its fallback to a new member of staff.
For example, an equipment supplier could route installation enquiries for its northern service area to one team, product-only enquiries to another, and missing-area requests to an intake owner. This is an invented planning example, not a ZoopCoder client result. The useful detail is the fallback: an unmatched enquiry should remain visible and actionable instead of disappearing between branches.
| Decision | Example instruction | Acceptance evidence |
|---|---|---|
| Record | Assign the new quote opportunity and link its contact | Correct record type and relationship |
| Match | Use the controlled service-area value | Matched, blank and conflicting inputs checked |
| Owner | Keep existing account owner where agreed | Repeat enquiry preserves the intended owner |
| Fallback | Unmatched requests go to intake | A visible unmatched request and responsible user |
| Next action | Create a follow-up task and chosen notification | Task, notification and access checked separately |
Treat matching and duplicate handling as separate decisions
Document which fields determine the route and where their values come from. A customer-entered free-text city is different from a controlled region field. Agree how blank, misspelled or conflicting values behave. If the rule depends on an account owner, decide whether a repeat enquiry stays with that owner or enters a fresh assignment process.
Before a CSV import, ask for a field map and the duplicate policy: create, update, skip or flag for review. Test a small labelled sample containing a genuinely new contact, an existing contact with a changed value and two rows referring to the same person. Keep the raw source file and the import result. Do not overwrite a useful customer history just to make the imported row count equal the spreadsheet count.
Verify the entry path and subscription before promising a rule
Zoho’s assignment-rule documentation distinguishes records created through import, webforms and API from records created manually; assignment rules do not apply to manual creation through that mechanism. Test the actual route that will be used after handover. A demonstration with an imported row does not establish that a salesperson’s manually entered record will behave the same way.
HubSpot documents workflow assignment and owner rotation with subscription and seat requirements. Its owner-rotation workflow action requires Sales or Service Hub Professional or Enterprise, with eligible seats. The published setup fee is separate from a software subscription. Ask the supplier to confirm feature availability in your actual account before designing the process around a screenshot from a different plan.
Test notification, task and ownership independently
A record can have the correct owner while the person never notices it. Decide whether the required next action is a task, an in-app notification, an email or a manually reviewed queue. HubSpot specifically notes that assigning owners through import does not notify them of that assignment. Include notification behaviour in the test instead of assuming it follows from the owner field.
Use controlled test addresses and agree whether automations should be paused during historical imports. A welcome message intended for new inbound enquiries may be inappropriate for an old contact list. Check the record owner, resulting task, notification destination and permitted record access as separate assertions. A routing test should not require sending marketing to real customers.
Include the exceptions that change who follows up
Run one matched request, one unmatched request, one repeated request and one request arriving when the normal owner cannot take it. Agree what “cannot take it” means in this project: leave, inactive account, missing permission or outside an agreed business period. Do not promise live availability-based allocation unless the selected product, plan and implementation support it.
Keep a short recovery instruction beside the rule inventory. It should explain how an administrator finds unassigned records, fixes a mistaken field and reassigns a request without triggering an unintended message. State who maintains the rules when staff, territory or pipeline stages change. A one-time configuration job does not automatically include ongoing sales operations.
Send a bounded brief and buy the matching implementation
Example brief: “Set up one sales pipeline for three users. Import our cleaned contact sample first, preserve existing owners on repeat enquiries and route new website quote requests by service area, with unmatched records assigned to intake. Demonstrate a next-action task and the chosen notification without sending messages to customers. Provide the field map, rule list and exception instructions.” The website connection and exact number of rules still need to be checked against the quote.
ZoopCoder’s Zoho CRM setup lists up to three users, 2,000 leads/contacts and five automation rules, with subscription fees, custom functions and integrations beyond email excluded. The HubSpot setup lists up to three users, 2,000 contacts, one pipeline and three workflow automations, plus a plan-fit check. Custom-coded actions and marketplace integrations are separate. A website-to-CRM connection is not implied by importing a CSV or connecting email.
If the CRM is already configured and one rule has stopped working, describe the failing event, expected record and observed result for the Zoho/Bigin bug-fix or HubSpot bug-fix scope. We supply this work; the worksheet is also usable when comparing another implementer. Buy the missing process and its proof, rather than another dashboard nobody is responsible for checking.
Questions before you commission the work
Does a CRM setup automatically connect my website?
No. Importing contacts and connecting email do not establish a website integration. Name the form, destination, authentication and error handling in a separately agreed connection scope.
Can I assume owner rotation works on a free account?
No. Assignment features depend on the product, plan, permissions and seats. Check your actual account before approving the implementation design.
Should old contacts receive new-lead messages during import?
Only if that is an intentional, permitted part of the process. Agree how automations behave during import and test with controlled records before loading real contacts.
Sources and scope
Primary documents checked 4 November 2026. The commissioning tables and sample briefs are editorial suggestions, not platform requirements or measured client outcomes. Live service pages govern the current price and included work.