AI for Email Marketing Specialists

Generate 25 subject-line variants for this email send. Inputs: the send purpose, the audience segment, the offer or content, the brand voice, the 3 highest-performing recent subject lines from this program, the character-count target across Apple Mail, Gmail, Outlook, and Yahoo preview windows. Output: 25 subject lines with the preview text per line, grouped into 5 strategic angles (curiosity-gap, specific-benefit, social-proof, urgency-without-spammy, value-tease). Each line under the character target. Avoid all-caps, excessive emoji, and the spammy patterns Gmail and Yahoo authentication-aware filters now weight against. Email context: [paste].

Architect a 7-email onboarding lifecycle for a SaaS product. Inputs: the activation event the program drives toward, the persona segments and their share of the new-user population, the brand voice reference, the technical sender setup, the current welcome-flow performance baseline. Output: 3 lifecycle architecture options, each with the 7-email sequence (subject-line theme, send-day, body angle, primary CTA, branching condition), the success metric per email, the suppression-and-re-entry rules, the recommendation. Product context: [paste].

Write the Liquid template for a dynamic-content email block with conditional logic. Conditions: subscriber segment, last-action timestamp, product-recommendation feed from the ESP catalog, dark-mode preference. The template must render correctly in Outlook 2021, iOS Mail, Gmail web, and Gmail dark mode. Output: the Liquid block, the testing matrix, the fallback content for null cases. ESP: [Klaviyo, Iterable, Marketo Engage, Customer.io, Braze, HubSpot — specify].

Diagnose this deliverability issue. Inputs: the send volume and recent trend, the Gmail and Yahoo authentication setup (SPF, DKIM, DMARC alignment, BIMI status), the complaint rate over the last 30 days, the engagement metrics by mailbox provider, the recent content changes to the program. Output: the 3-5 most likely root causes ordered by probability with the disambiguating signal for each, the immediate-action checklist for the next 24 hours, the 30-day remediation plan, the monitoring metrics the program watches during remediation. Context: [paste].

Draft the welcome-series cadence-and-content brief for our marketing operations team to load into [ESP]. Inputs: the 5-email welcome series, the segment-entry trigger, the per-email content with subject, preview, hero, body, primary CTA, fallback for dynamic-content nulls, the suppression rules against our other programs, the exit conditions to the post-onboarding nurture, the QA-and-render-test checklist. The brief should load into the ESP without follow-up questions from the operations team. Welcome series context: [paste].

Generate the abandoned-cart sequence for an ecommerce program. Inputs: the cart-abandonment trigger, the product-data feed, the discount-strategy guidance, the brand voice, the existing customer-segment performance baselines. Output: 4 emails over 7 days with the timing rationale, the dynamic-product-recommendation block per email, the branching condition that exits a converted subscriber, the suppression against the broader-promotional cadence, the post-sequence reactivation handoff. Brand and product context: [paste].

Audit this email template for accessibility. Inputs: the rendered HTML, the alt text on each image, the heading-tag hierarchy, the link-text clarity, the color-contrast ratios against WCAG AA and AAA, the dark-mode behavior, the text-only fallback. Output: the per-issue list with severity, the recommended fix, the testing approach to verify the fix. Voice: rigorous, the way an accessibility-first email program reviews every send before deployment. Template: [paste].

Translate this campaign performance report into the stakeholder narrative for the marketing leadership team. Inputs: the campaign goal, the headline metrics (sends, open-proxy where applicable, click-through, downstream conversion, revenue per recipient), the segment-level performance, the A/B test results with statistical significance, the qualitative customer-feedback signal. Output: the 1-page narrative report with the lede, the data section with the visualization recommendations, the wins-and-misses synthesis, the next-cycle priorities. Voice: clear, specific, the way a senior lifecycle marketer presents to a CMO. Inputs: [paste].

Draft the win-back sequence for subscribers dormant 90-180 days. Inputs: the dormant-subscriber definition, the prior engagement pattern of the cohort, the win-back-offer strategy, the brand voice, the deliverability-floor considerations for re-engagement to a partially-cold cohort. Output: a 3-email win-back sequence with the timing, the subject-line and content strategy designed for the re-engagement deliverability discipline (low-volume initial sends, engagement-based progression, hard-suppression on the no-engagement cohort), the exit conditions to either the reactivated segment or the sunset workflow. Context: [paste].

Generate the A/B test brief for [test hypothesis]. Inputs: the metric the test optimizes, the audience segment, the variant definitions, the sample-size requirement for the statistical-significance target, the test-duration plan, the success-criteria definition, the rollback-or-rollout plan based on the outcome. Output: the structured brief the marketing operations team and the leadership stakeholders sign off against before the test deploys. Voice: rigorous, specific, the way a senior lifecycle program runs its testing roadmap. Test hypothesis: [paste].

Draft the 6-issue editorial calendar for our customer newsletter. Inputs: the audience segments and their interests, the company's product roadmap milestones, the brand voice, the prior-issue performance signal, the cross-functional content sources (product, customer success, marketing, leadership). Output: 6 issue-by-issue plans with the theme, the lead story, the 3-4 supporting sections, the CTA placement, the cross-functional contributor and the deadline per issue. Voice: editorial, substantive, the way a newsletter audience earns retention over the long run. Inputs: [paste].

Help me think through whether to migrate from [current ESP] to [target ESP]. Inputs: the current send volume and program complexity, the deliverability and engagement baselines, the AI-feature gap that motivated the migration consideration, the integration-with-product-data layer, the team size and migration-execution capacity, the contract-and-pricing comparison. Walk through: the realistic 12-month TCO comparison, the deliverability-reputation-rebuild risk during migration, the data-portability and template-rebuild scope, the team-training requirement, the recommendation with the reasoning. Frame as advice from a senior lifecycle director I would actually trust.