evams®Discuss your project ↗

CRM and sales

How to connect a website to CRM and organise enquiry handling

Connecting a website to CRM means organising reliable enquiry delivery, assigning responsibility and preserving the history of subsequent work. An integration is ready when an enquiry can be traced from the form to the outcome, including errors and repeat submissions.

A simple “form sends an email” arrangement can work at low volumes, but makes oversight harder. CRM makes it easier to see status, next steps and reasons for lost deals. However, the system itself cannot fix an unclear process: describe it before configuring fields and automations.

Describe the enquiry journey before integration

Start with the sources: website forms, calls, messages, advertising lead forms and directory enquiries. Clarify which enquiries create a new deal and which continue an existing one. A customer may submit a form and call at the same time; the system should not automatically count these as two separate sales opportunities.

For each source, define the responsible person, response time and next step. For example, a quote request goes to the relevant manager, who clarifies the details, prepares a proposal and schedules a follow-up. If the request arrives outside working hours, the customer receives a realistic acknowledgement of the expected wait.

Document exceptions: spam, wrong numbers, returning customers, unsupported regions and support requests. Handle these separately from new sales where appropriate. Lead reports will then avoid mixing contacts with different meanings.

Choose the minimum data set

A form should collect enough information for the first useful response. Required fields are determined by the process, not a desire to fill every CRM field. A consultation often needs only contact details and a short description of the task; a property appraisal may require an address and specifications. Sensitive documents should not be requested through a general form without a carefully designed secure process.

GroupExamplesPurpose
ContactName, phone number or emailRespond to the person
RequestService, message, languageUnderstand and route the task
ContextPage, source, campaignEvaluate acquisition
Technical dataTime, enquiry ID, delivery statusFind errors and duplicates
ProcessOwner, status, next stepManage handling

Agree a format for each field: telephone, date, currency and service list. Free text is useful for messages but poorly suited to statuses or sources. A shared set of values produces comparable reports rather than dozens of variations of the word “website”.

Choose the connection method

Options include a native CMS module, an integration service or a custom server-side API integration. The choice depends on supported fields, reliability, data volume and process requirements. A ready-made module can reduce work if it genuinely covers the necessary scenarios.

What to check in a ready-made solution

Find out who maintains it, what plan limits apply and how errors are handled. Check the transfer of language, source and custom fields. Clarify whether logs can be exported and delivery retried. An attractive configuration screen does not prove that an enquiry will be preserved when CRM is unavailable.

When a custom integration is justified

It may be needed for complex routing, multiple systems, a particular deal structure or additional data validation. It also brings responsibility for API maintenance, access renewal and monitoring. The estimate should show both development and ongoing maintenance.

Secret keys must not be placed in public page code. Data should pass through a suitable server-side component or a supported secure platform mechanism. Limit integration access to the operations it needs and give staff individual accounts.

Plan for failures and repeated requests

The website and CRM may temporarily fail to respond to each other. Distinguish between the website accepting an enquiry and completed delivery to CRM. If the record is safely stored in a queue, you can tell the visitor that the request has been received. If it was not saved, do not display success merely because the button was clicked.

Use a unique enquiry identifier. Redelivery of the same event should not create a new deal. This is called idempotent processing: repeating the operation produces the same result. HubSpot’s integration guidance specifically discusses retries, timeouts and the risk of duplicate contact creation.

Errors need a log, an alert to the responsible person and limited retries. Technical context is sufficient for the log; avoid unnecessarily storing the full text of a personal enquiry. Failures should be visible to the team and recovery verifiable.

Separate the contact, enquiry and deal

A contact represents a person or company, an enquiry is a specific incoming request and a deal is a commercial process. CRM capabilities differ, but preserving this distinction is useful. One contact can have several independent projects, while several messages may concern one project.

Merge rules should be cautious. A matching email often helps identify a contact, but several people may share a company address. Do not irreversibly merge records based only on similar names. Where uncertain, leave the check to a manager.

A duplicate delivery and a repeat customer enquiry are different situations. The first should be suppressed technically; the second may contain important new information. The system should add to the history rather than silently discard everything similar.

Configure statuses that reflect the work

An initial pipeline might include “New enquiry”, “Contact established”, “Request clarified”, “Proposal sent”, “Customer decision” and “Completed”. Adapt the names to the real process. Do not add stages that staff cannot clearly distinguish.

An active deal should have an owner and a dated next action. “Waiting” without a deadline does not help manage work. For a lost deal, record a clear reason: unsuitable task, timing, price, another supplier selected or no response after the agreed number of attempts.

Do not force a manager to choose a convenient reason to make the report look better. If the reason is unknown, record that. Accurate data helps improve the offer and advertising. Detailed diagnosis is covered in “Enquiries but no sales”.

Preserve the source without false precision

Transfer permitted UTM parameters, landing-page address and language. Agree which source is stored as the first known source and which belongs to the current enquiry. Do not overwrite the entire history with the latest visit if you need it for analysis.

Some enquiries will lack a reliable source: a person may call after several visits or share a link with a colleague. An additional “How did you hear about us?” field is useful, but the customer’s answer is not technical attribution. Store these separately and do not fill unknown sources with an arbitrary channel.

Sending sales outcomes to advertising platforms requires separate configuration consistent with their requirements and the legal grounds for processing data. Connecting a website to CRM does not mean that all information may automatically be sent to advertising systems. Start by defining the events genuinely needed and the permitted data set.

Consider access and information protection

Collect data for a defined purpose and explain its processing to visitors. Consent to marketing emails should not be combined with a service enquiry. AKI notes that personal data processing requires a legal basis; choose it according to the actual purpose, rather than automatically using one checkbox for everything.

Restrict employee access by role and define retention periods and deletion procedures. Check who can access the integration service and backups. An employee’s departure should trigger access revocation, not handing a shared password to the next manager.

Accept the integration against scenarios

Test valid and invalid data in different languages and on different devices. Check repeated clicks, temporary CRM unavailability and recovery of delivery. Ensure the employee sees the necessary context and can complete the process through to an outcome.

  • Every accepted enquiry has an identifier and can be found in the system.
  • Fields and language are transferred without losing meaning.
  • There is an owner and a fallback route.
  • Duplicate deliveries do not create extra deals.
  • Errors are visible and can be retried.
  • Test records do not distort commercial reports.

After launch, reconcile accepted forms with delivered enquiries, not just the total number of CRM records. Document the configuration and assign an integration owner. This keeps the system manageable after a supplier change or website update.

An example acceptance scenario

Imagine a company receiving website quotation requests. A visitor selects a service and leaves an email address and task description in Russian. After submission, the server saves the enquiry with a unique ID, while the integration creates a CRM record and assigns the relevant manager. The customer sees confirmation with a realistic response time.

Now reproduce a failure: CRM is temporarily unavailable. The accepted enquiry must remain in controlled storage, and the responsible person must see the delivery error. After recovery, a retry creates one record. If CRM accepted the request but its acknowledgement was lost, the retry must not create a new deal.

The same customer then sends clarification from another page. This is a new message and cannot simply be discarded as a duplicate. The linking rule should preserve it in the contact’s history or prompt the manager to review it. A technical event identifier and a contact address serve different purposes.

Finally, the manager clarifies the project, sends a proposal and records the result. Check whether the original context remains, whether the next step is visible and whether a report can be produced without manually searching emails. This sequence demonstrates a working process much better than showing one successfully created record.

What to hand over to the team after launch

Provide a short guide explaining where enquiries come from, what the fields mean, how to change statuses, where to find errors and whom to notify. Include the fallback process if the system is unavailable. The document should be understandable to an employee who did not participate in development.

Separately retain a map of integrations and access owners. List the services involved in delivery, who pays for their plans and which limitations could interrupt operations. Do not include secret keys in a widely accessible guide. Access to them should be controlled.

It is useful to manually trace a sample of the first real enquiries. This helps identify incorrect routing, an inconvenient status or a missing field before large volumes accumulate. After fixing an issue, update the guide and repeat the affected test so the team follows the current process.

Regular checks are also necessary after updates. A changed form, required CRM field or integration permission can disrupt delivery. The assigned owner should know about these changes in advance and confirm that enquiries continue to arrive.

Frequently asked questions about CRM

Can we start with a simple system?

Yes. It matters more that staff understand the statuses and maintain the data. Complex automation is unnecessary until repeatable actions are described. However, export options, access and reliability should be checked from the start.

Are email notifications enough?

Sales oversight usually requires a history and status. Email can serve as a backup notification, but does not guarantee that someone is working on the enquiry. Responsibility must be visible in the process.

Do proposals need to be sent automatically?

Only if the terms can be established reliably without clarification. For a complex service, automate acknowledgement and task assignment while leaving the substantive proposal to a specialist.