This is the email identity your campaigns send from — an email concept, not a website address. You either use the built-in managed sender or prove you control your own domain by publishing DKIM CNAME records so the provider can verify it.
Who can do this
- Owners and Admins — can do this for any record or setting in the account.
- Agents and Assistants — cannot do this.
Roles are predefined by NextAccord. See all roles & permissions
Before you start
- Campaigns are included in your plan and enabled for the account.
- Your role can manage campaign senders (Owner or Admin).
- A campaign SES tenant is provisioned and its local state is ENABLED (shown in the SES tenant panel; provision it there if it is missing).
- For an agency domain: access to that domain’s DNS to add CNAME records.
Example
Illustrative example
Managed route: in "Managed NextAccordMail sender" you set Alias to hello, Display name to "Harborview Realty", and a real Reply-To mailbox, then choose Create managed sender.
Agency-domain route: in "Verified agency domains" you enter mail.harborview.example and choose Start verification. NextAccord shows three DKIM records like Type CNAME, Name abc123._domainkey.mail.harborview.example, Value abc123.dkim.amazonses.com.
You add those exact records at your DNS host, choose Refresh, and the identity moves to VERIFIED. You then add a From address, Display name, and Reply-To under that domain.
Steps
- Step 1: Open Settings › Campaign Senders. Confirm the SES tenant panel shows Local state ENABLED; if there is no tenant, choose Provision tenant.
- Step 2: Fastest path — managed sender: in "Managed NextAccordMail sender", set the Alias, Display name, and a real Reply-To address, then choose Create managed sender.
- Step 3: Your-domain path: in "Verified agency domains", enter a subdomain you control (for example mail.yourdomain.com) and choose Start verification.
- Step 4: Copy the DKIM CNAME records from the table (Type, Name, Value) exactly and add them at your DNS provider.
- Step 5: Choose Refresh. When the identity shows VERIFIED and enabled, add a From address, Display name, and Reply-To under it with Add agency sender.
What success looks like
- The SES tenant panel shows Local state ENABLED and provider sending active.
- A managed sender exists, or an agency identity shows Status: VERIFIED with DKIM verified.
- At least one configured sender is available for campaigns to use.
Common problems
- The identity stays unverified after adding records.
- The records must match the Name and Value exactly, as CNAME (not TXT), with no extra domain suffix added by your DNS host. Fix them and choose Refresh; DNS can take time to propagate. An identity may also show a specific failure message in red.
- Create managed sender is disabled.
- The campaign SES tenant is not locally enabled. Provision or resume it in the SES tenant panel first.
- Campaigns still will not send after verifying.
- Verifying a sender does not turn on delivery. Scheduled campaign processing is a deployment-level worker that is disabled by default. Confirm campaigns are enabled for the account and that a sender is configured and authorized.
Reconnect or remove
- Refresh: re-check verification status any time with Refresh on the identity.
- Disable: turn an identity off without deleting it with Disable — it can be re-enabled later.
- Remove: choose Remove to delete the identity and its provider verification (you are asked to confirm). Records you added at your DNS host should then be removed there too.
Good to know
- A campaign sending domain (email identity) is not the same as a landing-page custom domain (a website address). They are configured in different places.