The form is only the start: connecting your website and CRM.
What happens after someone clicks send? How to route each enquiry, give it an owner, follow it up and measure which leads become sales.
The idea in brief
Every accepted enquiry needs a record, a responsible person and a clear next action. Test that handoff before sending traffic.
A visitor fills in a form, sees a thank-you message and closes the tab. The marketing report counts an enquiry. Inside the business, the message waits in an inbox that everyone assumes someone else is checking.
A customer relationship management system, or CRM, can help organise that work. What matters is the handoff. The request has to be kept, someone has to own it, and everyone has to be able to see what happens next. Buying software does not define those rules for you.
Define the handoff before connecting tools
Write down what should happen when an enquiry is accepted. Which record gets created? Who owns it? What should they do next? Who covers the request when that person is unavailable?
Keep the first version understandable. A service enquiry might create a contact, attach the request, assign a responsible person and create a follow-up task. A repeat enquiry might belong on an existing record rather than becoming another disconnected contact.
Agree a response expectation that the team can actually meet. If the website states a time, make sure the workflow supports it, including weekends and staff absence. Avoid promising an immediate personal reply when the only immediate response is automated.
Keep the context needed for a good reply
The receiving team needs to know what the person asked for and which offer they saw. That usually means the enquiry text, the service, the landing page and the campaign source. Decide which fields are essential and which can be left empty.
Keep contact details in the systems intended to handle the enquiry. Analytics has a different job. Google’s guidance on avoiding personally identifiable information says not to send data such as email addresses or phone numbers to Analytics. Review event parameters and page URLs as well as the visible form.
Context should also be readable. A pile of tracking codes is not a helpful first view for someone returning a call. Show the requested service and the visitor’s message prominently; keep the attribution detail one click away.
Plan for the handoff to fail occasionally
A connection can time out. A field can change. A CRM can reject a record. The website needs a truthful definition of “sent” and the team needs a way to detect incomplete delivery.
The pattern we use is to save the accepted request before showing success, then deliver it to the CRM with retries. A unique request identifier helps prevent a repeated delivery from creating multiple records. The precise implementation depends on the systems involved.
If nothing has accepted the message, show an error and keep the person’s input available to retry. If the request is saved but a downstream delivery is delayed, surface that failure to the team responsible for fixing it. Silent failure is difficult to recover from because nobody knows to look.
Measure what happens past the form
Google Analytics documents separate lead events such as generate_lead, qualify_lead and close_convert_lead. They describe different stages and require appropriate implementation. A generated lead does not establish that the person became a customer.
Define your stages with the sales team before building the report. Use clear criteria for qualification, record a reason when an enquiry is unsuitable and decide who updates the outcome. Otherwise, two people can use the same label to mean different things.
Review the full path from the traffic source to a real sales conversation. Attribution will not explain every interaction, but a consistent record can reveal which campaigns create enquiries the business can serve.
Run a real rehearsal before sending traffic
Submit a clearly labelled test enquiry from a phone. Follow it through confirmation, the saved request, the CRM record, assignment and the task or notification used by the team. Confirm that the person receiving it can explain what to do next.
- The same enquiry arrives twice.
- A required field is missing or invalid.
- The receiving system is unavailable.
- The assigned person is away.
- The visitor returns with a second request.
To the customer, the website and the follow-up should feel like one conversation. When we plan a website, we define this part before launch.
