First of all, as a clarification, the Coaches Console uses SendGrid (3rd party email delivery system) to deliver the emails the coaches send to their clients, in the name of the coach's email address. So, your Console emails will appear to the client as sent via Coaches Console in the name of the email address you specify in your Console Communication Settings.
If you do not authorize the Coaches Console system to send on your behalf (in the name of the email address you use in your communication settings), then the recipients' end (the addresses you send to) cannot be sure it's really you sending the emails via the Console or perhaps somebody else trying to impersonate you (also know as spoofing). And they may place your Console emails in the spam folder or even reject (bounce) them.
So, when it comes to preventing potential spoofing alerts triggered by your Console messages in your clients' email inbox or bounces (your Console emails being rejected), we strongly recommend that you authorize the Coaches Console system to send emails on your behalf with the major sender authentication methods: SPF, DKIM, DMARC and domain branded tracking links.
These will significantly improve the sender legitimacy and delivery rates for the emails that you send from the Coaches Console system.
Important: All these require that you have a custom domain email address. You will not be able to implement sender authorization for the Coaches Console on a free email address (such as Gmail, or similar), because you need to own the domain name in order to have access to the DNS records and make the necessary changes and additions.
1. How to implement the SPF
You can go into the DNS records list of your email domain name, then to the SPF (Sender Policy Framework) TXT entry and add Coaches Console as an authorized sender, like this:
v= [what you already have... plus] include:spf1.coachesconsole.com ~all
So, you just need to type or copy/paste "include:spf1.coachesconsole.com" (without the double quotes) to the rest of the SPF specifications before the closing "~all" bit.
Important: Do not create a new TXT SPF entry where you include the Console email server. You already have a TXT SPF entry in your custom domain DNS settings, and that is the one you need to edit to include the Console email server along with the other email servers that you authorize to send in your name. Having two or more separate TXT SPF entries is a setup that does not work.
2. How to implement DKIM, DMARC and domain branded tracking links
For these we need to send you an email with domain specific instructions. So, you can submit a support ticket to let us know you you want to implement these methods and we will send the respective email.
Important: Adding DKIM and DMARC records to your DNS is a more complicated setup that requires a bit of technical expertise. You can ask your domain name host and/or email service provider to add the DNS entries.
If their support is unsure what to do, please contact us via a support ticket to let us know.
A special scenario:
If you have a custom domain email address linked to G-Suite (a Google account), then please check this Google FAQ on the topic:
Comments