Start with the routing question, not the tool
Write down, in plain language, who should own each kind of inquiry. For most local service businesses the useful dimensions are short:
- Service type — installation versus repair, residential versus commercial, website project versus maintenance request.
- Area — only if different people or crews cover different areas.
- Urgency — whether the customer chose an "urgent" option, which should usually trigger a phone call rather than a slower queue.
- Existing customer or new — existing customers often go to the person who already serves them.
If you cannot describe a rule in one sentence, it is probably too complex to automate reliably yet.
Design the form so routing is possible
Routing can only use data the form collects. A free-text "message" box cannot be routed reliably; a short required choice such as "What do you need help with?" can. Keep choices few and mutually exclusive, and add "Something else" so customers are not forced into a wrong category.
Use proper input types and labels so the form works on phones and with assistive technology. The W3C forms tutorial and MDN's form reference are good references for whoever builds it. More on which fields to ask for is in what a quote request form should ask.
A routing table you can maintain
Keep the rules in a small table that a non-technical person can read and change. For example:
| If the inquiry is… | Owner | Notified by | If owner is away |
|---|---|---|---|
| Repair, marked urgent | On-call coordinator | Text or call alert | Office manager |
| Repair, not urgent | Service desk queue | Shared inbox + CRM task | Next business day review |
| New installation quote | Sales owner | CRM assignment + email | Office manager |
| Existing customer | Their account owner | CRM assignment | Service desk queue |
| Anything else | Office manager | Shared inbox | Owner |
The last row matters most. Every routing setup needs a catch-all, because customers will always find a combination you did not plan for.
Connecting the pieces
Many CRMs, including HubSpot, can receive form submissions and assign owners with built-in workflows. When the form tool and the CRM do not integrate directly, a connector platform can pass the data across. Whichever route you choose, confirm three behaviours in testing:
- The record is created once. Retries and double-clicks should not create two contacts; see fixing duplicate CRM leads.
- The owner is notified where they actually look. A CRM assignment that nobody receives as a notification is not routing.
- Failures are visible. If the CRM rejects a record, someone should get an alert and the original submission should still be stored somewhere, such as a copy to a shared inbox.
Checks before you switch it on
- Every form choice maps to exactly one owner, plus a catch-all.
- Holidays and absences have a named backup.
- Urgent inquiries trigger a faster channel than email.
- Test submissions with obviously fake data reach the right person and are then deleted or labelled as tests.
- Someone reviews unassigned or failed records daily for the first few weeks.
- The privacy notice on the form matches where the data actually goes.
Where routing stops helping
Routing decides who should respond. It does not make them respond. If leads are assigned correctly but still wait days, the issue is capacity or process, and the next workflow to look at is follow-up reminders or a clearer pipeline — see CRM pipeline stages for a service business.
Questions
Do I need a CRM to route leads?
No. A shared inbox with clear rules, or a team channel with an owner per message, can work for a small team. A CRM becomes useful when you need history, stages and reporting across many inquiries.
Should routing be round-robin?
Only if everyone in the rotation can genuinely handle every inquiry type. Most small service businesses route by service type or area first, and use round-robin only within a group of interchangeable people.
Sources and further reading
- W3C forms tutorial w3.org
- MDN's form reference developer.mozilla.org
- HubSpot knowledge.hubspot.com
Official documentation changes. Check the current version before you rely on a rule, limit or setting.
Next step
Start with one workflow worth fixing.
Bring the real steps, the tools you already use and the place the handoff gets stuck. We review feasibility, access and approval points before quoting — no instant integration promise.
See Business Automations for what we scope, or prepare a custom quote brief.