How can I authorize the Coaches Console email server to send in the name of my custom email address?


First of all, as a clarification, the Coaches Console uses SendGrid and Newsman (3rd party email delivery systems) 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.

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), there are a few scenarios:

1. The recommended solution: you have a custom email address (hosted on your own external domain name; e.g.: In this case you can go to the SPF (Sender Policy Framework) settings of the email address and add Coaches Console as an authorized sender, like this:

v= [what you already have... plus] ~all

So, you just need to type or copy/paste "" (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.

This specification will communicate to any email receiving server that you authorize Coaches Console to deliver emails in the name of your address and thus the trust issue and the spoofing alert should no longer be a problem. Here is an example of how the SPF entry is setup in a domain name hosted on GoDaddy. (Below is a screenshot of how the SPF settings look like in the GoDaddy interface.) The interface and settings are pretty much the same for all domain name hosts. If you encounter difficulties with this, you can contact the support of your domain name host.


* In the Host field, you can simply put @.
** TTL means time-to-live or the interval after which the SPF changes become effective, from the moment you save them. You can choose other values, starting from 1/2 hour (it may depend on the host interface).

Important: Besides an SPF Record, adding DKIM and DMARC records to your DNS is a more complicated setup that requires expertise. So, unless you can work with someone qualified, our recommendation would be to not create these DKIM and DMARC Record DNS entries. If they are not setup the right way, they can interfere with the SPF Record and cause more delivery issues than it solves.

If you do have a tech person to help with setting up DKIM and DMARC, please contact us via a support ticket. We will take care of the needed settings in this regard on our end and then provide you with information you need to finish the setup on your domain's end.

2. If, on the other hand, you do not own a domain name and custom email address, but instead use a free email address provider (like when you are using a Gmail or a Yahoo address, etc.), then you do not have access to the SPF settings of the email address. In this case, please submit a support ticket about the issue and we will investigate the specific situation for you.

3. If you have a custom domain email address linked to G-Suite (a Google account), then please check this Google FAQ on the topic:

Have more questions? Submit a request


Powered by Zendesk