A From domain is the domain that appears as the sender in the header information of an email.

Note: A From domain is configured with less functionality than a custom domain. A custom domain has additional configurations, such as branded VMTA/URLs/links in the email. Custom domains can be used as From domains.

With only a From domain configuration, you can send an authenticated email (authenticated with DKIM/SPF), but the email links/URLs would be branded with the custom domain associated with the VMTA used.

To provision a From domain, you must 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.

Note: You must have a custom domain created before creating a From domain.

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. Having sub-domain choices is considered a best practice for deliverability. You can contact our deliverability team for more insights on best deliverability practices.

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

• The domain for the organization you wanted 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. Implementing DNS records 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: Acoustic is required to host the DNS when using a multi-client shared IP pool. If Acoustic hosts the DNS records, we will provide our name server records to implement in your domains' DNS records. If we are not hosting the domain DNS records, these DNS records will include SPF, MX, and DKIM records. In either method, DNS records must be implemented by your IT team or domain host DNS provider.

Implementing Acoustic-provided DNS records and successful domain validation 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 an end-to-end 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.

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

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

Once all steps have been completed and provisioning is successful, you can use the form 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 by opening a support case or contacting your Account Representative or client success director.