The research question
An accounting consultant sends invoices on behalf of several clients from one email domain. If the CRM treats every message from that domain as evidence for a single customer, documents from different legal entities become mixed. The reverse also happens when a customer uses several domains or a generic email provider across its operating history. Entity-resolution research separates selecting candidate pairs from deciding whether they identify the same object. That distinction makes the evidence and reversibility of a CRM identity decision central to this design question.
A concrete design choice
Domain matching should therefore contribute context rather than decide identity by itself. The proposed review can distinguish sender, document issuer, intended recipient and named contracting party. Registration identifiers and explicit document references should outweigh a convenient email grouping. When the message and attachment describe different organizations, the interface should retain both roles instead of choosing a single account too early in the import process.
Separating transport metadata from business identity also improves corrections. If a consultant changes their email provider, the historical client relationships need not be rebuilt. The account relationship can remain supported by the attachment’s explicit details while the communication record changes independently. A reviewer should see which clue selected the candidate and which evidence ultimately justified the identity decision, because those may be entirely different.
What would demonstrate usefulness
Try a shared-service provider, a customer with an old domain and a public-mail account. Review whether each document reaches the correct candidate party and whether the user can see why the email sender and the business subject are not necessarily identical.