Building personalization for 10 contacts is a design exercise. Building it for 500 contacts per week is an operations problem. Learn the QA systems and batch workflows that maintain quality at volume.
Use this file to discover all available pages before exploring further.
AP-6 · AI Personalization · 125 XP · ~20 min
The systems you’ve built across AP-1 through AP-5 work beautifully for small batches. At 500 contacts per week, new problems emerge: AI failures, inconsistent quality, personalization that’s technically correct but tone-deaf, and QA bottlenecks that kill the time savings you’re trying to create.This module covers the operational infrastructure for personalization at scale.
Review this email against these constraints:Email: {{email_body}}Check each constraint:1. No banned phrases: "hope this finds you well", "quick question", "just checking in", "I wanted to reach out", "touch base"2. First person singular only (no "we" unless referring to the company product in a specific sentence)3. Single CTA only (one ask, not multiple)4. No exclamation marks5. No bullet pointsReturn: {"passes": true/false, "violations": ["list of any violations found"]}
Evaluate the personalization depth of this email:Email: {{email_body}}Context provided to generate it:- Signal used: {{signal_description}}- Role challenge: {{primary_challenge}}- Individual hook: {{individual_observation}}Assess:1. Does the email reference a specific signal? (yes/no — if yes, quote the specific reference)2. Is the reference specific or generic? (specific = references the actual signal; generic = "companies like yours")3. Personalization level: 1/2/3/4 (using AP-1 spectrum)Return as JSON.
Review this email for factual claims that may be inaccurate:Email: {{email_body}}Source data used:- Company: {{company_name}}- Signal: {{signal_description}}- Contact title: {{job_title}}Flag any claims in the email that:- Cannot be verified from the provided source data- Make specific numerical claims not present in source data- Reference events, people, or facts not in the source dataReturn: {"hallucinations_detected": true/false, "flagged_claims": ["list any flagged phrases"]}
This email failed QA for the following reasons: {{qa_violations}}Original email: {{email_body}}Rewrite the email to fix these specific issues while keeping the personalization signals:- Signal used: {{signal_description}}- Role challenge: {{primary_challenge}}Apply the same constraints as the original prompt.Return ONLY the revised email body.
Run auto-retry once. If the retry also fails QA, flag for manual review — don’t loop indefinitely.
Review queue filtered: all approved_with_notes reviewed
Spot-check: 10% of approved reviewed manually
Final send list: only approved rows exported
Send rate: no more than 50 new contacts/sending domain/day
Quick Check: What are the four automated QA checks? What QA status triggers auto-retry? What percentage of approved emails should be spot-checked manually?