Connecting website enquiries to CRM records

A website form receipt is only the start: the CRM must hold the request as a findable enquiry, link it cautiously to a person and assign an owner or queue. HubSpot forms can create or update CRM records; FormsCRM describes an API webservice connector for sending mapped form fields to a CRM. Verify the CRM record and its routing rather than treating the receipt as proof of success.

Decide what the submission becomes

A contact record identifies a person; an enquiry records a request. For an existing customer who submits a new question, create a separate enquiry item or dated task linked to the contact. Define the result for a new person, an existing contact and an uncertain match before configuring the form.

Collect the fields needed to route and answer the request, such as the visitor’s message and a contact method. Retain the form or page name, submission reference and received time if available. Keep the visitor’s words distinct from fields the business assigns later.

HubSpot forms collect visitor information and create or update records in its CRM. For a separate website form, FormsCRM describes a connector using an API webservice and field mapping; its listed form plugins include GravityForms, Elementor Forms, Contact Form 7, WooCommerce, WPForms PRO and JetForms. HubSpot also points to its Forms API for custom solutions.

FormsCRM setup uses the CRM URL and credentials for the user that will create the entries, then maps form fields to CRM fields. Check that the fields are mapped to the intended destinations before accepting live submissions.

For Australian organisations subject to the Privacy Act, APP 1 requires an APP entity to have a clearly expressed, up-to-date privacy policy. The policy must describe the kinds of personal information it collects and holds, how it collects and holds it, and the purposes for which it collects, holds, uses and discloses it.

Form Field Mapping Options for CRM Integration

Match cautiously and retain the event

HubSpot form fields connect to CRM properties, and the property determines which object stores the data. A field connected to the default Company name property may create or update a company record and associate it with the contact. A company name typed into a form does not, by itself, establish which account owns the request.

Shared inboxes and changed addresses make email an imperfect person identifier. Keep uncertain matches for review rather than automatically merging people. Retain the original submission reference when available so a second request can be distinguished from a repeated delivery.

Test the configured duplicate handling before launch, and consider its effect on other record creation if you change a duplicate rule. Salesforce Duplicate Matching Rules can block Web-to-Lead submissions, so include a blocked submission in the exception test.

Key Data Points for Enquiry Tracking

Assign and reconcile the enquiry

Give each accepted enquiry an owner or queue. The person responding should see the question and contact route without searching the form platform. If the request moves to a specialist, make the transfer and response owner visible.

Define an exception path for invalid fields, blocked duplicates, spam and CRM outages. Before launch, test a new visitor, an existing contact, two people using one device and a repeated event. Compare each form receipt with the CRM record, owner and enquiry history.

Use the submission reference and received time, when available, to compare website submissions with accepted CRM enquiries. Repeat the comparison at an interval appropriate to the cost of delay, then assign discrepancies for review.