Email to Salesforce
Email to Salesforce is a per-user feature that lets each Salesforce User send or BCC mail to a generated personal Salesforce address, automatically logging the message as an EmailMessage record against matching Contacts, Leads, or other records in the org.
Definition
Email to Salesforce is a per-user feature that lets each Salesforce User send or BCC mail to a generated personal Salesforce address, automatically logging the message as an EmailMessage record against matching Contacts, Leads, or other records in the org. The feature exists so that sales reps using their corporate inbox (Outlook, Gmail, Apple Mail) can capture customer email in Salesforce without installing the full Outlook or Gmail integration. Each user enables the feature individually, receives a unique address like 12345abc@auto.salesforce.com, and adds that address as a BCC on outbound mail or forwards inbound mail to it.
The feature predates the modern Outlook and Gmail integrations and the Inbox product, but remains useful when the integrations are not feasible: users on unsupported mail clients, occasional capture from mobile, or partner organizations where IT has not approved the integration. Logged emails appear in the Activity Timeline of the matching record, threaded with prior conversations, and remain queryable through the EmailMessage object like any other Enhanced Email record.
How Email to Salesforce captures and matches mail
How the address is generated
When a user enables Email to Salesforce, the platform generates a unique address of the form alphanumeric@auto.region.salesforce.com. The address is tied to the user's User record and remains stable for the lifetime of the user (or until the feature is disabled and re-enabled). Each User has one address; there is no per-purpose split, so users cannot have one address for sales mail and another for support mail.
Record matching logic
When mail arrives at the user address, the platform parses From, To, and CC headers and looks up matching Contacts or Leads by email. If a match is found, the email is logged against that record; if multiple matches, it logs against all of them. If no match, the mail logs as an unassociated EmailMessage tied to the user. The matching is exact-match only, with no fuzzy logic; if the customer changes their email or uses an alias, the message will not link to the right Contact.
Per-user enablement
Email to Salesforce is enabled per-user, not org-wide. Users go to Personal Settings > My Email to Salesforce, generate their address, and configure capture options. The admin can enable the feature for the org through Setup, but each user must individually opt in and configure their address. This is unlike the Outlook and Gmail integrations, which an admin can roll out at scale through profile settings.
Auto-association versus auto-Bcc
Two configuration options shape behavior. Auto-Association controls whether the message is automatically logged to matching records. Auto-Bcc controls whether sent mail (forwarded to the address) is logged at all. Most users enable both. Disabling Auto-Association produces unassociated EmailMessage records that the user must manually link to records, which defeats the purpose for most workflows.
Attachments and limits
The standard inbound 25 MB per-message cap applies. Attachments arriving at the user address are stored as ContentDocument linked to the EmailMessage. There is no separate quota; storage counts against the Files allocation. Volume limits also apply: high-volume users may hit per-org caps that throttle further captures, with the platform queuing or rejecting excess.
Coexistence with Outlook and Gmail integrations
Email to Salesforce can coexist with the Outlook and Gmail integrations. Both will log the same message if a user has the integration installed and also BCCs to the auto address. Duplication is the result. Most orgs choose one path: either roll out the integration and disable Email to Salesforce, or keep Email to Salesforce as the universal fallback for users without the integration.
Migrating off the feature
Disabling Email to Salesforce after rollout requires user training. Each user has an existing address habit; removing it without warning means lost capture during the transition period. Plan migration as a phased rollout: enable the new integration, leave Email to Salesforce active for a quarter, communicate the cutover, then disable. Disabling does not delete historical EmailMessage records; existing logged email remains intact.
Roll out Email to Salesforce
Rolling out Email to Salesforce involves the org-level toggle, individual user enablement, and a coexistence plan with any modern integrations already deployed. The steps below cover the full path.
- Enable the feature org-wide
Setup > Email > Email to Salesforce. Check Active. This makes the feature available to users; it does not enable it for any specific user.
- Configure default options
On the same page, set the org defaults: Advanced Email Security Settings (require authentication from the From address), default Auto-Association, default capture behavior.
- Communicate to users
Send a clear how-to to every user the feature is for. Include the path to their Personal Settings, the address generation steps, and the recommended BCC habit. Without this, adoption is near zero.
- User enables and generates address
Each user goes to Personal Settings > My Email to Salesforce, clicks Edit, generates the address, and confirms. They then add the address as a BCC in their mail client.
- Test capture
User sends a test email to a known Contact, BCCs the auto address, and confirms the EmailMessage appears on the Contact within a few minutes.
- Train on unmatched captures
Show users the My Unresolved Items list where unmatched captures land. Train them to manually link unmatched email to records when the auto-match fails.
- Plan coexistence
Decide policy with any Outlook or Gmail integration users. Either disable Email to Salesforce for integration users, or accept duplicate captures and clean up in a scheduled job.
Automatically logs captured email to matching Contacts and Leads by email address. The default and expected behavior.
Logs the email to every matched Contact, not just one. Causes duplicate Activity Timeline entries if the same email appears multiple times.
Requires SPF/DKIM authentication on the From header. Reduces spoofing but blocks captures from senders without proper email auth.
List of email domains to skip (your own corporate domain, common spam domains). Prevents internal-only emails from cluttering records.
Logs sent mail BCCed to the auto address. The standard rep workflow; without it, only forwarded inbound is captured.
- Match logic is exact-match on email address only. Aliases, plus-addressing, and corporate-to-personal forwarding all produce unmatched captures.
- Coexistence with Outlook or Gmail integration produces duplicates. The same email is logged twice, once by each path; users see two Activity Timeline entries.
- Deactivating a user breaks their auto address. Any BCC or forward to that address bounces after deactivation. Cover address cleanup in your offboarding checklist.
- Volume limits throttle captures for high-volume users. The platform queues or rejects excess. Power users may need a coordinated rollout to avoid hitting caps.
- Disabling the feature does not delete historical EmailMessage records, but it does prevent new captures. Plan the cutover with a transition window so users adjust their habits.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is the primary benefit of Email to Salesforce for Salesforce administrators?
Q2. In which area of Salesforce would you typically find Email to Salesforce?
Q3. Why is understanding Email to Salesforce important for Salesforce admins?
Discussion
Loading discussion…