What is email whitelabelling?
Receptive sends email notifications to your team and customers from “email@example.com” by default.
If you’d like to send email notifications from your own domain for example firstname.lastname@example.org or email@example.com, Receptive can do that with our whitelabel email features.
Essentially, you set up some DNS records that prove that Receptive’s mail servers are permitted to sign emails from your domain. Read more about DKIM email signing.
Whitelabelling also helps with branding as your customers will definitely recognize the address your mails are sent from.
|Standard Email||Whitelabelled Email|
What we need to set up whitelabelling
- Ensure your price plan includes email whitelabelling. Email sales to check or upgrade.
- Choose a from email address for example firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, etc (should be a real email address at your actual domain).
- Choose a new hostname that Receptive will send emails from, for example featuremail.yourdomain.com. This should not already exist in DNS.
Note: this URL needs to be different from your white label domain, so choose something different than what you'd select for that. (Example: featuremail.yourdomain.com instead of features.yourdomain.com)
- Choose a hostname that Receptive will use for clicktracking for example featureclicks.yourdomain.com. This should not already exist in DNS
- Send the above information to email@example.com. We’ll configure whitelabelling on Receptive’s servers.
- We’ll notify you that setup is done on our side.
- Grab your DNS records from your Receptive account settings page and pass them to your network administrator to set up on your side. They will look similar to this:
- Once your network administrator has set up the new DNS records, we’ll check them and activate your whitelabel emails.
- Your emails will now be sent to your team and customers from firstname.lastname@example.org. Receptive’s servers will sign the emails on your behalf for maximum deliverability.
Users can reply directly to some notifications, (status changes and comments) and their email reply is routed into your Receptive account. This is done with a special reply-to header on the email that looks something like email@example.com
Suggestions for our email whitelabelling feature?