ChangelogBook a demoSign up

QA guide

AudienceMarketers, campaign managers
Prerequisites
  • At least one agent with messages configured
  • A connected destination (Braze, Iterable, or Salesforce Marketing Cloud)

Before launching a new AI Decisioning agent or updating content, use this checklist to catch issues early and ensure your messages send as expected.


What you'll learn

In this article, you'll learn how to:

  • QA email messages, including sender details, subject lines, content, links, and targeting
  • QA SMS messages, including text content, personalization, and compliance
  • QA push notifications, including titles, bodies, and deep links
  • Troubleshoot common issues, such as test sends not arriving and personalization errors

Overview

Running QA before launch helps you catch issues that can impact delivery, user experience, and campaign performance. This guide walks through what to check for each channel.

Run through this checklist whenever you launch a new agent, add messages, or make major updates.


Email QA

To QA an email message, go to:

AI Decisioning → Agents → [Your Agent] → Messages → [Your Message]

Use the Content and Configuration tabs as you follow the steps below.

Check sender

  • Check that the sender email address is correct.

Check subject line and preheader

If your message uses variants, preview each one and confirm the Now previewing indicator appears.

  1. Select a variant to preview.

Previewing a subject line variant

  1. Check that the subject line and preheader display correctly.
  2. Make sure personalization (like first name or dynamic fields) shows real user data.

Check body content

If your message uses variants, preview each one and confirm the Now previewing indicator appears.

  1. Select a variant to preview.

Previewing a body content variant

  1. Check that the content matches your intended message and layout.
  2. Make sure images load correctly and include alt text.
  3. Confirm dynamic or conditional content works for different audience segments.

If your message uses variants, preview each one and confirm the Now previewing indicator appears.

  1. Select a variant to preview.

Previewing a CTA variant

  1. Check that all links and buttons go to the correct destination.
  2. Confirm tracking (such as UTM parameters) is set up correctly.
  • Check that the footer displays correctly.
  • Make sure unsubscribe, privacy, and legal links work.

Check timing and targeting

Open the Configuration tab, then go to Advanced.

Configuration tab showing advanced tab dropdown

Check settings in three places:

  1. Message-level settings

Message-level advanced settings

  • Confirm send limits, timing, and audience eligibility are correct.
  1. Variant type settings

Variant-level settings overview

Send limit at the variant type level

  • Confirm send limits for each variant type.
  1. Individual variant settings

Audience eligibility at the individual variant option level

Audience eligibility at the individual variant option level (continued)

  • Confirm audience eligibility for each option.
  1. Make sure the message is turned on.

Message enabled — list view

Message enabled — detail view

Message enabled — confirmation

A message won’t send if it isn’t enabled—even if everything else is correct.


SMS QA

To QA an SMS message, go to:

AI Decisioning → Agents → [Your Agent] → Messages → [Your Message]

Use the Content and Configuration tabs as you follow the steps below.

Check sender

  • Check that the sender ID or phone number appears as expected.

Check title

If your message uses variants, preview each one and confirm the Now previewing indicator appears.

Check body content

If your message uses variants, preview each one and confirm the Now previewing indicator appears.

  1. Select a variant to preview.

Previewing an SMS body variant

  1. Check that the text is accurate, formatted correctly, and not cut off.
  2. Make sure personalization shows real user data.
  3. Confirm dynamic content works for all audience segments.
  • Test all links to make sure they work and track correctly.
  • Check that shortened URLs or deep links open as expected.

Check compliance

  • Make sure opt-out instructions are included (for example, "Reply STOP to unsubscribe").

Check timing and targeting

Open the Configuration tab, then go to Advanced.

  1. Confirm send limits, timing, and audience eligibility are correct.
  2. If settings differ across variants, check variant-level send limits and eligibility.
  3. Make sure the message is turned on.

Push notification QA

To QA a push notification, go to:

AI Decisioning → Agents → [Your Agent] → Messages → [Your Message]

Use the Content and Configuration tabs as you follow the steps below.

Check sender and app info

  • Check that the app name and sender ID are correct.
  • Make sure icons or media display correctly.

Check notification content

If your message uses variants, preview each one and confirm the Now previewing indicator appears.

  1. Check that the title and body display as expected.
  2. Make sure personalization shows real user data.
  3. Check how content appears on iOS and Android (watch for truncation).
  • Test links, buttons, and deep links to make sure they work correctly.

Check timing and targeting

Open the Configuration tab, then go to Advanced.

Push notification advanced congifuration settings

Check settings in three places:

  1. Message-level settings
  • Confirm send limits, timing, and audience eligibility.
  1. Variant type settings

Push variant-level settings overview

Push send limit at the variant type level

  1. Individual variant settings

Push audience eligibility at the individual variant option level

Push audience eligibility at the individual variant option level (continued)

  1. Make sure the message is turned on.

Troubleshooting

To find a message, go to:

AI Decisioning → Agents → [Your Agent] → Messages → [Your Message]

Message test not received

If your test send doesn’t arrive:

  1. Make sure the message is turned on.

Message list showing enabled toggle (state 1)
Message detail showing enabled toggle (state 2)
Message detail showing enabled confirmation (state 3)

  1. Check the identifier.
  • Make sure you entered the correct identifier (for example, email, user ID, or subscriber key).
  • It must match both your channel configuration and the value shown in the test send.

Test send callout showing the identifier field

Channel configuration showing the identifier setting

  1. Confirm the identifier exists in your destination.
  • The user must already exist in your email or messaging platform.
  1. Select a user in preview (SFMC).
  • Go to Settings → Select user before sending a test.

SFMC Settings > Select user dialog

Personalization not working

If personalization appears blank or incorrect:

  1. Check your channel configuration.
  • Make sure the fields you’re using are included (these are the fields sent with each message).

Channel configuration payload fields

Channel configuration payload fields (continued)

  1. Check your user data model.
  • Fields like first_name and last_name must exist on your main user model (AID parent model).

  • If they’re on a related model, you can either:

    • Merge the model into the main user model (so all fields are available in one place), or
    • Add the fields through Configuration → Additional user columns (to include specific fields without merging everything)

Variants not showing

Variant images not displaying

  • Make sure the code snippet is added to your template.
  • Confirm all image URLs are publicly accessible (no login required).

Ready to get started?

Jump right in or a book a demo. Your first destination is always free.

Book a demoSign upBook a demo

Need help?

Our team is relentlessly focused on your success. Don't hesitate to reach out!

Feature requests?

We'd love to hear your suggestions for integrations and other features.

Privacy PolicyTerms of Service

Last updated: Apr 2, 2026

On this page

Was this page helpful?