You can connect a web form to the CRM through a form built into the CRM itself, a compatible connector, or a custom integration. The job is to decide what gets saved, how to recognise an existing contact, and who takes ownership of the enquiry.
The same person may write today about one service and come back next month for another. You need to keep both requests and maintain a coherent contact record. That’s the rule you should agree on before you switch the connection on.
Separate the person, the enquiry and the opportunity
In the CRM, each piece of data has a role:
- Contact: who’s writing and how you can reach them.
- Enquiry: what they asked for in a specific submission, from which form and when.
- Sales opportunity: the job you’ll assess and follow up on, if that enquiry fits the sales process.
Record names and types change depending on the software. The enquiry may be saved as an activity, a lead, a request or its own record. What matters is being able to recover its content without replacing the previous one.
Not every message needs to become an opportunity either. A support request from an existing customer may need a task for customer service; a quote request, a sales review. Define that destination for each form.
Decide which fields go where
Before choosing the connector, prepare a simple table with whoever handles the requests. This could be a starting point:
| Web data | Destination and rule |
|---|---|
| Name, email and phone | Contact record, with a rule to recognise existing records. |
| Requested service and message | Specific enquiry, keeping the original text. |
| Submission date and ID | Request record to recognise retries. |
| Form and source page | Context for that enquiry: general contact, service or campaign. |
| Campaign, if collected | Separate field from the contact’s initial source. |
| Preferences stated in the form | Specific fields, respecting the option the person selected. |
Also decide which data the form can update. An empty field shouldn’t delete a phone number the team has already checked. A new enquiry shouldn’t automatically change the salesperson who’s already handling an open relationship.
The website and the CRM should share the same values for dropdowns. If “Maintenance” is renamed on the website, review the rule that assigns those requests. Design changes can also affect the connection.
Choose the connection based on your form and CRM
Form built into the CRM. This is an option if you can embed it on the website and it fits the design and fields you need. For example, Pipedrive web forms let you embed a form and receive the data as leads or deals. The feature is part of LeadBooster: you need to check whether it’s available in your account.
Connector between the tools you already use. This can work if you want to keep the form and there’s a compatible integration. Check what actions it supports: find a contact, update it, save a request and assign a task. Just because your CRM’s logo appears in a catalogue doesn’t mean all of those steps are covered.
Custom integration. This fits when you have your own rules, several systems or a custom form. It requires checking the available connection interfaces, permissions and maintenance. The proposal should explain what happens if one of the systems stops responding.
In any of the three options, the result is validated in the CRM: the right contact, a complete enquiry and one person responsible for handling it.
An example: three submissions, two enquiries and one contact
Ana asks for information about a service. The connection takes time to respond and the same submission gets processed again. Days later, Ana comes back to ask about another service. It’s an illustrative example for designing the integration.
The expected result would be:
| What comes in | How it should be handled |
|---|---|
| Ana’s first enquiry | Recognise or create her contact, save the request and assign the next step. |
| Technical retry of the same submission | Recover the previous result, without creating another enquiry or another task. |
| Ana’s new enquiry about another service | Keep the contact and record a new request with its own context. |
| A doubtful match with another record | Leave the association pending for review. |
To tell the first two cases apart, each submission needs a reference that stays the same through retries. If a different reference is generated every time the connection is retried, it no longer helps to identify the original operation.
How the contact is identified depends on the CRM. HubSpot documents deduplication by email: when a form comes in with the email of an existing contact, the information is added to that record. That rule doesn’t replace the decision about what to do with each enquiry.
Check the exceptions: shared email addresses used by several people, email changes or forms that only ask for a phone number. HubSpot also explains that its forms without email can associate submissions by cookies; on a shared device, that can link submissions from different people. You need to test the account’s real setup.
Assign an owner and recover errors
A saved enquiry needs a next step: review requirements, call back or prepare a reply. Agree on who receives it, what internal deadline it has and who covers absences.
For incidents, ask for a view that lets you answer three questions: what came in, what was saved and what still needs to be done. If the contact was created but the task failed, the retry should resume that pending step.
The website message also needs to be precise. You can show “We’ve received your request” when it has been safely saved for processing, even if the CRM is temporarily unavailable. If it hasn’t been saved anywhere, the visitor needs an error message and an alternative way to get in touch.
Where AI can help
AI can help summarise long messages or suggest a category when the request comes in free text. Keep the original alongside the summary and leave any doubts in a review queue.
For copying an email, transferring a selected option or assigning a form to a team, clear rules are enough. The first pilot should check that all the information is preserved and reaches the right person.
If you add AI-based classification, test requests that mention several services and ambiguous messages. A suggested category can help the team; merging records or discarding enquiries requires specific controls.
What to ask for in the final test
Run the test with a new contact, an existing one, a repeated submission and a CRM outage. Also check an enquiry with optional fields left blank and another that should go to customer service.
In each case, open the result and review: full message, associated contact, source, owner and pending task. Then measure how long it takes to handle the requests and how many need correcting. That way, you can assess performance with your own data.
If you’re deciding where to start, our guide on how to choose the first process to automate helps you prioritise.
At Digency, we connect websites and tools through custom automations. Tell us which form and which CRM you use, and we’ll define what should happen from the moment an enquiry arrives until the team handles it.
Cover: illustration generated with AI.
