Follow-up emails landing in spam? Run the deliverability DNS check

If your follow-up emails are landing in spam folders instead of inboxes, the most common cause is missing or misconfigured DNS records on your sending domain. The Cadence deliverability page (https://km-florist-receptionist.vercel.app/cadence/deliverability) checks those records for you and tells you exactly what to fix.

Run the check

1. Open /cadence/deliverability.
2. Review the DNS record status rows. Each row is one record the check looked at, with its current status.
3. For any record that isn't passing, open its recommended fix - the page spells out what to change for that specific record.

Apply the fixes

The fixes are DNS changes, so you make them wherever your domain's DNS is managed - your registrar or DNS host (GoDaddy, Cloudflare, Namecheap, and so on). For each failing row:

1. Copy the recommended fix from the deliverability page.
2. Sign in to your DNS host and add or edit the record exactly as recommended.
3. Save, then give the change time to propagate - DNS updates can take anywhere from minutes to a day or so depending on your host.
4. Come back to /cadence/deliverability and re-check. The row should flip to passing once the record is visible.

Why this matters

Inbox providers decide where to file your email based partly on whether your domain's DNS proves the message really came from you. When those records are missing, even perfectly good follow-up copy gets filed as spam, and your open rates on /cadence/flow will sag no matter how strong the sequence is. Getting every row on this page to pass is the single highest-leverage fix for follow-up deliverability.

If a record still won't pass

Double-check that you added the record to the exact domain the check expects, not a www subdomain or a different domain you also own. Typos in copied values are the other frequent culprit - re-copy the recommended value from the page rather than retyping it. If it still fails after propagation time, open a support ticket and include which record row is failing.

Still stuck? Submit a ticket from this help center and we'll take it from there.