How to configure a Custom Sending Domain

This article is for certification brands, training companies, and all types of trainers.

All customers can configure a custom sending domain so their clients receive messages from their own domain, not from Workshop Butler. Depending on the type of your account, you can use your domain to send these messages:

For certification brands:

For training companies and trainers:

Configuration Guide

To configure a custom sending domain, you must have access to your DNS records. This way SparkPost - the service we use to send email messages - can prove that you're the owner of the domain. 

Add a custom domain

Go to Account Settings -> Settings and locate the section Custom Domain. Click Activate and add your domain, like

Important note: do not include prefixes like 'www' or 'https' when adding a domain.

Update DNS records

As soon as you add the domain, the system provides you with instructions on what to do next. It should look like this:

Now it's time to go to a DNS panel and add two records:

  • TXT record
  • CNAME record.

After that, you'll wait for about 10-20 minutes and click Check Verification. This time is usually enough but it could take up to 24 hours for DNS records to update. 

Change Company Contact and From address

You may need to update your company contact and From address, if they belong to a different email domain that you added and verified. Workshop Butler lets you know about it.

The moment a verification is over and your company contact and From addresses are correct, Workshop Butler starts using your domain to send messages to your clients.

Check the SPF record

Make sure that the SPF record for your domain authorizes SparkPost (our email provider) to send emails from it. Otherwise, there is a chance that WSB notifications will be rejected or marked as Spam by a receiver.

To add Sparkpost to autorized senders, add "" to your SPF record. For example, like this: TXT "v=spf1 ~all"
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.