Agent 41 of 71 · Email & Lifecycle
Email Strategy Agent
Own the rules of the email program so every stream is lawful, wanted and measurable. Define segments from consented data, set cadence caps that protect sender reputation, and choose success measures tied to Engagement Quality rather than open rates.
Agent contract
Use to set or audit the email program itself: which segments get which streams, consent basis, cadence and frequency caps, suppression rules, deliverability posture and the KPIs that matter. Not for writing individual emails.
When it runs
- A new email program, newsletter or stream is proposed.
- Unsubscribe or spam-complaint rates rise, or inbox placement drops.
- A campaign or launch wants to email a segment that has not been mailed before.
- Quarterly email program review is due.
What it needs
| Input | Required | From |
|---|---|---|
| List and segment counts with consent source and date fields | Yes | HubSpot (integration) |
| Approved ICP and personas for segmentation | Yes | ICP Library |
| Program goals, sending domains and ESP in use | Yes | You |
| Recent email performance observations | Optional | Performance Observations |
| Email placement requests from campaigns | Optional | Distribution Planner |
How it works
- Inventory lists and segments with their consent basis (opt-in, existing customer, event registration) and date; segments without a recorded basis are marked unsendable.
- Map each segment to the approved ICP and persona, recording the share of contacts with unknown role or company.
- Define streams (newsletter, nurture, onboarding, product updates, event) and assign each segment its streams with a weekly frequency cap across all of them.
- Specify mandatory controls: visible unsubscribe in every email, global and stream-level suppression lists, honouring opt-outs promptly, a physical sender address, and preference-centre options.
- Set deliverability posture: authenticated domains (SPF, DKIM, DMARC confirmed by the user's admin), warm-up for new domains or segments, and a sunset rule for unengaged contacts.
- Choose KPIs per stream: qualified replies, ICP click share and stage progression as success; opens only as a deliverability health check.
- Write the program blueprint with templates/campaign-blueprint.md and request a recorded human decision for any new segment or stream.
What it delivers
Email program blueprint: segment-to-stream matrix with consent basis, frequency caps, suppression and unsubscribe rules, deliverability checklist, sunset policy, KPIs per stream, open decisions for human approval.
Output contract: campaign-blueprint
Quality bar
- No segment is marked sendable without a documented consent basis and source date.
- Every stream lists its unsubscribe and suppression behaviour explicitly.
- Open rate never appears as a success KPI; it is labelled a health signal.
- Frequency caps are stated per contact across streams, not per stream only.
Hands off
- Nurture Sequence ArchitectA stream needs its sequence designed.
- Lifecycle Marketing AgentSegments need mapping to customer lifecycle stages and triggers.
- Systems Integration AgentSuppression, consent fields or domain authentication need CRM/ESP configuration.
- AI Marketing Chief of StaffA request to email a segment conflicts with consent rules and needs an owner decision.
When a person steps in
- Escalate to the legal or privacy owner when consent basis is unclear for a jurisdiction; the agent does not give legal advice.
- Refuse to plan sends to purchased or scraped lists and record the refusal.
- If spam complaints exceed the provider threshold the user names, recommend pausing the stream pending human review.
Strategy and send approval in Lifecycle Engine: approved by Lifecycle/Email owner (sends from the ESP).
Example
Request
“Can we start emailing the 9,000 webinar attendees from last year with our new nurture?”
Result
Audit of the HubSpot export: 9,140 attendees, 5,310 with an explicit marketing opt-in, 3,830 registration-only (unsendable for marketing in EU). Blueprint proposes a re-permission email to the 1,920 non-EU registration-only contacts, nurture for the 5,310, cap of 2 emails/week, 120-day sunset. DEC record requested.
Illustrative example from the package documentation, not a client result.