Ask most businesses how a website enquiry reaches their CRM and you get a version of the same answer: it emails the office, and someone adds it later. That works, in the sense that nobody is lost. What is lost is everything around the enquiry – where they came from, what they read first, how long they took to decide to get in touch.
Six months later you want to know which marketing is producing revenue, and the only honest answer is that nobody recorded it.
What integration should actually do
Connecting a website to a CRM is usually described as “sending the form to the CRM”. That is the least interesting part. A well-built integration does four things.
Captures the full context
Name, email and message are the easy bit. What matters as much is the first page they landed on, the referring source, the campaign that brought them, and which form they used. Attach it to the record automatically at the moment of submission and it is there forever. Ask someone to remember it and it is gone.
Routes to the right person immediately
An enquiry should arrive with the right owner attached, based on service, location or deal size. A shared inbox where everyone assumes someone else has replied is how enquiries go cold. Response time is largely decided by routing.
Deduplicates
When an existing client fills in a form, it should attach to their record rather than creating a second contact. Duplicate records are how a business ends up with three versions of the truth about one company.
Starts something
An acknowledgement to the enquirer, an internal notification, a task with a due time. The point is that a human does not have to notice before anything happens.
The ways it goes wrong
Native form, no fallback. If the integration fails silently – an expired API key, a changed field – enquiries vanish with nobody noticing. Always keep an email copy going somewhere as a safety net, and check it occasionally.
Embedded CRM forms that do not match the site. Technically simple, but an embedded form often arrives with its own styling, loads slowly and sometimes breaks on mobile. A native form that posts to the CRM usually gives a better experience.
Tracking that only works for some visitors. If a visitor declines analytics cookies, campaign data may not be available. Build so the enquiry still arrives complete, just with less attribution, rather than failing.
Capturing more than you need. Every extra field costs completions. Ask for what you need to have an intelligent first conversation and find the rest out by talking to them.
Consent and data protection
Two things have to be true. Tell people what you are collecting and why, with a privacy notice linked from the form. And make marketing consent a separate, unticked choice – submitting an enquiry is not agreement to join a mailing list.
Analytics and advertising cookies need consent before they load, which affects how much campaign data you can attach. Handle that properly rather than hoping nobody asks, and keep enquiry capture working regardless of the answer.
A reasonable order to do this in
Most businesses do not need a large project. In sequence: get every form posting into the CRM with source data attached; add routing so each enquiry has an owner within minutes; add an automatic acknowledgement; then add reporting that shows enquiries and revenue by source. Each step is useful on its own, which matters — integrations that are rebuilt all at once tend to stall halfway.
Frequently asked questions
Do we need a paid CRM tier for this?
Usually not for basic capture and routing. Most CRMs, including free tiers, accept form submissions through their API or native forms. Advanced automation and attribution reporting is where paid tiers start to matter.
Should we use the CRM’s embedded forms or our own?
Our preference is the site’s own forms posting to the CRM. You keep control of design, validation and speed, and the form still works if the CRM is briefly unavailable.
What about spam?
Use a quiet method – honeypot fields or invisible verification – rather than anything that makes a genuine enquirer work. Spam reaching the CRM is an annoyance; a real enquirer abandoning a form is a lost client.
Can we see which pages lead to enquiries?
Yes, once source and landing page are captured on each record. That is what turns the CRM from an address book into a tool that tells you where to spend next.
Get the plumbing right
We build websites with CRM capture, routing and attribution set up from the start, and retrofit it to existing sites. See our website design service or our lead generation and sales service, or get in touch.
