A Mistyped Email Should Create a Review Task, Not a Guessed Customer Identity
A prospect can enter a typo in a form or use a different email while booking. The sales process needs a way to correct it without guessing which person owns an address. Treat conflicting contact details as a verification task.
Preserve the original entry
Keep the submitted value, the time and the source of the inquiry. Store any later correction with the way it was confirmed. Silently replacing the original can hide why a message failed or why a second record appeared.
Do not automatically turn a familiar-looking domain typo into a deliverable address. Even a likely correction can identify the wrong destination. Ask the prospect through an appropriate existing channel or have an employee review the request.
Use a correction decision tree
- The prospect confirms the corrected detail: update the appropriate field and preserve useful history.
- A verified existing alias matches: keep it attached to the known contact according to your CRM’s supported process.
- Several identifiers agree but one conflicts: ask a person to review before combining records.
- Only a similar name matches: keep the records separate until there is reliable evidence.
- No suitable contact route exists: record the unresolved inquiry rather than sending to an invented address.
Keep the appointment safe while reviewing identity
A calendar booking can remain real even if the CRM cannot confidently match it. Preserve the scheduling reference and the current meeting time. Do not cancel a meeting merely because an automated contact match failed.
When an approved merge is needed, review which record should remain and what happens to appointments, notes, source information and active follow-up. A merge that removes the duplicate card but drops the reminder journey is incomplete.
Check communication ownership after the repair
Confirm which email or number is primary, which additional identifiers are retained and which workflow owns the next message. Stop obsolete requests to book if the person already has an appointment. Verify that customer-facing instructions point to the current booking.
Use internal test records for scenarios such as an email alias, a phone number in a different format and a conflicting name. A safe matching rule should hold ambiguous cases for review, not maximize the number of automatic matches.
Measure corrections as data-quality work
Track failed contact attempts, duplicate records and reviewed corrections separately from lead suitability. A contact typo does not establish that a prospect lacks interest. It shows that your team does not yet have a dependable destination.
Google’s enhanced-conversion setup guidance shows why customer-provided identifiers also matter to advertising measurement. Only share data under the platform’s requirements and the permissions applicable to your business.
Related guides cover record matching and booking handoffs. Build Your AI Agents to discuss managed conversion work with a practical review path.
