Most businesses already have both ends of this process: a website that collects enquiries and a CRM where the sales team works. Between them there is often a person copying details from an email into the CRM and deciding who should follow up. Each step is small, but together they introduce delay, typing errors and enquiries that are never answered.
This path is a good first automation project: the process is easy to describe, the data is structured and the result is easy to check. Below is a practical order, starting with the steps everything else depends on.
Capture everything at the moment of submission
Some information exists only at the moment of submission. Once the visitor leaves, the campaign they came from and the page they were reading are gone. Capture this context in hidden fields.
- UTM parameters (source, medium, campaign, term, content) stored when the visitor lands, not only when they submit.
- Click identifiers such as gclid and fbclid, so the enquiry can later be matched to an ad click.
- The page URL where the form was submitted and the referring page.
- A submission timestamp in a single time zone, ideally UTC.
- The consent choices the visitor made, if your forms or cookie banner record them.
Send the submission to a webhook or an automation platform such as n8n, Make or Zapier, or directly to the CRM's API. Avoid using the email notification as the data source: parsing emails is fragile and breaks whenever the template changes.
Validate before anything reaches the CRM
Validation keeps records that waste the sales team's time out of the CRM. Run checks in the form and again on the server, because browser checks can be bypassed.
- Required fields are present and within sensible length limits.
- Email addresses have a valid format. Optionally, check that the domain can receive mail.
- Phone numbers are normalized to one international format, such as E.164, so they can be compared and dialled.
- Spam protection is in place: a honeypot field, rate limiting and, if needed, a CAPTCHA service.
- Free-text fields are treated as plain text, never rendered as HTML.
De-duplicate against existing records
People submit forms more than once, and existing customers use the contact form too. Without de-duplication, the CRM fills with copies of the same person.
Search the CRM for an existing contact before creating one. Match on normalized email first and normalized phone number second. When a match exists, add the new enquiry as an activity or a new deal on the existing contact instead of creating a duplicate, and keep the original owner unless there is a reason to reassign.
Decide the rules in writing
Agree what counts as a duplicate and what should happen to it before building the workflow. Edge cases, such as two people from the same company or a shared office email address, are easier to settle in a document than in a live system.
Enrich only what you will use
Enrichment adds information the visitor did not type. Much of it needs no third-party service: the company domain from a business email address, the country from the dialling code, or the service of interest from the page the form was on.
Before adding a third-party enrichment tool, confirm that its data will change a decision, such as routing, and that your privacy notice covers it.
Assign an owner automatically
Assignment is where most of the delay in manual processes comes from. Write the rules down, then automate them. Common approaches are round-robin between available salespeople, routing by service or product line, routing by country or language, and routing larger enquiries to a senior team member.
Every rule set needs a fallback owner for enquiries that match no rule, and a way to reroute enquiries when someone is on leave.
Notify by email and WhatsApp
Once the record has an owner, notify that person with a link to the CRM record rather than a copy of the data, so the CRM stays the single source of details.
For the person who submitted the form, an automatic confirmation email sets expectations about when they will hear back. WhatsApp confirmations are possible through the WhatsApp Business Platform, which requires an approved message template for business-initiated messages and the contact's opt-in. Check both requirements before planning WhatsApp into the flow.
- Internal notification to the owner, by email or a team chat channel, with a link to the record.
- Confirmation to the enquirer by email, optionally followed by WhatsApp where they have opted in.
- A reminder to the owner, or their manager, if the enquiry has no recorded activity after a set time.
Log every run and handle failures
An automation that fails silently is worse than a manual process, because nobody notices the missing enquiries. Log each run with its input, actions and result. When a step fails, retry a limited number of times, then alert a named person.
As a safety net, keep a copy of every raw submission outside the automation, such as a database table, so no enquiry is lost if the workflow breaks.
Measure response time
With timestamps captured at submission and activities recorded in the CRM, response time can be measured rather than estimated. Define it clearly, for example as the time between submission and the first logged call, email or message from the owner.
Report the median rather than the average, because a few very slow responses distort averages. Break it down by owner, hour and day of the week to see where the process still needs attention, such as enquiries that arrive outside working hours.
Where to start
- Map the current process and where data is copied by hand.
- Build capture, validation and CRM record creation, with logging, as the first release.
- Add de-duplication and assignment once the records are arriving reliably.
- Add notifications, reminders and response-time reporting.
- Review logs and reports after a few weeks and adjust the rules.
