Configure email sending
Choose quick-start or branded-domain delivery, verify the sender state, and test the identity recipients will see.
See it in Leado
What you’ll achieve
- A testable sender whose visible identity and verification state match the delivery route selected for the campaign.
What you’ll need
- Permission to send on behalf of the brand
- For branded-domain sending: access to the domain’s authoritative DNS settings
Follow the workflow
-
1
Open Settings → Email
Review the sender state for the selected workspace. Quick-start campaigns can use Leado’s shared verified sender; a paid branded-domain setup uses Amazon SES after DNS verification.
-
2
Choose the appropriate sender route
Use quick-start for initial testing when the shared sender is available. Use a branded domain when recipients must see and authenticate your organization’s own sending domain.
-
3
Configure a branded domain when required
Enter the owned sending domain and sender details, then copy every displayed SES verification record into the authoritative DNS provider exactly as shown.
-
4
Check verification state
Allow DNS propagation, return to Settings, and run Check verification until the branded domain is shown as ready. Do not interpret a saved domain as a verified sender.
-
5
Save an email and send a test
Use Send test email from a saved draft. Confirm the visible From name and address, subject, rendering, links, inbox placement, and whether the expected quick-start or branded identity was used.
Verify your work
- Settings shows the intended quick-start or branded sender state without a blocking warning
- For a branded domain, every required SES DNS record is published and verification is ready
- A real inbox test shows the expected From identity and working links
If something doesn’t look right
A branded domain remains pending
Compare every DNS name, type, and value, remove accidental domain duplication, and allow propagation before checking again.
Send test is disabled
Save the email draft and resolve the sender or provider warning for the active workspace.
The test uses an unexpected sender
Verify the active workspace and whether the campaign is using quick-start or its configured branded domain.
Limitations and safeguards
DNS verification establishes technical sender readiness but does not guarantee inbox placement; reputation, content, authentication alignment, and recipient engagement still matter.
Important notes
Do not send a customer campaign while the sender is unverified or while the delivery provider remains in a restricted sandbox state.