A lead arrives through a website form. Someone notices it, copies it into the CRM, checks whether the company already exists, works out who should follow up and tells them. Each of those steps can be automated. The order matters: the team has to agree how the steps should work before anyone connects a tool.
This walkthrough uses an illustrative B2B marketing setup. Your form tool, CRM and team structure will change the details, not the sequence.
Map the current path first
Follow one real enquiry from submission to first reply and write down what happened at each point.
- Where the submission arrives: an inbox, a form dashboard, a chat channel.
- Who reads it and how quickly.
- What they check: existing contact, existing company, spam, missing details.
- How the owner is chosen: territory, product interest, company size, campaign source or simply who is free.
- How the owner is told, and what they see when they open the record.
- What happens to the awkward ones: duplicates, incomplete forms, requests that fit nobody.
The last item is where most manual routing quietly lives. If the exceptions are handled by one experienced person from memory, the automation has to make those decisions explicit.
Write the routing rules in plain language
Before touching any tool, the team should be able to write the rules as sentences.
- Enquiries from Germany, Austria and Switzerland go to the DACH account owner.
- Enquiries that mention an existing customer’s domain go to that customer’s owner, not the new-business queue.
- Enquiries from the partner campaign are tagged with the campaign and go to the partnerships lead.
- Anything that matches no rule goes to a named person, with a note explaining why.
If a rule cannot be written down, it is not ready to be automated. That is useful information in itself.
Handle duplicates and missing information
Two decisions cause most of the trouble later. First, what counts as a duplicate: the same email address, the same company domain or the same person within a certain time. Second, what to do with a submission that lacks something the owner needs, such as a company name.
A reasonable default is to update the existing record rather than create a second one, and to send incomplete submissions to the owner with a short note about what is missing. Do not let a tool guess the missing value. A blank field is easier to deal with than a wrong one.
Where AI helps and where it does not
Choosing an owner by country or campaign is a rule. Detecting a duplicate is a rule. Neither needs AI, and adding it makes the behaviour harder to predict.
AI is useful one step later. A free-text message can be summarised for the owner, with the original kept alongside. The enquiry can be classified as a suggestion, for example “looks like a partnership request”, that the owner confirms or corrects. The distinction is that AI prepares information for a person, while rules move records.
If you are unsure which of your steps are rules and which need interpretation, this guide works through the question with marketing examples.
Connect the tools
Most form tools, CRMs such as HubSpot, Salesforce or Pipedrive and automation platforms such as Zapier, Make or n8n can handle this without custom code. The typical flow is: form submission triggers the workflow, the workflow looks up the contact and company in the CRM, applies the rules, creates or updates the record, assigns the owner and sends a notification.
Custom code becomes worthwhile when the rules branch heavily, when data needs reshaping between systems or when the CRM’s own automation cannot express the logic. Check what your current tools allow before deciding. That check often changes the scope.
Test before switching it on
Run the workflow against a test destination with a small set of deliberate cases.
- A normal enquiry that matches one rule.
- A submission from an existing customer’s domain.
- A duplicate sent twice within an hour.
- A form with the company field empty.
- A country that matches no rule.
- An obvious spam submission.
Look at the CRM record the owner will actually open, not just the log that says the workflow ran. The record is the result.
Give the workflow an owner
Territories change, campaigns end and someone leaves the sales team. Agree who updates the rules, who is notified when a run fails and where the team can see what happened to a given lead. A workflow without an owner slowly drifts back to manual routing.
We help marketing teams build and maintain this kind of handoff as part of workflow automation and integrations. If you want to talk through your own form-to-CRM path, get in touch.
