A "from domain" is the domain that appears as the sender in the header information of an email. Note that a “from domain” is configured with less functionality than a “custom domain” which is configured as a from domain with the additional configuration of branded VMTA/URLs/links in the email. With only a “from domain” configuration, you have the ability to send authenticated email (authenticated with DKIM/SPF), but the email links/URLs would be branded with the “custom domain” associated with the VMTA used.

In order to provision a "from domain", open a support case. The provisioning team will configure the "from domain" for your organization along with configurations performed by your IT or domain host provider.

Details required to provision a domain

• Name of the Campaign organizations and pod where the domain should be provisioned. The organization name can be located by logging in to the organization and viewing the name beside the username.
• The domain that you would like to use. The “from domain” cannot be the same domain used for a custom “landing page” domain due to how DNS records work with domain security.

Tip: It is important to choose sub-domain choices for "from" domains, such as email.yourparentdomain.com or info.yourparentdomain.com. In this case, “yourparentdomain.com” is your company domain, root, or parent domain. This is considered a best practice for deliverability. You can contact our deliverability team for more insights on best deliverability practices.

Additionally, if you are using a sub-domain, you have the option of using Acoustic Campaign's reply handling feature. If you chose to use this feature, the following information is required:

• The domain for the organization you provided to be provisioned. If further information is required, a member of the Provisioning team will contact you.
• DNS records are provided via a provisioning case.
• Use these DNS records and implement them for the domain(s) requested. This typically involves logging into the DNS host's control panel and creating the records. Contact your IT team or domain hosting provider for assistance.
• Update the provisioning team once the DNS records are implemented on your end.

Based on your sub-domain choice, Acoustic provides the appropriate DNS records. Note that when using a multi-client shared IP pool, it is required that Acoustic hosts the DNS. If we are hosting the DNS records, we provide our name server records to implement in the clients domains DNS records. If we are not hosting the domain DNS records, these DNS records will comprise of SPF, MX, and DKIM records. In either method, DNS records need to be implemented by the clients IT team or domain host DNS provider.

Implementation of Acoustic provided DNS records and successful validation of your domain ensures your domain is authenticated in the eyes of ISPs.

Provision a "from domain"

Warning: Do not follow the steps below until your Account Representative or Client Success Director places the order and a case is raised. Implementing these steps can cause harm to your system. Do not complete until directed to do so by a provisioning specialist.

1. Create a case with the following information: pod number, org name, sub-domain to configure as a "from domain," and the VMTA where to associate the from domain.
2. The Provisioning team validates the choice of the "from domain" and organization location.
3. The Provisioning team provides the appropriate DNS records.
4. Confirm to Acoustic when the DNS records have been implemented.
5. The Provisioning team adds the domain to the "from domain" settings of your organization.
6. The Provisioning team performs a validation check on your domain, which includes a request to send us an email from the domain within the Campaign organization to validate DNS/authentication end-to-end.

Note: A successful validation confirms that the client implemented DNS records properly. This ensures that records in Acoustic's internal system match what was implemented publicly. If the DNS records do not validate, the case is updated. This typically means the DNS records are either not yet published or there is an error in which the next steps are provided.

If you decided to use the Acoustic Campaign reply handling feature, the domain is added to your organization's email response settings. You are then able to set up your reply forwarding (where you would like the replies to be forwarded to and how the replies should be forwarded).

Once all steps have been completed and provisioning is successful, you can use the "from domain" to send messages.

Acoustic Support and Service experts are available to assist you in navigating your new organization and utilizing your domains. You can reach us via support case or your Account Representative or Client Success Director.