Sender Reputation Gate (QA)

Sender Reputation Gate (QA)

1. 01

   Verify SPF, DKIM, and DMARC alignment on every sending domain before the first sequence goes live

   Check the client's root domain and any secondary outbound domains. A DMARC policy of p=none is acceptable for week one but must be scheduled for p=quarantine within 30 days.

2. 02

   Warm each new mailbox for 14 to 21 days at a starting volume of 15 to 20 sends per day

   Ramp by roughly 10 to 15 percent daily. Skipping the ramp is the fastest way to land a client's domain on a blocklist before the retainer has produced a single meeting.

3. 03

   Cap total daily volume per mailbox at 50 and per domain at 200, then confirm the platform enforces it

   Sequencing tools such as Reply and Klenty will happily exceed these limits if the throttle is left at default. Set the ceiling in the tool, not in a spreadsheet.

4. 04

   Run the full sequence copy through a spam filter check and require a score below 3.0

   Test the actual rendered email, including tracking pixels and any link shorteners. Replace shortened links with the client's own subdomain to keep domain reputation consolidated.

5. 05

   Confirm a suppression list is loaded and syncing across every sending tool in the stack

   Opt-outs, bounces, and existing client contacts must propagate within one hour. Apollo and Amplemarket both hold their own suppression state, so verify the sync rather than assuming it.

6. 06

   Sample 20 outbound messages per week for reply sentiment and unsubscribe language

   Flag any sequence where negative replies exceed 2 percent of sends. That threshold usually signals a targeting or offer problem, not a deliverability one.

7. 07

   Document the bounce and complaint thresholds that trigger a pause, and name who can pull the switch

   A hard bounce rate above 2 percent or a spam complaint rate above 0.1 percent should halt the sequence automatically. Give one named operator on the account authority to pause without escalation.