Customer mapping controls how a form submission becomes useful customer context. Map stable fields such as email, name, and phone before relying on automation or reporting.

What this guide helps you do

• Turn form submissions into customer records or customer updates.
• Choose which fields should sync to Customer 360.
• Avoid duplicate or incomplete customer records.

Before you start

• The form should collect an email address if it needs to identify a customer.
• Review current customer fields and any required CRM fields.
• Decide which submission details belong on the customer record and which should remain submission-only.

Do it manually

1. Open the form detail page and review What this form collects.
2. Check whether Contact sync is on.
3. Map email, name, phone, and other useful fields to customer properties where appropriate.
4. Submit a test entry with a known email address.
5. Open the matching customer record and confirm the submission appears in the customer context.
6. Adjust mapping if the wrong field appears or data is missing.

Ask Faster AI

• Review this form and map the fields that should update Customer 360. Keep private notes as submission-only data.
• Turn on customer sync for this consultation form and make sure email, name, and phone are mapped correctly.
• Find forms that collect email but are not syncing to customers, then show me what needs review.

Review before publishing or using the form

• Email is the safest matching field for customer sync.
• Avoid mapping long free-text answers into core customer fields unless your team needs that on every record.
• After changing mapping, test with both a new email and an existing customer email.

Common issues and fixes

• If a customer record is not created, confirm the form collects email and contact sync is on.
• If duplicates appear, check whether emails are missing, mistyped, or collected in more than one field.
• If a field maps to the wrong place, update the mapping and test again before using it in journeys.

Lead capture workflow

For the full path from form submission to customer record, attribution, and follow-up, read the lead capture forms article. Lead Capture Forms That Actually Convert.

AI form building practice

For how customer mapping fits into an AI-created form review, read the AI form building article. Describe a Form, Get a Form: AI Form Building in Practice.

Smarter Forms workflow

For how submission fields become Customer 360 context and follow-up signals, read the Smarter Forms product article. Smarter Forms: Tracking, Mapping, and Follow-Up Built In.

Referral systems for local businesses

For why referral forms should capture who sent the new customer and keep that context on the customer record, read the referral strategy article. Referral Strategies for Local Businesses That Don't Feel Awkward.

Consultant client machine

For why consultation forms should become customer records instead of disconnected email threads, read the consultant client machine article. The Consultant's Client Machine: From Inquiry to Retainer.

GRC Consulting customer story

For why B2B form submissions should land as structured customer context instead of staying in an inbox, read the GRC Consulting customer story. A 30-Year Auto-Industry Veteran's One-Person Firm: GRC Consulting.

Placeholder media

• Screenshot placeholder: add an annotated screenshot of map form submissions to customer records with names, emails, submission values, and private tracking details blurred.
• Video placeholder: add a short walkthrough that starts from Forms, shows the manual path, then shows how to ask Faster AI for the same outcome and review the result.

Related help

• Map form submissions to customer records
• Connect a form to an Audience or journey
• Create a welcome journey