---
name: email-marketing-operations
description: "Build email segments, templates and lifecycle campaigns from approved audience rules. Use when the user requests email marketing operations. Select relevant methods for the requested outcome; unrelated tasks do not require this skill."
metadata:
  version: "1.0.1"
---

# Email Marketing Operations

Build email segments, templates and lifecycle campaigns from approved audience rules.

## OLLIE Runtime integration

Use this capability under the active OLLIE Operator. Read live Workspace Context and tenant bindings for client facts and required inputs. This generic package contains no client configuration. Consume ask-ollie-authority-core for authority, outloop-access-fallback for access and recovery, email-lifecycle-core for communication, and the bootstrapper Runtime Contract for ownership, scheduling and completion. Preserve domain constraints; this Skill creates no competing execution path. Use one method, combine skills, or fill missing steps with authorized tools as the task requires.

External access uses the active Workspace’s approved Outloop capabilities. Never request, read, embed or expose credentials. A service named in a method is a possible dependency, not an access grant. Local file and application work uses the host’s authorized tools.

## Required inputs

- Audience consent and suppression rules
- Campaign objective
- Approved content
- Provider capability

## Methods

### Define segment membership

Define inclusion and exclusion rules before counting recipients. Test intersections, suppression and unsubscribe behavior with synthetic contacts.

### Map lifecycle transitions

Map lifecycle entry, exit and re-entry conditions; prevent overlapping automations from sending the same message for one event.

### Prepare and preview content

Draft subject, preview text, body, links and personalization fallbacks. Check mobile rendering and plain-text alternatives and validate all destinations.

### Verify delivery state

Separate saved content, scheduled delivery and actual sent state. Verify audience size and approved sender immediately before an authorized send, then read the stored provider state.

## Completion

Verify findings against source evidence and read back the resulting artifact or authorized change. Report inputs used, methods selected, output location, assumptions and unresolved dependencies. Do not report a plan, queue entry, draft, test fixture or accepted request as a completed external action. Use the task’s requested format; if a tool is unavailable, finish independent work and identify the exact unfulfilled deliverable.

## Test before relying on it

Read [the synthetic evaluation cases](references/evaluation.md) for activation, output and isolation checks. These cases are test instructions, not evidence that a host or provider test has passed.

## Additional operational methods

Read [focused operational guidance](references/provider-planning.md) for email marketing operations decisions that require deeper reconciliation.