Suppression and Frequency Cap Review (QA)

Suppression and Frequency Cap Review (QA)

1. 01

   Pull the last 30 days of send volume per contact from the client's engagement platform

   Export raw send logs rather than dashboard totals. Dashboard rollups often exclude transactional sends, which is where duplicate contact risk hides.

2. 02

   Flag any contact who received more than 4 marketing messages in a rolling 7-day window

   Four is a defensible starting ceiling for most B2B and DTC retainers. Tighten to 2 for high-ticket or long-consideration client segments.

3. 03

   Cross-check suppression lists against the client's own do-not-contact file and any prior unsubscribe exports

   A contact who unsubscribed in a legacy ESP but still appears active in the current platform is a compliance exposure, not a data hygiene nit.

4. 04

   Verify that failed renewal and abandoned checkout sequences respect the same global cap as promotional flows

   Recovery tools such as Snagr run their own send logic, so confirm the cap is enforced at the contact level, not per-campaign.

5. 05

   Confirm quiet hours and timezone logic match the client's stated policy in the retainer agreement

   Document the exact window in the QA log. If the client has no stated policy, propose one and get written sign-off before the next send cycle.

6. 06

   Test one live contact record end to end through a triggered journey and count actual messages received

   Use an internal seed address. Platform previews frequently undercount messages that fire from overlapping entry criteria.

7. 07

   Log every override, exception, and unresolved conflict in a shared QA register with an owner and a due date

   Unresolved suppression conflicts are the most common cause of client escalations in month two of a lifecycle retainer.