The customer sees “sent”, but nobody has the enquiry
Hypothetical example: a renovation company receives quote requests through its website. Someone copies each email into the CRM and assigns the work. If an email is lost or that person is away, the enquiry goes unanswered. Connecting the form can remove that manual step, but the path between submission and the sales team's queue needs checking.
Before building anything, check whether your CRM already provides a form or connector that fits. Collecting the right fields, assigning an owner and handling errors may be enough. A custom integration makes sense for a specific gap: special data, another application or rules the existing connection cannot cover.
One person can have two different enquiries
A contact and an enquiry are different records. A customer may request a kitchen quote and later ask about a business premises. A shared email address does not make those enquiries duplicates. Keep the link to the person while separating opportunities where appropriate.
Agree which value identifies a submission and when to update an existing contact. Do not automatically merge people just because they share a phone number or mailbox: it might be a company's general contact. Ambiguous matches should be reviewed.
- Contact: who is asking and how they can be reached.
- Enquiry: what they need, when they asked and which form they used.
- Follow-up: owner, status and next planned action.
Two clicks should not create two jobs
If a connection problem causes the browser to repeat a submission, the integration needs to recognise it. A stable submission identifier can let the system handle that attempt without creating another opportunity. This is different from deleting similar enquiries: two real needs must remain separate.
Technically, the aim is for repeating the same operation to add no new effects. MDN describes this as idempotency and notes that POST alone does not guarantee it. Disabling the submit button helps in the interface, but does not replace server-side checks.
When the CRM fails, the enquiry needs a clear status
Decide whether the form confirms an enquiry saved for later transfer or one already present in the CRM. The visitor's confirmation must reflect what actually happened. An email notification does not prove that a record exists or that someone will handle it.
Provide a queue of pending or failed submissions and someone responsible for reviewing it. Limit retries and respect the destination system's rules. If completion is uncertain, check the submission identifier before creating another record. Keep personal data out of public logs and credentials out of browser-side code.
Five checks before accepting the delivery
Use fictional data and test the whole path from a phone to the assigned task. These are proposed acceptance criteria, not results from a customer deployment.
- A valid enquiry creates the expected request and assigns an owner.
- Repeating the same submission does not create another opportunity.
- The same person can submit another need without overwriting the previous one.
- A temporary CRM failure remains visible and can be recovered without duplicates.
- An invalid field shows a clear error rather than a false success message.
What is needed to scope a first connection
Start with the form URL, CRM name, a field list without real customer data and the assignment rule. Add approximate enquiry volume and the problem you face today. API availability, the subscription plan and provider limits need checking before agreeing scope.
A first delivery can cover one form and one destination, including testing, error handling and documentation. Migrating old contacts, changing CRM or adding channels are separate scopes. Adaris can assess this integration from Elche for SMEs in Alicante and across Spain, with commercial communication in Spanish. Price, schedule and maintenance depend on the actual systems.
Related services
Sources
Where do your website enquiries get stuck?
Tell us which website and CRM you use and which step remains manual. That is enough to start assessing a first connection; do not send credentials or your customer database. Commercial enquiries are handled in Spanish.