Email Marketing & AI CRM Automation Specialist

Profession 34 · Free learning resource

120 Email Marketing & AI CRM Automation Prompts

A complete, searchable, practical English tutorial for email marketers, CRM operators and remote-work candidates. Discover each workflow, adapt its inputs, copy the prompt, and review outputs before use.

12 modules · 120 prompts · Responsive · Copy ready

How to use this library

  1. Search for a task or browse a module below.
  2. Open a prompt card to read its complete instructions and intended usage.
  3. Click Copy Prompt and replace all bracketed placeholders with your project facts.
  4. Check customer consent, applicable rules, platform documentation and any generated claims before sending or automating.
  5. Build a portfolio using anonymized or fictional examples, and distinguish simulated results from real outcomes.

Reference IDs are organizational labels, not executable WordPress shortcodes. Never provide passwords or API keys to an AI prompt.

Explore the 120 prompts

120 of 120 prompts

No prompts found. Try another keyword or reset the filters.
EMAIL-001 · Strategy & Client Discovery

Marketing discovery interview

Use this template to create a decision-ready brief for marketing discovery interview, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Marketing discovery interview.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a decision-ready brief specifically for “Marketing discovery interview” within the module “Strategy & Client Discovery”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Separate observed facts, assumptions, and questions requiring confirmation. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended marketing discovery interview deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-002 · Strategy & Client Discovery

Business goals and email objectives

Use this template to create an implementable outline for business goals and email objectives, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Business goals and email objectives.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an implementable outline specifically for “Business goals and email objectives” within the module “Strategy & Client Discovery”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include a compact input-to-output map and explain dependencies. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended business goals and email objectives deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-003 · Strategy & Client Discovery

Audience and offer audit

Use this template to create a structured working document for audience and offer audit, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Audience and offer audit.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a structured working document specifically for “Audience and offer audit” within the module “Strategy & Client Discovery”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Specify ownership, timeline, and a minimum viable first iteration. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended audience and offer audit deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-004 · Strategy & Client Discovery

Email program maturity assessment

Use this template to create a reviewer-ready draft for email program maturity assessment, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Email program maturity assessment.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a reviewer-ready draft specifically for “Email program maturity assessment” within the module “Strategy & Client Discovery”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Use clear examples without making up customer facts or performance results. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended email program maturity assessment deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-005 · Strategy & Client Discovery

Brand voice questionnaire

Use this template to create an actionable plan for brand voice questionnaire, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Brand voice questionnaire.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an actionable plan specifically for “Brand voice questionnaire” within the module “Strategy & Client Discovery”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include a pass/fail QA checklist and revision priorities. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended brand voice questionnaire deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-006 · Strategy & Client Discovery

Customer lifecycle map

Use this template to create a decision-ready brief for customer lifecycle map, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Customer lifecycle map.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a decision-ready brief specifically for “Customer lifecycle map” within the module “Strategy & Client Discovery”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Map edge cases, exclusions, and what happens when required data is missing. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended customer lifecycle map deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-007 · Strategy & Client Discovery

Channel integration plan

Use this template to create an implementable outline for channel integration plan, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Channel integration plan.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an implementable outline specifically for “Channel integration plan” within the module “Strategy & Client Discovery”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Show two defensible options and the trade-offs between them. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended channel integration plan deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-008 · Strategy & Client Discovery

Quarterly email roadmap

Use this template to create a structured working document for quarterly email roadmap, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Quarterly email roadmap.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a structured working document specifically for “Quarterly email roadmap” within the module “Strategy & Client Discovery”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Identify privacy, accessibility, and customer trust implications. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended quarterly email roadmap deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-009 · Strategy & Client Discovery

Stakeholder approval workflow

Use this template to create a reviewer-ready draft for stakeholder approval workflow, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Stakeholder approval workflow.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a reviewer-ready draft specifically for “Stakeholder approval workflow” within the module “Strategy & Client Discovery”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include measurable success criteria and a practical verification method. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended stakeholder approval workflow deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-010 · Strategy & Client Discovery

Email program success criteria

Use this template to create an actionable plan for email program success criteria, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Email program success criteria.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an actionable plan specifically for “Email program success criteria” within the module “Strategy & Client Discovery”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Finish with a handoff checklist and follow-up questions. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended email program success criteria deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-011 · Audience, Data & Segmentation

Subscriber data inventory

Use this template to create a decision-ready brief for subscriber data inventory, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Subscriber data inventory.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a decision-ready brief specifically for “Subscriber data inventory” within the module “Audience, Data & Segmentation”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Separate observed facts, assumptions, and questions requiring confirmation. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended subscriber data inventory deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-012 · Audience, Data & Segmentation

Consent status segmentation

Use this template to create an implementable outline for consent status segmentation, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Consent status segmentation.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an implementable outline specifically for “Consent status segmentation” within the module “Audience, Data & Segmentation”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include a compact input-to-output map and explain dependencies. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended consent status segmentation deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-013 · Audience, Data & Segmentation

Lifecycle segments

Use this template to create a structured working document for lifecycle segments, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Lifecycle segments.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a structured working document specifically for “Lifecycle segments” within the module “Audience, Data & Segmentation”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Specify ownership, timeline, and a minimum viable first iteration. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended lifecycle segments deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-014 · Audience, Data & Segmentation

RFM customer segmentation

Use this template to create a reviewer-ready draft for rfm customer segmentation, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: RFM customer segmentation.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a reviewer-ready draft specifically for “RFM customer segmentation” within the module “Audience, Data & Segmentation”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Use clear examples without making up customer facts or performance results. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended rfm customer segmentation deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-015 · Audience, Data & Segmentation

Lead scoring framework

Use this template to create an actionable plan for lead scoring framework, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Lead scoring framework.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an actionable plan specifically for “Lead scoring framework” within the module “Audience, Data & Segmentation”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include a pass/fail QA checklist and revision priorities. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended lead scoring framework deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-016 · Audience, Data & Segmentation

Preference center taxonomy

Use this template to create a decision-ready brief for preference center taxonomy, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Preference center taxonomy.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a decision-ready brief specifically for “Preference center taxonomy” within the module “Audience, Data & Segmentation”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Map edge cases, exclusions, and what happens when required data is missing. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended preference center taxonomy deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-017 · Audience, Data & Segmentation

Engagement-based cohorts

Use this template to create an implementable outline for engagement-based cohorts, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Engagement-based cohorts.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an implementable outline specifically for “Engagement-based cohorts” within the module “Audience, Data & Segmentation”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Show two defensible options and the trade-offs between them. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended engagement-based cohorts deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-018 · Audience, Data & Segmentation

Inactive audience definition

Use this template to create a structured working document for inactive audience definition, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Inactive audience definition.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a structured working document specifically for “Inactive audience definition” within the module “Audience, Data & Segmentation”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Identify privacy, accessibility, and customer trust implications. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended inactive audience definition deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-019 · Audience, Data & Segmentation

B2B account segmentation

Use this template to create a reviewer-ready draft for b2b account segmentation, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: B2B account segmentation.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a reviewer-ready draft specifically for “B2B account segmentation” within the module “Audience, Data & Segmentation”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include measurable success criteria and a practical verification method. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended b2b account segmentation deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-020 · Audience, Data & Segmentation

Segment validation plan

Use this template to create an actionable plan for segment validation plan, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Segment validation plan.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an actionable plan specifically for “Segment validation plan” within the module “Audience, Data & Segmentation”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Finish with a handoff checklist and follow-up questions. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended segment validation plan deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-021 · Newsletter & Editorial Production

Newsletter content pillars

Use this template to create a decision-ready brief for newsletter content pillars, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Newsletter content pillars.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a decision-ready brief specifically for “Newsletter content pillars” within the module “Newsletter & Editorial Production”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Separate observed facts, assumptions, and questions requiring confirmation. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended newsletter content pillars deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-022 · Newsletter & Editorial Production

Monthly newsletter calendar

Use this template to create an implementable outline for monthly newsletter calendar, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Monthly newsletter calendar.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an implementable outline specifically for “Monthly newsletter calendar” within the module “Newsletter & Editorial Production”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include a compact input-to-output map and explain dependencies. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended monthly newsletter calendar deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-023 · Newsletter & Editorial Production

Issue angle generator

Use this template to create a structured working document for issue angle generator, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Issue angle generator.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a structured working document specifically for “Issue angle generator” within the module “Newsletter & Editorial Production”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Specify ownership, timeline, and a minimum viable first iteration. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended issue angle generator deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-024 · Newsletter & Editorial Production

Editorial briefing template

Use this template to create a reviewer-ready draft for editorial briefing template, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Editorial briefing template.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a reviewer-ready draft specifically for “Editorial briefing template” within the module “Newsletter & Editorial Production”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Use clear examples without making up customer facts or performance results. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended editorial briefing template deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-025 · Newsletter & Editorial Production

Newsletter subject line variants

Use this template to create an actionable plan for newsletter subject line variants, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Newsletter subject line variants.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an actionable plan specifically for “Newsletter subject line variants” within the module “Newsletter & Editorial Production”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include a pass/fail QA checklist and revision priorities. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended newsletter subject line variants deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-026 · Newsletter & Editorial Production

Newsletter opening hook

Use this template to create a decision-ready brief for newsletter opening hook, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Newsletter opening hook.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a decision-ready brief specifically for “Newsletter opening hook” within the module “Newsletter & Editorial Production”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Map edge cases, exclusions, and what happens when required data is missing. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended newsletter opening hook deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-027 · Newsletter & Editorial Production

Educational newsletter draft

Use this template to create an implementable outline for educational newsletter draft, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Educational newsletter draft.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an implementable outline specifically for “Educational newsletter draft” within the module “Newsletter & Editorial Production”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Show two defensible options and the trade-offs between them. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended educational newsletter draft deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-028 · Newsletter & Editorial Production

Curated digest blueprint

Use this template to create a structured working document for curated digest blueprint, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Curated digest blueprint.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a structured working document specifically for “Curated digest blueprint” within the module “Newsletter & Editorial Production”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Identify privacy, accessibility, and customer trust implications. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended curated digest blueprint deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-029 · Newsletter & Editorial Production

Newsletter accessibility review

Use this template to create a reviewer-ready draft for newsletter accessibility review, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Newsletter accessibility review.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a reviewer-ready draft specifically for “Newsletter accessibility review” within the module “Newsletter & Editorial Production”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include measurable success criteria and a practical verification method. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended newsletter accessibility review deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-030 · Newsletter & Editorial Production

Newsletter production checklist

Use this template to create an actionable plan for newsletter production checklist, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Newsletter production checklist.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an actionable plan specifically for “Newsletter production checklist” within the module “Newsletter & Editorial Production”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Finish with a handoff checklist and follow-up questions. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended newsletter production checklist deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-031 · Email Copy & Creative

Welcome email copy

Use this template to create a decision-ready brief for welcome email copy, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Welcome email copy.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a decision-ready brief specifically for “Welcome email copy” within the module “Email Copy & Creative”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Separate observed facts, assumptions, and questions requiring confirmation. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended welcome email copy deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-032 · Email Copy & Creative

Product launch email

Use this template to create an implementable outline for product launch email, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Product launch email.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an implementable outline specifically for “Product launch email” within the module “Email Copy & Creative”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include a compact input-to-output map and explain dependencies. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended product launch email deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-033 · Email Copy & Creative

Promotional email angle

Use this template to create a structured working document for promotional email angle, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Promotional email angle.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a structured working document specifically for “Promotional email angle” within the module “Email Copy & Creative”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Specify ownership, timeline, and a minimum viable first iteration. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended promotional email angle deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-034 · Email Copy & Creative

Plain-text founder email

Use this template to create a reviewer-ready draft for plain-text founder email, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Plain-text founder email.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a reviewer-ready draft specifically for “Plain-text founder email” within the module “Email Copy & Creative”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Use clear examples without making up customer facts or performance results. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended plain-text founder email deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-035 · Email Copy & Creative

Email CTA options

Use this template to create an actionable plan for email cta options, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Email CTA options.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an actionable plan specifically for “Email CTA options” within the module “Email Copy & Creative”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include a pass/fail QA checklist and revision priorities. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended email cta options deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-036 · Email Copy & Creative

Mobile-first layout brief

Use this template to create a decision-ready brief for mobile-first layout brief, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Mobile-first layout brief.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a decision-ready brief specifically for “Mobile-first layout brief” within the module “Email Copy & Creative”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Map edge cases, exclusions, and what happens when required data is missing. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended mobile-first layout brief deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-037 · Email Copy & Creative

Brand-aligned email design

Use this template to create an implementable outline for brand-aligned email design, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Brand-aligned email design.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an implementable outline specifically for “Brand-aligned email design” within the module “Email Copy & Creative”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Show two defensible options and the trade-offs between them. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended brand-aligned email design deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-038 · Email Copy & Creative

Personalization token fallback

Use this template to create a structured working document for personalization token fallback, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Personalization token fallback.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a structured working document specifically for “Personalization token fallback” within the module “Email Copy & Creative”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Identify privacy, accessibility, and customer trust implications. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended personalization token fallback deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-039 · Email Copy & Creative

Transactional message clarity

Use this template to create a reviewer-ready draft for transactional message clarity, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Transactional message clarity.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a reviewer-ready draft specifically for “Transactional message clarity” within the module “Email Copy & Creative”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include measurable success criteria and a practical verification method. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended transactional message clarity deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-040 · Email Copy & Creative

Copy quality review

Use this template to create an actionable plan for copy quality review, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Copy quality review.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an actionable plan specifically for “Copy quality review” within the module “Email Copy & Creative”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Finish with a handoff checklist and follow-up questions. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended copy quality review deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-041 · Lifecycle & Lead Nurturing

Welcome sequence architecture

Use this template to create a decision-ready brief for welcome sequence architecture, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Welcome sequence architecture.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a decision-ready brief specifically for “Welcome sequence architecture” within the module “Lifecycle & Lead Nurturing”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Separate observed facts, assumptions, and questions requiring confirmation. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended welcome sequence architecture deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-042 · Lifecycle & Lead Nurturing

Lead magnet delivery sequence

Use this template to create an implementable outline for lead magnet delivery sequence, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Lead magnet delivery sequence.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an implementable outline specifically for “Lead magnet delivery sequence” within the module “Lifecycle & Lead Nurturing”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include a compact input-to-output map and explain dependencies. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended lead magnet delivery sequence deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-043 · Lifecycle & Lead Nurturing

New lead education series

Use this template to create a structured working document for new lead education series, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: New lead education series.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a structured working document specifically for “New lead education series” within the module “Lifecycle & Lead Nurturing”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Specify ownership, timeline, and a minimum viable first iteration. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended new lead education series deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-044 · Lifecycle & Lead Nurturing

Trial activation sequence

Use this template to create a reviewer-ready draft for trial activation sequence, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Trial activation sequence.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a reviewer-ready draft specifically for “Trial activation sequence” within the module “Lifecycle & Lead Nurturing”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Use clear examples without making up customer facts or performance results. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended trial activation sequence deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-045 · Lifecycle & Lead Nurturing

Onboarding milestones

Use this template to create an actionable plan for onboarding milestones, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Onboarding milestones.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an actionable plan specifically for “Onboarding milestones” within the module “Lifecycle & Lead Nurturing”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include a pass/fail QA checklist and revision priorities. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended onboarding milestones deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-046 · Lifecycle & Lead Nurturing

Abandoned browse recovery

Use this template to create a decision-ready brief for abandoned browse recovery, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Abandoned browse recovery.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a decision-ready brief specifically for “Abandoned browse recovery” within the module “Lifecycle & Lead Nurturing”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Map edge cases, exclusions, and what happens when required data is missing. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended abandoned browse recovery deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-047 · Lifecycle & Lead Nurturing

Abandoned cart recovery

Use this template to create an implementable outline for abandoned cart recovery, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Abandoned cart recovery.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an implementable outline specifically for “Abandoned cart recovery” within the module “Lifecycle & Lead Nurturing”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Show two defensible options and the trade-offs between them. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended abandoned cart recovery deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-048 · Lifecycle & Lead Nurturing

Post-purchase nurture

Use this template to create a structured working document for post-purchase nurture, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Post-purchase nurture.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a structured working document specifically for “Post-purchase nurture” within the module “Lifecycle & Lead Nurturing”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Identify privacy, accessibility, and customer trust implications. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended post-purchase nurture deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-049 · Lifecycle & Lead Nurturing

Replenishment reminder

Use this template to create a reviewer-ready draft for replenishment reminder, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Replenishment reminder.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a reviewer-ready draft specifically for “Replenishment reminder” within the module “Lifecycle & Lead Nurturing”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include measurable success criteria and a practical verification method. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended replenishment reminder deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-050 · Lifecycle & Lead Nurturing

Win-back sequence

Use this template to create an actionable plan for win-back sequence, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Win-back sequence.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an actionable plan specifically for “Win-back sequence” within the module “Lifecycle & Lead Nurturing”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Finish with a handoff checklist and follow-up questions. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended win-back sequence deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-051 · CRM Platforms & Integrations

Mailchimp audience setup plan

Use this template to create a decision-ready brief for mailchimp audience setup plan, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Mailchimp audience setup plan.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a decision-ready brief specifically for “Mailchimp audience setup plan” within the module “CRM Platforms & Integrations”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Separate observed facts, assumptions, and questions requiring confirmation. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended mailchimp audience setup plan deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-052 · CRM Platforms & Integrations

Klaviyo event and property map

Use this template to create an implementable outline for klaviyo event and property map, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Klaviyo event and property map.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an implementable outline specifically for “Klaviyo event and property map” within the module “CRM Platforms & Integrations”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include a compact input-to-output map and explain dependencies. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended klaviyo event and property map deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-053 · CRM Platforms & Integrations

HubSpot workflow specification

Use this template to create a structured working document for hubspot workflow specification, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: HubSpot workflow specification.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a structured working document specifically for “HubSpot workflow specification” within the module “CRM Platforms & Integrations”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Specify ownership, timeline, and a minimum viable first iteration. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended hubspot workflow specification deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-054 · CRM Platforms & Integrations

CRM field mapping

Use this template to create a reviewer-ready draft for crm field mapping, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: CRM field mapping.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a reviewer-ready draft specifically for “CRM field mapping” within the module “CRM Platforms & Integrations”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Use clear examples without making up customer facts or performance results. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended crm field mapping deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-055 · CRM Platforms & Integrations

Form-to-CRM integration

Use this template to create an actionable plan for form-to-crm integration, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Form-to-CRM integration.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an actionable plan specifically for “Form-to-CRM integration” within the module “CRM Platforms & Integrations”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include a pass/fail QA checklist and revision priorities. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended form-to-crm integration deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-056 · CRM Platforms & Integrations

Shopify customer data sync

Use this template to create a decision-ready brief for shopify customer data sync, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Shopify customer data sync.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a decision-ready brief specifically for “Shopify customer data sync” within the module “CRM Platforms & Integrations”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Map edge cases, exclusions, and what happens when required data is missing. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended shopify customer data sync deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-057 · CRM Platforms & Integrations

WooCommerce lifecycle triggers

Use this template to create an implementable outline for woocommerce lifecycle triggers, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: WooCommerce lifecycle triggers.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an implementable outline specifically for “WooCommerce lifecycle triggers” within the module “CRM Platforms & Integrations”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Show two defensible options and the trade-offs between them. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended woocommerce lifecycle triggers deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-058 · CRM Platforms & Integrations

Webhook event contract

Use this template to create a structured working document for webhook event contract, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Webhook event contract.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a structured working document specifically for “Webhook event contract” within the module “CRM Platforms & Integrations”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Identify privacy, accessibility, and customer trust implications. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended webhook event contract deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-059 · CRM Platforms & Integrations

Duplicate contact prevention

Use this template to create a reviewer-ready draft for duplicate contact prevention, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Duplicate contact prevention.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a reviewer-ready draft specifically for “Duplicate contact prevention” within the module “CRM Platforms & Integrations”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include measurable success criteria and a practical verification method. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended duplicate contact prevention deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-060 · CRM Platforms & Integrations

Integration acceptance tests

Use this template to create an actionable plan for integration acceptance tests, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Integration acceptance tests.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an actionable plan specifically for “Integration acceptance tests” within the module “CRM Platforms & Integrations”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Finish with a handoff checklist and follow-up questions. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended integration acceptance tests deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-061 · Automation & Journey Orchestration

Trigger-action workflow specification

Use this template to create a decision-ready brief for trigger-action workflow specification, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Trigger-action workflow specification.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a decision-ready brief specifically for “Trigger-action workflow specification” within the module “Automation & Journey Orchestration”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Separate observed facts, assumptions, and questions requiring confirmation. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended trigger-action workflow specification deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-062 · Automation & Journey Orchestration

Branching logic and exit rules

Use this template to create an implementable outline for branching logic and exit rules, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Branching logic and exit rules.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an implementable outline specifically for “Branching logic and exit rules” within the module “Automation & Journey Orchestration”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include a compact input-to-output map and explain dependencies. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended branching logic and exit rules deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-063 · Automation & Journey Orchestration

Timing and frequency caps

Use this template to create a structured working document for timing and frequency caps, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Timing and frequency caps.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a structured working document specifically for “Timing and frequency caps” within the module “Automation & Journey Orchestration”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Specify ownership, timeline, and a minimum viable first iteration. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended timing and frequency caps deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-064 · Automation & Journey Orchestration

Suppression and exclusion logic

Use this template to create a reviewer-ready draft for suppression and exclusion logic, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Suppression and exclusion logic.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a reviewer-ready draft specifically for “Suppression and exclusion logic” within the module “Automation & Journey Orchestration”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Use clear examples without making up customer facts or performance results. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended suppression and exclusion logic deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-065 · Automation & Journey Orchestration

Human approval checkpoint

Use this template to create an actionable plan for human approval checkpoint, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Human approval checkpoint.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an actionable plan specifically for “Human approval checkpoint” within the module “Automation & Journey Orchestration”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include a pass/fail QA checklist and revision priorities. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended human approval checkpoint deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-066 · Automation & Journey Orchestration

Automation failure handling

Use this template to create a decision-ready brief for automation failure handling, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Automation failure handling.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a decision-ready brief specifically for “Automation failure handling” within the module “Automation & Journey Orchestration”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Map edge cases, exclusions, and what happens when required data is missing. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended automation failure handling deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-067 · Automation & Journey Orchestration

Re-entry and deduplication rules

Use this template to create an implementable outline for re-entry and deduplication rules, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Re-entry and deduplication rules.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an implementable outline specifically for “Re-entry and deduplication rules” within the module “Automation & Journey Orchestration”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Show two defensible options and the trade-offs between them. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended re-entry and deduplication rules deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-068 · Automation & Journey Orchestration

Cross-channel coordination

Use this template to create a structured working document for cross-channel coordination, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Cross-channel coordination.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a structured working document specifically for “Cross-channel coordination” within the module “Automation & Journey Orchestration”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Identify privacy, accessibility, and customer trust implications. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended cross-channel coordination deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-069 · Automation & Journey Orchestration

Automation documentation

Use this template to create a reviewer-ready draft for automation documentation, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Automation documentation.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a reviewer-ready draft specifically for “Automation documentation” within the module “Automation & Journey Orchestration”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include measurable success criteria and a practical verification method. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended automation documentation deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-070 · Automation & Journey Orchestration

Journey QA test scenarios

Use this template to create an actionable plan for journey qa test scenarios, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Journey QA test scenarios.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an actionable plan specifically for “Journey QA test scenarios” within the module “Automation & Journey Orchestration”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Finish with a handoff checklist and follow-up questions. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended journey qa test scenarios deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-071 · Deliverability & Compliance

Permission and consent audit

Use this template to create a decision-ready brief for permission and consent audit, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Permission and consent audit.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a decision-ready brief specifically for “Permission and consent audit” within the module “Deliverability & Compliance”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Separate observed facts, assumptions, and questions requiring confirmation. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended permission and consent audit deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-072 · Deliverability & Compliance

Sender authentication checklist

Use this template to create an implementable outline for sender authentication checklist, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Sender authentication checklist.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an implementable outline specifically for “Sender authentication checklist” within the module “Deliverability & Compliance”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include a compact input-to-output map and explain dependencies. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended sender authentication checklist deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-073 · Deliverability & Compliance

List hygiene framework

Use this template to create a structured working document for list hygiene framework, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: List hygiene framework.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a structured working document specifically for “List hygiene framework” within the module “Deliverability & Compliance”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Specify ownership, timeline, and a minimum viable first iteration. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended list hygiene framework deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-074 · Deliverability & Compliance

Bounce and complaint triage

Use this template to create a reviewer-ready draft for bounce and complaint triage, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Bounce and complaint triage.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a reviewer-ready draft specifically for “Bounce and complaint triage” within the module “Deliverability & Compliance”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Use clear examples without making up customer facts or performance results. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended bounce and complaint triage deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-075 · Deliverability & Compliance

Unsubscribe experience audit

Use this template to create an actionable plan for unsubscribe experience audit, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Unsubscribe experience audit.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an actionable plan specifically for “Unsubscribe experience audit” within the module “Deliverability & Compliance”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include a pass/fail QA checklist and revision priorities. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended unsubscribe experience audit deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-076 · Deliverability & Compliance

Spam-risk copy review

Use this template to create a decision-ready brief for spam-risk copy review, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Spam-risk copy review.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a decision-ready brief specifically for “Spam-risk copy review” within the module “Deliverability & Compliance”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Map edge cases, exclusions, and what happens when required data is missing. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended spam-risk copy review deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-077 · Deliverability & Compliance

Preference and consent records

Use this template to create an implementable outline for preference and consent records, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Preference and consent records.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an implementable outline specifically for “Preference and consent records” within the module “Deliverability & Compliance”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Show two defensible options and the trade-offs between them. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended preference and consent records deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-078 · Deliverability & Compliance

Regional compliance review brief

Use this template to create a structured working document for regional compliance review brief, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Regional compliance review brief.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a structured working document specifically for “Regional compliance review brief” within the module “Deliverability & Compliance”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Identify privacy, accessibility, and customer trust implications. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended regional compliance review brief deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-079 · Deliverability & Compliance

Deliverability incident runbook

Use this template to create a reviewer-ready draft for deliverability incident runbook, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Deliverability incident runbook.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a reviewer-ready draft specifically for “Deliverability incident runbook” within the module “Deliverability & Compliance”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include measurable success criteria and a practical verification method. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended deliverability incident runbook deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-080 · Deliverability & Compliance

Sending ramp-up plan

Use this template to create an actionable plan for sending ramp-up plan, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Sending ramp-up plan.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an actionable plan specifically for “Sending ramp-up plan” within the module “Deliverability & Compliance”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Finish with a handoff checklist and follow-up questions. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended sending ramp-up plan deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-081 · Experiments & Conversion Optimization

A/B test hypothesis

Use this template to create a decision-ready brief for a/b test hypothesis, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: A/B test hypothesis.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a decision-ready brief specifically for “A/B test hypothesis” within the module “Experiments & Conversion Optimization”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Separate observed facts, assumptions, and questions requiring confirmation. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended a/b test hypothesis deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-082 · Experiments & Conversion Optimization

Subject line experiment

Use this template to create an implementable outline for subject line experiment, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Subject line experiment.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an implementable outline specifically for “Subject line experiment” within the module “Experiments & Conversion Optimization”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include a compact input-to-output map and explain dependencies. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended subject line experiment deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-083 · Experiments & Conversion Optimization

Send-time experiment

Use this template to create a structured working document for send-time experiment, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Send-time experiment.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a structured working document specifically for “Send-time experiment” within the module “Experiments & Conversion Optimization”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Specify ownership, timeline, and a minimum viable first iteration. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended send-time experiment deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-084 · Experiments & Conversion Optimization

Email creative test

Use this template to create a reviewer-ready draft for email creative test, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Email creative test.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a reviewer-ready draft specifically for “Email creative test” within the module “Experiments & Conversion Optimization”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Use clear examples without making up customer facts or performance results. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended email creative test deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-085 · Experiments & Conversion Optimization

CTA experiment design

Use this template to create an actionable plan for cta experiment design, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: CTA experiment design.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an actionable plan specifically for “CTA experiment design” within the module “Experiments & Conversion Optimization”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include a pass/fail QA checklist and revision priorities. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended cta experiment design deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-086 · Experiments & Conversion Optimization

Holdout group planning

Use this template to create a decision-ready brief for holdout group planning, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Holdout group planning.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a decision-ready brief specifically for “Holdout group planning” within the module “Experiments & Conversion Optimization”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Map edge cases, exclusions, and what happens when required data is missing. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended holdout group planning deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-087 · Experiments & Conversion Optimization

Sample size assumptions

Use this template to create an implementable outline for sample size assumptions, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Sample size assumptions.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an implementable outline specifically for “Sample size assumptions” within the module “Experiments & Conversion Optimization”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Show two defensible options and the trade-offs between them. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended sample size assumptions deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-088 · Experiments & Conversion Optimization

Experiment result interpretation

Use this template to create a structured working document for experiment result interpretation, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Experiment result interpretation.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a structured working document specifically for “Experiment result interpretation” within the module “Experiments & Conversion Optimization”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Identify privacy, accessibility, and customer trust implications. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended experiment result interpretation deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-089 · Experiments & Conversion Optimization

Conversion funnel diagnosis

Use this template to create a reviewer-ready draft for conversion funnel diagnosis, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Conversion funnel diagnosis.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a reviewer-ready draft specifically for “Conversion funnel diagnosis” within the module “Experiments & Conversion Optimization”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include measurable success criteria and a practical verification method. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended conversion funnel diagnosis deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-090 · Experiments & Conversion Optimization

Testing roadmap prioritization

Use this template to create an actionable plan for testing roadmap prioritization, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Testing roadmap prioritization.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an actionable plan specifically for “Testing roadmap prioritization” within the module “Experiments & Conversion Optimization”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Finish with a handoff checklist and follow-up questions. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended testing roadmap prioritization deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-091 · Analytics & Attribution

Email KPI dictionary

Use this template to create a decision-ready brief for email kpi dictionary, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Email KPI dictionary.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a decision-ready brief specifically for “Email KPI dictionary” within the module “Analytics & Attribution”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Separate observed facts, assumptions, and questions requiring confirmation. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended email kpi dictionary deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-092 · Analytics & Attribution

Campaign performance report

Use this template to create an implementable outline for campaign performance report, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Campaign performance report.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an implementable outline specifically for “Campaign performance report” within the module “Analytics & Attribution”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include a compact input-to-output map and explain dependencies. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended campaign performance report deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-093 · Analytics & Attribution

Flow performance dashboard

Use this template to create a structured working document for flow performance dashboard, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Flow performance dashboard.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a structured working document specifically for “Flow performance dashboard” within the module “Analytics & Attribution”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Specify ownership, timeline, and a minimum viable first iteration. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended flow performance dashboard deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-094 · Analytics & Attribution

UTM naming convention

Use this template to create a reviewer-ready draft for utm naming convention, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: UTM naming convention.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a reviewer-ready draft specifically for “UTM naming convention” within the module “Analytics & Attribution”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Use clear examples without making up customer facts or performance results. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended utm naming convention deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-095 · Analytics & Attribution

Revenue attribution caveats

Use this template to create an actionable plan for revenue attribution caveats, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Revenue attribution caveats.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an actionable plan specifically for “Revenue attribution caveats” within the module “Analytics & Attribution”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include a pass/fail QA checklist and revision priorities. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended revenue attribution caveats deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-096 · Analytics & Attribution

Cohort retention analysis

Use this template to create a decision-ready brief for cohort retention analysis, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Cohort retention analysis.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a decision-ready brief specifically for “Cohort retention analysis” within the module “Analytics & Attribution”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Map edge cases, exclusions, and what happens when required data is missing. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended cohort retention analysis deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-097 · Analytics & Attribution

Engagement trend diagnosis

Use this template to create an implementable outline for engagement trend diagnosis, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Engagement trend diagnosis.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an implementable outline specifically for “Engagement trend diagnosis” within the module “Analytics & Attribution”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Show two defensible options and the trade-offs between them. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended engagement trend diagnosis deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-098 · Analytics & Attribution

List growth quality report

Use this template to create a structured working document for list growth quality report, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: List growth quality report.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a structured working document specifically for “List growth quality report” within the module “Analytics & Attribution”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Identify privacy, accessibility, and customer trust implications. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended list growth quality report deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-099 · Analytics & Attribution

Executive summary narrative

Use this template to create a reviewer-ready draft for executive summary narrative, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Executive summary narrative.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a reviewer-ready draft specifically for “Executive summary narrative” within the module “Analytics & Attribution”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include measurable success criteria and a practical verification method. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended executive summary narrative deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-100 · Analytics & Attribution

Measurement QA checklist

Use this template to create an actionable plan for measurement qa checklist, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Measurement QA checklist.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an actionable plan specifically for “Measurement QA checklist” within the module “Analytics & Attribution”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Finish with a handoff checklist and follow-up questions. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended measurement qa checklist deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-101 · Retention & CRM Operations

Customer health signals

Use this template to create a decision-ready brief for customer health signals, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Customer health signals.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a decision-ready brief specifically for “Customer health signals” within the module “Retention & CRM Operations”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Separate observed facts, assumptions, and questions requiring confirmation. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended customer health signals deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-102 · Retention & CRM Operations

Churn-risk intervention plan

Use this template to create an implementable outline for churn-risk intervention plan, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Churn-risk intervention plan.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an implementable outline specifically for “Churn-risk intervention plan” within the module “Retention & CRM Operations”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include a compact input-to-output map and explain dependencies. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended churn-risk intervention plan deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-103 · Retention & CRM Operations

Loyalty program messaging

Use this template to create a structured working document for loyalty program messaging, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Loyalty program messaging.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a structured working document specifically for “Loyalty program messaging” within the module “Retention & CRM Operations”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Specify ownership, timeline, and a minimum viable first iteration. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended loyalty program messaging deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-104 · Retention & CRM Operations

VIP customer journey

Use this template to create a reviewer-ready draft for vip customer journey, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: VIP customer journey.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a reviewer-ready draft specifically for “VIP customer journey” within the module “Retention & CRM Operations”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Use clear examples without making up customer facts or performance results. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended vip customer journey deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-105 · Retention & CRM Operations

Review request workflow

Use this template to create an actionable plan for review request workflow, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Review request workflow.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an actionable plan specifically for “Review request workflow” within the module “Retention & CRM Operations”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include a pass/fail QA checklist and revision priorities. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended review request workflow deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-106 · Retention & CRM Operations

Referral email strategy

Use this template to create a decision-ready brief for referral email strategy, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Referral email strategy.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a decision-ready brief specifically for “Referral email strategy” within the module “Retention & CRM Operations”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Map edge cases, exclusions, and what happens when required data is missing. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended referral email strategy deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-107 · Retention & CRM Operations

Reactivation offer evaluation

Use this template to create an implementable outline for reactivation offer evaluation, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Reactivation offer evaluation.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an implementable outline specifically for “Reactivation offer evaluation” within the module “Retention & CRM Operations”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Show two defensible options and the trade-offs between them. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended reactivation offer evaluation deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-108 · Retention & CRM Operations

Support-to-marketing handoff

Use this template to create a structured working document for support-to-marketing handoff, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Support-to-marketing handoff.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a structured working document specifically for “Support-to-marketing handoff” within the module “Retention & CRM Operations”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Identify privacy, accessibility, and customer trust implications. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended support-to-marketing handoff deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-109 · Retention & CRM Operations

CRM record hygiene SOP

Use this template to create a reviewer-ready draft for crm record hygiene sop, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: CRM record hygiene SOP.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a reviewer-ready draft specifically for “CRM record hygiene SOP” within the module “Retention & CRM Operations”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include measurable success criteria and a practical verification method. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended crm record hygiene sop deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-110 · Retention & CRM Operations

Quarterly retention review

Use this template to create an actionable plan for quarterly retention review, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Quarterly retention review.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an actionable plan specifically for “Quarterly retention review” within the module “Retention & CRM Operations”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Finish with a handoff checklist and follow-up questions. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended quarterly retention review deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-111 · Client Delivery & Remote Career

Email marketing service proposal

Use this template to create a decision-ready brief for email marketing service proposal, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Email marketing service proposal.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a decision-ready brief specifically for “Email marketing service proposal” within the module “Client Delivery & Remote Career”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Separate observed facts, assumptions, and questions requiring confirmation. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended email marketing service proposal deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-112 · Client Delivery & Remote Career

Discovery call agenda

Use this template to create an implementable outline for discovery call agenda, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Discovery call agenda.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an implementable outline specifically for “Discovery call agenda” within the module “Client Delivery & Remote Career”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include a compact input-to-output map and explain dependencies. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended discovery call agenda deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-113 · Client Delivery & Remote Career

Campaign creative brief

Use this template to create a structured working document for campaign creative brief, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Campaign creative brief.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a structured working document specifically for “Campaign creative brief” within the module “Client Delivery & Remote Career”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Specify ownership, timeline, and a minimum viable first iteration. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended campaign creative brief deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-114 · Client Delivery & Remote Career

CRM automation handoff

Use this template to create a reviewer-ready draft for crm automation handoff, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: CRM automation handoff.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a reviewer-ready draft specifically for “CRM automation handoff” within the module “Client Delivery & Remote Career”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Use clear examples without making up customer facts or performance results. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended crm automation handoff deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-115 · Client Delivery & Remote Career

Client reporting template

Use this template to create an actionable plan for client reporting template, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Client reporting template.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an actionable plan specifically for “Client reporting template” within the module “Client Delivery & Remote Career”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include a pass/fail QA checklist and revision priorities. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended client reporting template deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-116 · Client Delivery & Remote Career

Email audit portfolio case study

Use this template to create a decision-ready brief for email audit portfolio case study, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Email audit portfolio case study.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a decision-ready brief specifically for “Email audit portfolio case study” within the module “Client Delivery & Remote Career”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Map edge cases, exclusions, and what happens when required data is missing. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended email audit portfolio case study deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-117 · Client Delivery & Remote Career

Mock brand lifecycle project

Use this template to create an implementable outline for mock brand lifecycle project, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Mock brand lifecycle project.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an implementable outline specifically for “Mock brand lifecycle project” within the module “Client Delivery & Remote Career”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Show two defensible options and the trade-offs between them. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended mock brand lifecycle project deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-118 · Client Delivery & Remote Career

Remote role skills matrix

Use this template to create a structured working document for remote role skills matrix, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Remote role skills matrix.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a structured working document specifically for “Remote role skills matrix” within the module “Client Delivery & Remote Career”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Identify privacy, accessibility, and customer trust implications. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended remote role skills matrix deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-119 · Client Delivery & Remote Career

Interview case exercise

Use this template to create a reviewer-ready draft for interview case exercise, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: Interview case exercise.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce a reviewer-ready draft specifically for “Interview case exercise” within the module “Client Delivery & Remote Career”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Include measurable success criteria and a practical verification method. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended interview case exercise deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.
EMAIL-120 · Client Delivery & Remote Career

30-60-90 day onboarding plan

Use this template to create an actionable plan for 30-60-90 day onboarding plan, with implementation and validation steps.

Show full prompt and usage

Replace all bracketed fields with real, permissioned project information before using. Review the output and verify platform-specific instructions.

You are a senior email marketing and CRM automation specialist. Complete this assignment: 30-60-90 day onboarding plan.

PROJECT INPUTS
- Business and website: [BUSINESS / WEBSITE]
- Industry and audience: [INDUSTRY / IDEAL AUDIENCE]
- Offer, product or lifecycle stage: [OFFER / STAGE]
- CRM/email platform and integrations: [MAILCHIMP / KLAVIYO / HUBSPOT / OTHER]
- Available consented data and events: [DATA / EVENT DEFINITIONS]
- Brand voice and locale: [VOICE / LANGUAGE / REGION]
- Goal and baseline metrics: [GOAL / VERIFIED BASELINE]
- Constraints and deadline: [LIMITS / DATE]
- Supporting material: [PASTE BRIEF OR ANONYMIZED SAMPLE]

TASK
Produce an actionable plan specifically for “30-60-90 day onboarding plan” within the module “Client Delivery & Remote Career”. First identify any missing critical inputs; if an input is absent, mark it as an assumption rather than inventing data. Define the recommended approach, a concrete example or template, implementation steps, and the exact deliverables a client or teammate can use. Finish with a handoff checklist and follow-up questions. Where platform-specific settings, regulations, or API capabilities matter, label them for verification against current official documentation. Do not invent metrics, testimonials, consent, customer records, or legal assurances. Respect opt-outs and never suggest sending to non-consenting contacts.

OUTPUT FORMAT
1. Objective and input assumptions
2. Recommended 30-60-90 day onboarding plan deliverable
3. Copy-ready example / specifications
4. Implementation steps and responsible owner
5. QA, privacy and compliance checks
6. Metrics, validation and next action.

Practical portfolio project: lifecycle email system

Design a fictional DTC store’s consent-first email program: discovery brief, segmentation, welcome sequence, post-purchase journey, deliverability checklist, analytics specification and handoff document. Use IDs EMAIL-001, EMAIL-023, EMAIL-051, EMAIL-058, EMAIL-083, EMAIL-092 and EMAIL-114 as your starting path. Publish sample copy, a flowchart and a QA test matrix. Clearly mark any estimates as hypothetical.

Quality control before delivery

  • Verify opt-in status, suppression, consent records and unsubscribe handling.
  • Check every claim, price, link, personalization fallback and accessibility detail.
  • Confirm platform triggers, API properties, delays and error handling against live documentation.
  • Use actual measured data for reports; do not fabricate performance metrics.
  • Secure approval and test with internal contacts before launching.

Frequently asked questions

Are these actual WordPress shortcodes?

No. EMAIL-001 through EMAIL-120 are searchable prompt reference IDs, not executable WordPress shortcodes.

Can I paste customer lists into AI?

Use only authorized, minimized or anonymized data under your organization’s privacy and vendor policies. Never assume consent.

Do the prompts automatically run Mailchimp, Klaviyo or HubSpot?

No. They generate plans, drafts and specifications. Verify platform capabilities and obtain permission before performing account changes.

Can I use these for a portfolio?

Yes. Use fictional sample data, clearly label simulated results, and show your own implementation and testing.

Educational template library. Human verification is required for live marketing, legal compliance and integrations.