Getting a sending domain properly verified used to be something you had to remember to finish on your own, and it was easy to leave half-done. Now the DNS step is a required part of connecting a mailbox, the records you need are ready to copy, and FirstSales keeps checking on them until they pass.
What changed
When you connect a mailbox now, the connector wizard includes a DNS verification step you have to complete as part of setup, not an optional extra you can skip and forget. The wizard gives you the exact DNS records you need to add at your domain registrar, formatted so you can copy them directly instead of retyping them by hand. That includes the tracking CNAME record, which is easy to miss if you're setting up records manually.
Once you've added the records, you don't have to keep checking back to see if they've propagated. FirstSales re-checks pending DNS records automatically until they verify, so the moment your registrar's changes take effect, your domain shows as verified without you having to trigger anything yourself.
If a sender's domain still isn't verified, the scheduler flags it. Instead of a campaign quietly using an unverified sender, or you finding out after the fact that mail wasn't sending the way you expected, you get a flag directly in the scheduler with a one-click fix that takes you back to the missing DNS step so you can finish it.
This release also closes a related edge case: a domain could previously end up marked as verified based on a stale claim that no longer matched its actual DNS state. That's fixed, so a verified badge in FirstSales now reflects what your domain's DNS records actually say, not what they said the last time a check happened to run.
DNS changes don't take effect instantly once you save them at your registrar; propagation can take anywhere from a few minutes to a longer stretch depending on your registrar and existing DNS configuration. That's exactly why the automatic re-checking matters: instead of you needing to know how long propagation might take for your specific registrar and coming back at the right moment to check, FirstSales keeps checking in the background and updates your domain to verified the moment it actually detects the records are in place.
This also removes a specific failure mode that used to be common with manual DNS setup: copying a record by hand from documentation, a help article, or a support message, and getting a character wrong, a missing dot, an extra space, a truncated value. Because the wizard now gives you the record to copy directly rather than to retype, that class of mistake is far less likely to happen in the first place.
How to use it
When you add or edit a tracking domain, a DNS records modal opens with the values you need to add, the CNAME target and any supporting records, each with a copy button so you can paste them directly into your domain registrar's DNS settings without retyping anything. The mailbox connector wizard walks you through the equivalent SPF and DKIM records for your sending domain the same way, before you finish connecting the mailbox.
After you've added the records at your registrar, you can leave the tab. FirstSales checks pending records on its own on a regular basis, so you don't need to keep refreshing the page to see if verification has gone through. Once your registrar's DNS changes propagate, the domain updates to verified automatically.
If you open your scheduler and see a sender flagged as unverified, click the fix link on the flag. It takes you straight to the DNS step for that sender so you can see exactly which record is missing or incorrect, rather than having to dig through settings to find it.
If you're setting up multiple sending domains at once, work through the DNS step for each mailbox as you connect it. Since verification happens automatically in the background afterward, you can move on to the next mailbox without waiting for the first one to finish propagating.
If you manage sending domains for more than one workspace or client, the same pattern applies across all of them: connect the mailbox, work through the DNS step once per domain, and let the automatic re-checking handle confirming each one as its records propagate, rather than manually tracking which domains are still pending and checking back on each one yourself.
Why it matters
Deliverability depends on your sending domain actually being verified: unverified or misconfigured DNS records are one of the most common reasons cold email ends up in spam or gets blocked outright. A setup flow that lets you skip that step, or that leaves it up to you to remember to check back on propagation, makes it easy to end up sending from a domain that isn't ready without realizing it.
Making the DNS step required, and giving you exact copy-ready records instead of general instructions, cuts down on the most common way this goes wrong: a typo'd record or a missing tracking CNAME that quietly breaks click tracking or authentication. Automatic re-checking means you find out your domain is verified as soon as it actually is, not whenever you happen to remember to look.
The scheduler flag is the safety net for everything else. If a domain somehow ends up unverified when a campaign is about to send from it, you see that before it becomes a delivery problem, with a direct path to fix it instead of having to figure out on your own what went wrong.
Even with the automatic re-checking in place, it's still worth double-checking the records you add match exactly what the wizard gave you, particularly if your registrar's interface trims or reformats values on save; the copy-ready format removes the most common source of manual error, but it can't account for every quirk of every registrar's own DNS editor.
Availability
The DNS verification step is required for all new mailbox connections. Existing connected mailboxes are checked against the same verification logic, and any that come up unverified will show as flagged in your scheduler with the one-click fix available.