Connect email and CRM records
Bring the relevant exchange to the customer record deliberately.
Match conversation participants to CRM contacts and companies, maintain their details and explicitly share or withdraw a chosen customer thread.
Check the address against CRM
An address match does not share the conversation.
Knowing the correspondent and sharing the conversation are different decisions.
A mail address can belong to an existing customer, a new contact or a company not yet recorded. The CRM panel helps examine those relationships beside a conversation. It is available only when CRM is enabled and the reader has the relevant authority. Recognizing an address does not automatically publish the thread to everybody who can read that customer record.
Examine matches before creating another contact.
The panel examines participants and shows permitted contact or company matches and available customer context. Review names and addresses before choosing a match. A domain-based company suggestion is a proposal, not verified identity or legal company information. A familiar display name is not proof that two addresses belong to the same person, especially with shared addresses or external consultants.
- Participant matching with reviewable company suggestions
Maintain contact details under CRM permissions.
Where permitted, add a participant address to a record or create a contact or company through the supported workflow. Parsed signature details can help prepare fields such as name, phone and role, but need human review. The operation uses the owning module's validation and your authority. Creating a contact is not permission to disclose every message that person has ever sent.
Give the record access to one conversation
People who may read this record can then read the thread.
Share one thread with the record's actual audience.
Explicit sharing makes the thread visible in the record timeline to colleagues who may read that record. For personal mail, only its owner can share or unshare; for shared mail, suitable response authority is required. Unsharing ends that record-based access. Read the whole thread before widening its audience. The rest of a personal mailbox remains private and is not converted into a team inbox.
- Explicit thread sharing and withdrawal with record-based visibility
A concrete workflow
Inspect
Identify the participants and existing customer matches.
Maintain
Review suggested fields and update only the intended record.
Review audience
Read the thread and consider who can read the customer record.
Share or withdraw
Make or remove the explicit thread share through the permitted workflow.
An illustrative working example
Illustrative scenario: a new customer representative
A customer introduces a new representative by email. The account manager checks whether the address already matches a CRM contact, reviews the signature and adds the correct details. A project decision in the thread should be visible to the customer team, so the manager reviews the audience and explicitly shares it with the right record. Personal scheduling discussion in another thread stays private. If the association was wrong, the manager withdraws that thread share rather than assuming a contact edit will hide it.
Questions about this topic
Does an address match share the thread?
No. Matching and sharing are distinct. A thread needs an explicit share to the chosen record.
Who can see a shared conversation?
Colleagues permitted to read the associated record can see its shared thread in that record's timeline.
Can an administrator share my personal thread?
Only the personal mailbox owner may share or unshare it. Shared accounts follow their own response authority.
Is CRM required for email itself?
No. The CRM panel is optional and appears only with the relevant module and access.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
HubSpot
Application concept: Review HubSpot contact identities before mapping a conversation participant to the intended customer record.
Salesforce
Application concept: Separate Salesforce contact identification from the explicit decision to disclose one email conversation.
Gmail
Application concept: Choose a Gmail thread suitable for customer-record sharing after reading the full conversation and its audience.