Keep a second inquiry from creating a second customer

A customer sends a website inquiry, then emails again from another address. Your CRM connection must decide whether these are two contacts, two requests or one conversation. Automatically merging by name can join unrelated people; always creating a new customer produces a different kind of confusion.

Separate person and request

One person can have several independent projects. Store the request as its own record with a date, source and subject, then associate it with a contact where there is enough confidence. Do not erase a new message merely because the email address already exists.

Define a review path

A Colombian service firm might receive messages from a company buyer and a personal address used by the same buyer. A suggested match can help staff investigate, but uncertain matches should remain reversible. Keep the information that led to the decision.

Test ordinary variations

Use fictional examples for a repeated email, a changed company name, a shared inbox and two people with the same name. Check what the salesperson sees and whether the original messages remain accessible. Routine logs should avoid unnecessary message content.

Provider identifiers and account-specific API behavior matter more than a generic deduplication checkbox. Review the behavior of POST requests alongside the provider documentation when designing retries. We can map the record model and failure cases before building a CRM integration.