An email message created by our integration will use the Single Email message method, and count towards your organization's limit. We have introduced a feature that aims to mitigate this by diverting as many messages away from the method as possible, which is useful if you are close to hitting any of those limits.
If your organization was created before the Spring '19 release, sending emails through flows won't count towards the daily limit.
if your organization was created after that, this method won't serve any purpose.
By checking the configuration item under the Unbabel for Service Cloud Configuration menu, it is possible to have email messages be sent from a custom flow instead, provided they meet some requirements.
In order for an email to be sent, it must match certain criteria. The email cannot include:
- attachments.
- CC addresses.
- BCC addresses.
- more than 5 "To" addresses.
In order for the process to work, it is also necessary that your Organization hasn't opted in to or been created using the new Message ID threading behaviour. It needs to use the string-based Ref ID threading instead, or else the native threading behaviour from SF will break while using the feature.
You can learn more about this topic, and see how to check which you are running, in this SF article.