Domain authentication supports sender identity but does not guarantee inbox delivery. Plan changes with the person responsible for existing email services.

Before you beginConfirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.

Step by step

  1. Record the current From address, Reply-To destination and authenticated sending domain.
  2. Confirm ownership of the proposed domain or subdomain and inventory existing DNS and mail dependencies.
  3. Review the account-generated authentication requirements in Email Services. Use its exact values rather than a generic example.
  4. Have the authorized domain administrator assess conflicts and approve the change before any DNS edit.
  5. After a separately authorized setup, verify domain status and the assignments for the intended email categories.
  6. Inspect a controlled received message, reply routing and authentication results. Monitor failures before increasing sending volume.

Expected result

The team can explain the sender identity and verify the intended category uses the approved domain.

Troubleshooting

  • Do not delete existing MX or SPF records to resolve a conflict without checking their owner.
  • A verified domain and a completed SSL certificate are separate setup results.
  • Check reputation, list quality and content when authenticated email still misses the inbox.

Supporting documentation

These links open the provider’s documentation. Availability and permissions depend on your account.

More guides

Create and verify a contactKeep a single useful customer record, check the business context, and confirm your changes saved.
Review and respond to a conversationFind the right thread, review its history, and check the channel and recipient before responding.
Check a website lead form before launchFollow a controlled submission from the public form to the correct contact and follow-up process.
Prepare an authorized private integrationDefine the business, owner and permissions before an administrator grants a developer access.