Website-to-CRM Integration: No More Manual Re-entry

The website form sends an email to a shared inbox. In the morning a salesperson opens the mail, copies the phone number and creates a record. At lunch they are in a meeting, by evening they have forgotten, and at the weekend the email went to spam. In our experience manual handling loses 10–15 percent of enquiries, and those are the most expensive losses in the business: you have already paid for that traffic through advertising.

How it should work

The user submits the form. The site validates the data and passes it to the CRM via API. A deal is created with the source, the page, the ad tag and the message text, an owner is assigned and a "call back" task is set with a deadline. The customer receives a confirmation. The whole path takes a second and requires no human. The salesperson sees a task, not an email — and a task, unlike an email, does not get lost and does appear in reports.

What should reach the system along with the enquiry

• UTM tags and referral source — otherwise you will never know which advertising pays for itself.
• The page the enquiry came from: different customers, different conversation scripts.
• The visitor identifier from your analytics system, so the deal can be linked to on-site behaviour.
• Consent to personal data processing with a timestamp — without it the form must not be submitted.
• A technical flag for repeat submission, so you do not breed duplicates when a customer clicks twice.

What breaks most often

First, silent failures. The CRM is unavailable for ten minutes, the site receives an error and simply does nothing; enquiries from that window disappear for good. The right approach is to write the enquiry into the site's own database and send it to the CRM with retries. Then whatever goes wrong, the data stays with you. Second, duplicates from repeat clicks and autofill. Fixed with an idempotency key and merging by phone number. Third, spam bots: with no protection a form brings in forty junk leads a day and the sales team stops trusting the system. Fourth, tags lost to redirects and caching. How we assemble all this on the site side is described in the web development section, and correct form behaviour and validation are covered in detail in the MDN documentation on HTML forms.

Timelines and cost

A simple integration of one form with a popular CRM is 15,000–30,000 roubles and three to five days. A full setup with several forms, a quiz, call tracking and messengers is 60,000–150,000 roubles and two to three weeks. If you have a non-standard or custom-built system, add time for studying its API. We build these links both as standalone jobs and as part of CRM projects — the latter is cheaper, because there is no need to learn the process twice.

Not just forms

Enquiries do not only come from the website. A call, a messenger message, an email, a chat — all of these are leads too, and all of them must land in the same pipeline, or your source report is lying. Telephony gives you call recordings and missed calls, and a missed call with no callback task is a customer you paid for and threw away. For appointment-based businesses the logic goes further: the customer picks a time themselves and the enquiry becomes a booking immediately. That is how online booking in homade works, where the website and the stylist schedule live in one system.

How to check it is all working

Once a week, send a test enquiry with a marker phone number and see whether it arrived and with what data. Once a month, reconcile the number of form submissions in analytics against the number of deals in the CRM: a discrepancy above five percent is a reason to look for a leak. And set up an alert for when no enquiries have come in for four hours during working time: more often than not that is a broken form, not a quiet market. We include this monitoring in technical support.