Enhanced Email Verification for Campaigns!

Previously, From email addresses on campaigns were not verified. That oversight made identity spoofing possible and could damage sender reputation.

To enhance security, we now require verification of your From email address before sending an email campaign. Only valid, verified addresses can be used — preventing anyone from spoofing your sender identity.

When Verification Is Not Required

Two cases skip the OTP verification step:

If your sending domain is one of the custom domains issued under Adaptive AI Email, ownership is already verified and the From address is trusted automatically.

If the From address matches the Location admin email already saved in your settings, it's treated as verified — no OTP required.

How to Verify Your Email

Navigate to Email Marketing and start a new campaign.

In the sender email field, type the address you'd like to use as the From address.

A Verify Now button appears next to the unverified address. Click it to trigger the OTP email.

Open the email at the address you entered, copy the 6-digit One-Time Password, and paste it into the verification dialog.

Once the OTP is accepted, the address is verified and can be used as the From email for any future campaign.

Verified addresses persist across all your campaigns — you only need to verify each address once.

Verify From the Settings Page

You can verify an address before you start a campaign by going to the settings page and clicking Verify an email. The OTP flow is identical to the in-campaign one.

Frequently Asked Questions

Before you begin

“Enhanced Email Verification for Campaigns!” is part of the Marketing → Marketing Settings area in Adaptive AI. Configure defaults, tracking, sender details, and connected accounts. Email configuration affects deliverability, reputation, consent, and reporting. Test the exact sender, content, links, and recipient state before sending to a real audience. The objective is not merely to save a setting; it is to confirm the result works for the staff member or customer who will depend on it.

• Confirm the sending domain or provider is connected, authenticated, and approved for the From address you plan to use.
• Verify the audience has appropriate consent and exclude unsubscribed, bounced, suppressed, or otherwise restricted recipients.
• Prepare a small internal test segment with multiple mailbox providers and complete contact fields for merge-value testing.
• Review the subject, preview text, sender name, reply-to address, links, fallback values, and required business identification.
• Check whether the email is part of a campaign, workflow, course, invoice, or system notification so you test the correct sending path.

Verify the result

After completing the instructions in this guide, use a controlled test before treating the setup as finished. A saved screen or success message confirms configuration, but only an end-to-end test confirms the business outcome.

1. 1Send to the internal test segment and confirm each mailbox receives the message from the intended sender without broken merge values.
2. 2Open the message on desktop and mobile, then test every link, image, button, reply path, and unsubscribe control.
3. 3Review delivery logs for accepted, delivered, bounced, blocked, complained, opened, and clicked events where available.
4. 4Confirm replies return to the correct inbox and that the related contact conversation or workflow updates as intended.
5. 5Only expand the audience after the test content, recipient filters, timing, and tracking behavior are all correct.

Troubleshooting checklist

If the result differs from what you expected, preserve the current state and isolate one variable at a time. Start with the checks below before deleting the configuration or rebuilding it from scratch.

• Check domain authentication, provider status, From-address alignment, and sending limits when messages are rejected or never leave the queue.
• Review suppression, bounce, complaint, unsubscribe, and invalid-domain status for a recipient-specific delivery failure.
• Use the email log and provider response rather than repeated test sends to identify the exact rejection or deferral reason.
• Confirm merge fields have fallback values and that the test contact contains the data expected by the template.
• Compare campaign or workflow scheduling, account time zone, smart-send rules, and quiet hours when delivery is delayed.

Best practices

• Send relevant content to well-defined segments and avoid sudden volume increases that can damage domain reputation.
• Use one recognizable sender identity, working reply path, accurate subject, and clear unsubscribe option in marketing messages.
• Remove chronically invalid addresses and investigate complaint or bounce spikes before sending the next campaign.
• Keep templates focused, accessible, mobile-readable, and free of unnecessary tracking or image weight.
• Record major sender, domain, audience, and automation changes so deliverability shifts can be traced to a specific event.