Domain Setup
Prepare transactional email for live delivery by verifying the sending domain and sender identity your application will use.
Before an application can send transactional email reliably through Leadpush, the workspace needs a verified sending domain and a verified sending address under that domain. These steps establish the sender identity mailbox providers and recipients will see.
Domain verification and sender verification are separate
Leadpush transactional sending depends on two related setup steps:
- Sending domain verification, which proves the workspace is authorized to send from that domain
- Sending address verification, which confirms the specific sender mailbox under that domain
Both matter. A verified domain without a verified sender address still leaves the application without a fully usable sender identity.
Use the dashboard guides for the exact setup flow
For the step-by-step dashboard workflow, use:
- Workspaces -> Email -> Sending Domains when you are already inside a workspace and need the exact settings flow
- Add a Sending Domain when you want the broader onboarding version of the same setup
Those guides cover how to:
- create the domain record
- review the DNS entries Leadpush generates
- verify the domain after DNS is published
- create sending addresses under the domain
- complete the sender-address email verification step
Recommended order for transactional senders
Create and verify the sending domain
Publish the DNS records shown by Leadpush and confirm the domain is verified before planning live transactional traffic.
Create the sending address your app will use
Add the mailbox and display details under that domain, then complete the email verification step.
Confirm the address fits the use case
Make sure the sender name, reply-to address, and mailbox are appropriate for the operational mail you plan to send.
Test from the application path
After credentials are in place, send a real test from the application to make sure the sender identity appears as expected.
Best practices for transactional senders
- Use a sender address your team monitors for replies, operational issues, or customer confusion.
- Keep transactional sender names clear and functional so recipients recognize the message immediately.
- If your team wants clearer separation from promotional traffic, reserve a sender identity specifically for operational mail.
- Re-test after changing the domain, sender address, or reply-to behavior.