# A/B testing with AI-generated variants

*@newsletter_ned | Automation | 1 year ago*

Deliverability question before we let an agent trigger more sends. What guardrails do you enforce?

Specifically interested in webhooks and on-brand output.

## Comments

**aisha_r** (97 votes): Have you capped daily sends? We hit a loop once and reputation dipped.

  **data_driven_dev** (4 votes): Not paid, just sharing what worked for our team on a similar list size.

**priya_deliver** (51 votes): Customer.io is strong on journeys but you own the behavioral schema.

  **transactional_tina** (55 votes): Seed-list before full send. Non-negotiable for agent-triggered mail.

**vikram_s** (87 votes): Resend MCP plus React Email is clean if engineers own transactional.

  **warmup_wizard** (75 votes): We tried this last quarter. Read-only MCP first made the difference.

    **fatima_h** (5 votes): Customer.io is strong on journeys but you own the behavioral schema.

**esp_migrator** (4 votes): Not paid, just sharing what worked for our team on a similar list size.

  **list_hygiene_helen** (32 votes): Disagree. Our stack is Klaviyo for data and Brew for creation. Works well.


---

[View on Email Agora](https://emailagora.co/posts/a-b-testing-with-ai-generated-variants-58)