Review details before setting up Send through External Email Services, including details about triggers and workflow rules and information for organizations that use Communities.
Required Editions
| Available in: Lightning Experience |
| Available in: Essentials, Professional, Enterprise, Performance, Unlimited, and Developer Editions |
When setting up Send through External Email Services:
- The feature isn’t available in Communities. If your organization has the feature turned on, emails sent in Communities go through Salesforce or Email Relaying instead, depending on which option your organization has configured.
- The feature isn’t available for Einstein Activity Capture or Salesforce Inbox users. Those users’ emails are already sent through their connected Gmail or Outlook account.
- If you use Send through Gmail, have your users visit their My Email Settings page in Salesforce to customize the name that shows in the From field of their outgoing emails. If you use Send through Office 365, you can’t change the name in Salesforce.
When using Send Through External Email Services:
- Emails aren’t stored in Salesforce email logs, which means email delivery information isn’t available in Salesforce. Salesforce email logs are only used for emails sent through Salesforce. Obtain email logs from Gmail or Outlook instead.
- List emails and emails sent by triggers and workflow rules are still sent through Salesforce.
- Emails sent from organization-wide email addresses are still sent through Salesforce.
- Bounce management isn’t supported, so contacts and leads aren’t automatically updated with bounce information. However, you can view bounced emails in your email inbox. If you require bounce management, use Send through Salesforce instead versus an external email service.
- Transport Layer Security (TLS) is handled through the external email service and not through Salesforce settings.
- Organization-wide footers don’t appear in emails sent from Salesforce.