When you connect (CE) with Salesforce, the system automatically prevents any email addresses marked as “do not contact” (DNC) in either platform from receiving messages from your CE AI email agent (formerly called the “AI assistant”). This ensures that your emails align with the CAN-SPAM Act best practices and are less likely to be flagged as spam.
To make it easy for recipients to opt out, we recommend adding an Unsubscribe option in your email signature.
Requirements
The DNC field in Salesforce must be a boolean field.
The boolean DNC field in Salesforce must be mapped to the one in CE.
One-time DNC sync
To align your DNC records, CE performs a one-time sync where:
CE looks at your Salesforce records and matches any leads that are already in CE by their email addresses. CE uses the email address as the unique identifier for each lead and assigns a Salesforce ID to those leads.
If there are duplicate leads in Salesforce (same email address), CE uses latest modified record and assigns that Salesforce ID to CE lead.
DNC status logic
If a Salesforce lead has a DNC status of false or blank, the CE DNC status updates to true.
If a Salesforce lead has a DNC status of true, the CE DNC status updates to true.
This logic ensures that a lead that is marked as DNC in either CE or Salesforce will be marked on both platforms as DNC, thus ensuring that no communication will be sent to those DNC leads from CE.
Post-sync checks
After the initial sync, CE checks Salesforce on a Just-In-Time (JIT) basis, before the CE AI email agent sends out any communication (initial email and follow-up emails), CE performs a sequence of checks as follows:
If a lead is marked as DNC in CE, the email will not be sent.
CE checks Salesforce for DNC status. DNC status must be either False or blank. If DNC status is not False or blank, email will be sent.
If the Salesforce DNC status is True on the JIT check, CE updates the lead record on CE to reflect DNC=True.
Given this logic, CE always checks just before an email is sent, to get the DNC status of a lead. This prevents an email being sent to a lead that is marked as DNC in either CE or Salesforce.
Given the nature of JIT checks, the DNC statuses across CE and Salesforce are not synced in real-time or regularly. Thus, there may be discrepancies in records at any one time.
Example of a post-sync check
To explain the Salesforce post-sync check, consider a lead that exists in CE but hasn’t been updated for a long time. This lead may have a different DNC status compared to what is in Salesforce. The statuses won’t match until a JIT check is done. When an email is about to be sent to this lead through CE, the JIT check reveals that the lead is marked as DNC in Salesforce. As a result, the email won’t be sent, and CE updates its record to show that the lead is DNC=True.
CE manual DNC requests
When a lead requests not to be contacted through the AI email agent, or if a CE user marks the lead as “DNC” in CE, then if the lead has a Salesforce ID, CE updates the DNC status in Salesforce. If the lead does not have a Salesforce ID, CE cannot update the status.