Emails sent on behalf of users represent a unique category of communication, where a system or service sends out messages as if they're originating directly from an individual user. Unlike transactional or marketing emails, which are typically from businesses to users, these emails act as a proxy, allowing for automated yet personalized interactions between users or between a user and their contacts.
📄️ Example Sending Flow
This flowchart displays the process of a user sending a support request email to a user of a SaaS service. Upon the SaaS service detecting the email, it utilizes an LLM model to analyze its content and subsequently formulates a response. The reply is then sent on behalf of the SaaS service user, ensuring the end recipient perceives the response as coming directly from the user, not the SaaS platform itself.
📄️ "Via Provider"
In this simple approach, your SaaS platform sends emails on behalf of the user, similar to how transactional emails are dispatched. The distinguishing feature is that the user's name appears as the sender name in the email header, while the actual email address remains that of the service.
📄️ 3rd-Party DNS Setup
This approach allows your SaaS service to send emails with the user's domain name, making the emails look more authentic.
📄️ Direct account access
By obtaining direct access to your users' email accounts, you can seamlessly send emails as if the user themselves initiated it. This method involves connecting to the user's SMTP server, authenticating as the user, and dispatching the email.