30 Claude Prompts for Klaviyo

You are a lifecycle marketer who builds recency, frequency, monetary segmentation for ecommerce email programs. <context> My customer list has grown past 20,000 profiles and I am still emailing everyone the same way. I need clear RFM segment definitions I can build directly as Klaviyo segments. </context> <inputs> - Average order value: [AVERAGE ORDER VALUE] - Typical repurchase cycle: [REPURCHASE CYCLE, e.g. 45 DAYS] - List size: [LIST SIZE] - Business model: [BUSINESS MODEL, e.g. CONSUMABLE OR ONE TIME PURCHASE] </inputs> <task> Define five RFM segments (such as champions, at risk, new customers, lapsing, and lost) with exact recency and order count thresholds based on the [REPURCHASE CYCLE] and [BUSINESS MODEL]. For each segment, state the Klaviyo filter logic in plain language. </task> <constraints> Thresholds must be grounded in the [REPURCHASE CYCLE], not generic 30/60/90 day defaults, unless the cycle happens to match. Keep each segment definition to two or three sentences. Avoid vague labels like "engaged" without a number attached. </constraints> <format> Return a table style list with segment name, Klaviyo filter logic, and one recommended action per segment. </format>

You are a deliverability focused email marketer who cleans lists to protect sender reputation. <context> My open rates have been sliding and I suspect a chunk of my Klaviyo list is dragging down deliverability. I need a sunset segment plan before I suppress anyone. </context> <inputs> - Current average open rate: [CURRENT OPEN RATE] - Sending frequency: [SENDING FREQUENCY] - Days of no engagement to flag: [DAYS NO ENGAGEMENT] - Sending domain type: [DOMAIN TYPE, e.g. SUBDOMAIN OR ROOT DOMAIN] </inputs> <task> Define a tiered sunset policy for subscribers with no opens or clicks in [DAYS NO ENGAGEMENT] days. Include a re-engagement segment that gets one last attempt before suppression, and a final suppression segment. Explain the Klaviyo filter logic for each tier. </task> <constraints> Do not recommend deleting subscribers outright, only suppressing from regular sends. Be specific about what "engagement" should include, such as opens, clicks, or site visits, given [SENDING FREQUENCY]. Avoid vague buzzwords and keep the explanation practical, not theoretical. </constraints> <format> Return three tiers labeled Re-engage, Final Attempt, and Suppress, each with Klaviyo filter logic and the reasoning behind the threshold. </format>

You are an ecommerce personalization specialist who builds product affinity segments for targeted campaigns. <context> I sell across multiple product categories and want to segment customers by what they actually buy so campaigns feel relevant instead of generic. </context> <inputs> - Product categories sold: [PRODUCT CATEGORIES, comma separated] - Cross-sell opportunity: [CROSS SELL OPPORTUNITY] - Purchase data available in Klaviyo: [DATA AVAILABLE, e.g. ORDER LINE ITEMS OR CATEGORY TAGS] </inputs> <task> Propose product affinity segments based on the [PRODUCT CATEGORIES], including a segment for customers who bought category A but never category B where a [CROSS SELL OPPORTUNITY] exists. State the Klaviyo filter logic using the [DATA AVAILABLE]. </task> <constraints> Only propose segments that are buildable with the [DATA AVAILABLE], do not assume data fields that were not listed. Limit to four segments so the list stays actionable. Avoid marketing jargon like "synergy" or "maximize impact". </constraints> <format> Return a numbered list of segments, each with the filter logic and a one sentence campaign idea that would use it. </format>

You are a growth marketer who uses Klaviyo's predictive analytics to align email and paid ad spend. <context> I want to use predicted customer lifetime value to stop wasting ad spend on low value customers and to prioritize my highest value ones for retention email. </context> <inputs> - Current average CLV: [AVERAGE CLV] - Ad platforms in use: [AD PLATFORMS] - Business goal for this quarter: [BUSINESS GOAL] - Klaviyo plan tier: [KLAVIYO PLAN TIER] </inputs> <task> Explain how to build a predicted CLV segment split into three bands relative to the [AVERAGE CLV], and describe how each band should be used differently, one for ad suppression lists fed to [AD PLATFORMS], one for a VIP retention flow, and one for standard treatment. Tie the recommendation back to the [BUSINESS GOAL]. </task> <constraints> Be upfront if predicted CLV requires a [KLAVIYO PLAN TIER] that may not be available on lower tiers, and offer a fallback using historical CLV instead. Keep the explanation under 250 words. Avoid overstating predictive accuracy. </constraints> <format> Return three sections, one per CLV band, each stating the segment logic and its recommended use. </format>

You are a Klaviyo flow architect who personalizes onboarding using signup form or quiz data. <context> My signup form or quiz collects a preference answer and I want to route new subscribers into different segments and flows based on their answer instead of one generic welcome series. </context> <inputs> - Quiz or form question asked: [QUESTION ASKED] - Possible answers: [POSSIBLE ANSWERS, comma separated] - Product tied to each answer: [PRODUCT MAPPING] - Number of segments wanted: [NUMBER OF SEGMENTS] </inputs> <task> Define [NUMBER OF SEGMENTS] segments based on the [POSSIBLE ANSWERS] to "[QUESTION ASKED]", each mapped to the relevant [PRODUCT MAPPING], and describe the Klaviyo filter logic using the custom property created by the form. </task> <constraints> Assume the answer is stored as a Klaviyo profile property, not an event, unless told otherwise. Keep segment names short enough to recognize at a glance in the Klaviyo segment list. Avoid overlapping logic between segments. </constraints> <format> Return a list of segments with name, filter logic, and the flow or campaign each segment should feed into. </format>

You are an ecommerce copywriter who writes product launch campaigns for direct to consumer brands. <context> I am launching a new product and want a three email campaign arc that builds anticipation, announces the launch, and follows up with holdouts. </context> <inputs> - Product name: [PRODUCT NAME] - Key benefit: [KEY BENEFIT] - Launch date: [LAUNCH DATE] - Price: [PRICE] - Launch incentive if any: [LAUNCH INCENTIVE] </inputs> <task> Write three campaign emails: a teaser sent before [LAUNCH DATE] that does not reveal the product, a launch day announcement email centered on [KEY BENEFIT] and [PRICE], and a follow up email for people who opened but did not click, using [LAUNCH INCENTIVE] if provided. </task> <constraints> The teaser must not name the product. Each email needs one clear call to action, not multiple competing links. Keep launch day copy focused on [KEY BENEFIT] rather than a feature list. Avoid the word "revolutionary" or similar hype. </constraints> <format> Return three labeled emails, each with subject line, preview text, and body copy. </format>

You are a promotions copywriter for an ecommerce brand who avoids manufactured urgency. <context> I am running a time limited sale and want campaign copy that creates real urgency without the fake countdown gimmicks that make customers distrust the brand. </context> <inputs> - Discount amount: [DISCOUNT AMOUNT] - Sale end date and time: [SALE END DATE] - Products included: [PRODUCTS INCLUDED] - Reason for the sale: [SALE REASON, e.g. END OF SEASON OR ANNIVERSARY] </inputs> <task> Write a two email sale campaign, one announcing the sale with the [SALE REASON] stated honestly, and one final reminder sent close to [SALE END DATE]. Cover [PRODUCTS INCLUDED] and the [DISCOUNT AMOUNT]. </task> <constraints> The urgency must be real, tied to the actual [SALE END DATE], not implied to be shorter than it is. Do not use all caps in subject lines. Keep both emails focused on value, not just the discount number. </constraints> <format> Return two emails with subject line, preview text, and body copy, plus a note on ideal send time for the reminder relative to [SALE END DATE]. </format>

You are a content driven email marketer who builds trust with educational campaigns before making a sales ask. <context> My audience needs to understand a concept before they will buy my product, and I want an email that teaches first and pitches second without feeling like a bait and switch. </context> <inputs> - Concept to explain: [CONCEPT] - Product that solves it: [PRODUCT] - Audience sophistication level: [AUDIENCE LEVEL, e.g. BEGINNER OR EXPERIENCED] - Common misconception: [COMMON MISCONCEPTION] </inputs> <task> Write a single educational campaign email that explains [CONCEPT] for a [AUDIENCE LEVEL] reader, corrects the [COMMON MISCONCEPTION], and then introduces [PRODUCT] as one way to apply what they just learned. </task> <constraints> The educational portion must be genuinely useful even if the reader never buys anything. The product mention should take up no more than the final quarter of the email. Avoid sounding like a listicle, write it as a real explanation. </constraints> <format> Return subject line, preview text, and full body copy in flowing paragraphs, not bullet points. </format>

You are a social proof focused ecommerce copywriter who turns customer reviews into campaign emails. <context> I have strong customer reviews and photos sitting unused and want a campaign email built around real customer voices instead of brand copy. </context> <inputs> - Product being featured: [PRODUCT] - Best review quote available: [REVIEW QUOTE] - Customer detail worth mentioning: [CUSTOMER DETAIL, e.g. USE CASE OR LOCATION] - Call to action: [CALL TO ACTION] </inputs> <task> Write a campaign email centered on the [REVIEW QUOTE] from a customer, adding the [CUSTOMER DETAIL] for context, that leads naturally into the [CALL TO ACTION] for [PRODUCT]. </task> <constraints> Keep the brand's own voice secondary to the customer's words, do not paraphrase the [REVIEW QUOTE] into marketing language. One call to action only. Avoid stacking multiple reviews into one email, this prompt is for a single strong quote. </constraints> <format> Return subject line, preview text, and body copy that visually sets the review quote apart from the surrounding copy using a simple format like quotation marks or a dash-free line break. </format>

You are an ecommerce email marketer who writes restock announcement campaigns for products with a history of selling out. <context> A popular product just came back in stock after selling out, and I want a campaign that reaches the people who wanted it most without spamming the full list. </context> <inputs> - Product restocked: [PRODUCT] - How long it was out of stock: [TIME OUT OF STOCK] - Quantity available this time: [QUANTITY AVAILABLE] - Segment to target: [SEGMENT, e.g. BACK IN STOCK SIGNUPS] </inputs> <task> Write a restock announcement email for the [SEGMENT] that acknowledges the [TIME OUT OF STOCK] wait and sets honest expectations about [QUANTITY AVAILABLE] if supply is limited. </task> <constraints> Only mention limited quantity if [QUANTITY AVAILABLE] is genuinely limited, do not fabricate scarcity. Keep the email short, this is a transactional-feeling announcement, not a full campaign story. Avoid exclamation points stacked in the subject line. </constraints> <format> Return subject line, preview text, and body copy, plus a one sentence recommendation on send timing relative to the restock. </format>

You are an email copywriter who specializes in subject line testing for ecommerce campaigns. <context> I have a campaign written and need a wide set of subject line options to test in Klaviyo before choosing a winner. </context> <inputs> - Campaign topic: [CAMPAIGN TOPIC] - Key benefit or hook: [KEY HOOK] - Brand tone: [BRAND TONE] - Character limit target: [CHARACTER LIMIT, e.g. 40] </inputs> <task> Write ten subject line variants for the [CAMPAIGN TOPIC], covering at least four different angles such as curiosity, direct benefit, urgency, and a question format, all built around the [KEY HOOK]. </task> <constraints> Stay within the [CHARACTER LIMIT]. Match the [BRAND TONE]. No clickbait that misrepresents the email content. Do not repeat the same opening word across more than two variants. </constraints> <format> Return a numbered list of ten subject lines, each labeled with its angle in parentheses. </format>

You are an email marketer who treats preview text as a second sentence, not a subject line repeat. <context> Most of my preview text just restates the subject line or shows the plain unsubscribe footer text, and I want preview text that actually adds a reason to open. </context> <inputs> - Chosen subject line: [SUBJECT LINE] - Email's main offer or content: [MAIN CONTENT] - Character limit target: [CHARACTER LIMIT, e.g. 90] </inputs> <task> Write five preview text options that pair with the [SUBJECT LINE] without repeating its words, each adding a new piece of information about the [MAIN CONTENT] that makes the open feel worthwhile. </task> <constraints> Stay within [CHARACTER LIMIT]. Do not restate any word already in [SUBJECT LINE]. Avoid generic filler like "click to learn more". </constraints> <format> Return a numbered list of five preview text options, each on its own line. </format>

You are a deliverability aware copywriter who writes subject lines specifically for a disengaged audience. <context> I have a segment with historically low open rates and want subject lines designed to re-earn attention rather than the same style I use for engaged subscribers. </context> <inputs> - Segment description: [SEGMENT DESCRIPTION] - Historical open rate: [HISTORICAL OPEN RATE] - Content of the email: [EMAIL CONTENT] - What might have caused disengagement: [DISENGAGEMENT CAUSE, if known] </inputs> <task> Write five subject lines aimed at the [SEGMENT DESCRIPTION] with a [HISTORICAL OPEN RATE], designed to feel different from routine promotional sends, referencing [EMAIL CONTENT] in a way that acknowledges they have not engaged in a while without sounding needy. </task> <constraints> Do not use spam-trigger words like "free", "urgent", or excessive punctuation, this segment needs deliverability caution as much as copy improvement. Avoid guilt language. Keep each subject line under 50 characters. </constraints> <format> Return a numbered list of five subject lines with a one line rationale for each. </format>

You are an email deliverability specialist who rewrites subject lines that trigger spam filters. <context> One of my past subject lines seems to have landed in spam more than usual and I want a rewritten version that keeps the same intent without the flagged language. </context> <inputs> - Original subject line: [ORIGINAL SUBJECT LINE] - Suspected trigger words: [SUSPECTED TRIGGER WORDS] - Core message to preserve: [CORE MESSAGE] </inputs> <task> Rewrite the [ORIGINAL SUBJECT LINE] into three alternatives that preserve the [CORE MESSAGE] while removing or replacing the [SUSPECTED TRIGGER WORDS] and any other likely spam triggers you notice. </task> <constraints> No excessive punctuation such as multiple exclamation points or question marks. No all caps words. Avoid dollar signs or percent symbols directly next to numbers if that was part of the original issue. </constraints> <format> Return the three rewritten subject lines, each followed by a short note on what was changed and why. </format>

You are a seasonal campaign copywriter who avoids the same recycled holiday subject line tropes every brand uses. <context> I am planning a seasonal campaign and want subject lines that reference the season without falling back on the most overused phrases everyone's inbox is already full of. </context> <inputs> - Holiday or season: [HOLIDAY OR SEASON] - Product or offer tied to it: [PRODUCT OR OFFER] - Brand tone: [BRAND TONE] - Phrases to avoid: [PHRASES TO AVOID, e.g. LAST CHANCE OR DEALS] </inputs> <task> Write six subject lines for a [HOLIDAY OR SEASON] campaign promoting [PRODUCT OR OFFER], written in a [BRAND TONE] voice, that deliberately avoid the [PHRASES TO AVOID] and typical holiday cliches. </task> <constraints> Do not use the literal holiday name in every single subject line, vary the angle. Keep each under 50 characters. No emoji unless [BRAND TONE] explicitly calls for a playful style. </constraints> <format> Return a numbered list of six subject lines. </format>

You are an email deliverability consultant who diagnoses sudden drops in inbox placement for Klaviyo senders. <context> My open rates dropped noticeably in a short window and I need a structured way to figure out whether it is a deliverability problem or something else before I panic and change everything. </context> <inputs> - Open rate before the drop: [OPEN RATE BEFORE] - Open rate after the drop: [OPEN RATE AFTER] - Recent changes made: [RECENT CHANGES, e.g. NEW DOMAIN OR SENDING FREQUENCY CHANGE] - Sending volume per week: [SENDING VOLUME] </inputs> <task> Build a diagnostic checklist to work through, moving from most likely to least likely cause, given the drop from [OPEN RATE BEFORE] to [OPEN RATE AFTER] and the [RECENT CHANGES]. Cover authentication, list hygiene, content triggers, and sending pattern changes relative to [SENDING VOLUME]. </task> <constraints> Order the checklist by likelihood, not alphabetically. Be specific about what to check in Klaviyo versus what requires checking the domain's DNS records. Do not recommend starting from scratch on the whole email program, this needs a targeted diagnosis. </constraints> <format> Return a numbered checklist, each item with what to check and what result would confirm that item as the cause. </format>

You are a deliverability specialist who plans domain warm-up schedules for ecommerce senders migrating to Klaviyo. <context> I am setting up a new sending domain in Klaviyo and need a warm-up plan so I do not damage my sender reputation by blasting my full list on day one. </context> <inputs> - Total list size: [TOTAL LIST SIZE] - Most engaged segment size: [ENGAGED SEGMENT SIZE] - Target full send volume: [TARGET VOLUME] - Timeline available: [TIMELINE, e.g. 4 WEEKS] </inputs> <task> Build a week by week warm-up schedule across the [TIMELINE] that starts by sending only to the [ENGAGED SEGMENT SIZE] and gradually expands to the [TOTAL LIST SIZE], reaching the [TARGET VOLUME] by the end. </task> <constraints> Do not jump more than roughly double the previous week's volume at any step. Specify which segment to send to each week, not just a raw number. Note where to pause and reassess if open rates drop during the ramp. </constraints> <format> Return a week by week table with week number, segment to send to, approximate volume, and what to monitor that week. </format>

You are an email compliance and deliverability advisor who cleans up risky email lists before they damage a sending domain. <context> I merged in an old list or acquired contacts from another source and I am worried about sending to addresses that could hurt my deliverability or violate consent rules. </context> <inputs> - Source of the list: [LIST SOURCE, e.g. OLD SHOPIFY EXPORT OR ACQUIRED COMPANY] - Age of the list: [LIST AGE] - Consent status known: [CONSENT STATUS, e.g. UNKNOWN OR OPT-IN CONFIRMED] - Size of the list: [LIST SIZE] </inputs> <task> Create a list hygiene plan for the [LIST SIZE] contacts from [LIST SOURCE], given they are [LIST AGE] old with [CONSENT STATUS] consent, before allowing them into regular Klaviyo sends. Include validation, a re-permission approach if consent is unclear, and a suppression rule for anyone who does not respond. </task> <constraints> If [CONSENT STATUS] is unknown or unclear, treat re-permission as mandatory, not optional, do not recommend directly sending promotional email to unconfirmed contacts. Be specific about what counts as a valid response to a re-permission email. </constraints> <format> Return a step by step plan with each step numbered, including what to do with contacts who do not respond. </format>

You are an email marketing strategist who balances sending frequency against unsubscribe and complaint rates. <context> My unsubscribe rate has been creeping up and I suspect I am emailing too often, but I do not want to under-communicate and lose revenue either. </context> <inputs> - Current sends per week: [SENDS PER WEEK] - Current unsubscribe rate: [UNSUBSCRIBE RATE] - Revenue per email currently: [REVENUE PER EMAIL] - Business type: [BUSINESS TYPE, e.g. FLASH SALE RETAILER OR SLOW REPLENISHMENT] </inputs> <task> Recommend a revised sending frequency given [SENDS PER WEEK] current volume, [UNSUBSCRIBE RATE], and [REVENUE PER EMAIL], tailored to a [BUSINESS TYPE]. Include a plan for testing the new frequency against the old one without losing the ability to compare results. </task> <constraints> Do not simply recommend cutting frequency in half without reasoning, tie the recommendation to the specific numbers given. Include how to structure the test so it isolates frequency as the variable. Avoid vague advice like "send less, but not too much less". </constraints> <format> Return a recommended frequency, the reasoning in two or three sentences, and a simple test structure with a duration and what to measure. </format>

You are a lifecycle marketer who writes the final re-engagement email a subscriber sees before being moved to a suppressed or sunset segment. <context> A group of subscribers is about to be moved out of regular sends due to inactivity, and I want one honest last email that gives them a real choice instead of quietly dropping them. </context> <inputs> - Days of inactivity: [DAYS INACTIVE] - What they will miss if suppressed: [WHAT THEY WILL MISS] - Reason they might have gone quiet: [POSSIBLE REASON] </inputs> <task> Write a single sunset email for subscribers inactive for [DAYS INACTIVE] days that names the situation plainly, offers a simple way to stay subscribed, and briefly mentions [WHAT THEY WILL MISS] if they do nothing, while acknowledging [POSSIBLE REASON] as a fair explanation for their silence. </task> <constraints> Do not use guilt or pressure tactics. Make the action to stay subscribed genuinely one click. Keep the email under 100 words. Avoid framing suppression as a punishment. </constraints> <format> Return subject line, preview text, and body copy, plus a one sentence note on what to do with subscribers who take no action within a stated window. </format>

You are a conversion focused email marketer who designs A/B tests inside Klaviyo flows. <context> I want to test a change to one email in an existing flow but I am not sure how to structure the test so the result is actually trustworthy. </context> <inputs> - Flow being tested: [FLOW NAME] - Email position in flow: [EMAIL POSITION, e.g. SECOND EMAIL] - Element to test: [ELEMENT TO TEST, e.g. SUBJECT LINE OR CTA BUTTON] - Monthly volume through this flow: [MONTHLY VOLUME] </inputs> <task> Design an A/B test for the [ELEMENT TO TEST] on the [EMAIL POSITION] of the [FLOW NAME], including the two variants to test, the primary metric to judge the winner, and a rough estimate of how many days it will take to reach a usable sample size given [MONTHLY VOLUME]. </task> <constraints> Pick one primary metric only, not multiple competing ones. Be honest if [MONTHLY VOLUME] is too low to reach significance quickly, and suggest an alternative test approach if so. Avoid recommending a test duration shorter than one full week. </constraints> <format> Return variant A, variant B, primary metric, estimated test duration, and a one sentence caveat about sample size. </format>

You are an email marketing manager who reports Klaviyo performance to a non technical stakeholder each month. <context> I need to summarize this month's email performance for a founder or manager who does not look at Klaviyo dashboards directly and wants the headline story, not raw numbers. </context> <inputs> - This month's revenue from email: [MONTH REVENUE] - Last month's revenue from email: [LAST MONTH REVENUE] - Notable campaign or flow change this month: [NOTABLE CHANGE] - Overall open and click rate trend: [OPEN CLICK TREND] </inputs> <task> Write a short monthly summary comparing [MONTH REVENUE] to [LAST MONTH REVENUE], explaining the [OPEN CLICK TREND], and connecting the result to the [NOTABLE CHANGE] where relevant. End with one recommendation for next month. </task> <constraints> Keep it under 200 words. No raw data dumps or tables, this is meant to be read in under a minute. State the revenue change as a plain percentage, not just raw numbers. Avoid hedging every sentence with qualifiers. </constraints> <format> Return three short paragraphs: what happened, why it likely happened, and what to do next month. </format>

You are an email conversion specialist who diagnoses the gap between opens and clicks in Klaviyo flows. <context> One of my flows gets strong open rates but people are not clicking through, and I want to understand what in the email itself might be causing that gap. </context> <inputs> - Flow name: [FLOW NAME] - Open rate: [OPEN RATE] - Click rate: [CLICK RATE] - Call to action used: [CURRENT CTA] - Email length: [EMAIL LENGTH, e.g. SHORT OR LONG WITH MULTIPLE SECTIONS] </inputs> <task> Analyze the likely reasons the [FLOW NAME] has an [OPEN RATE] of that level but only a [CLICK RATE], given the [CURRENT CTA] and [EMAIL LENGTH]. Suggest three specific changes to test, ranked by how likely each is to move the click rate. </task> <constraints> Do not suggest changing the subject line, that only affects opens, stay focused on click through factors like CTA clarity, placement, and content relevance. Rank the three suggestions, do not present them as equally likely to help. </constraints> <format> Return a short diagnosis paragraph followed by three ranked suggestions, each with the reasoning behind its rank. </format>

You are an email operations manager who plans weekly send calendars to avoid over-messaging customers across flows and campaigns. <context> I run several always-on flows plus weekly campaigns and worry that some customers are getting hit with too many emails in the same day when a flow and a campaign overlap. </context> <inputs> - Active flows and their typical daily volume: [ACTIVE FLOWS] - Planned campaigns this week: [PLANNED CAMPAIGNS] - Maximum emails per customer per day target: [MAX PER DAY] - Days campaigns are typically sent: [CAMPAIGN SEND DAYS] </inputs> <task> Build a weekly send calendar that schedules the [PLANNED CAMPAIGNS] on the [CAMPAIGN SEND DAYS] while accounting for overlap with the [ACTIVE FLOWS], staying under the [MAX PER DAY] target for any single customer where flows and campaigns might collide. </task> <constraints> Flag any day where a customer could realistically receive more emails than [MAX PER DAY] due to overlap. Suggest a smart sending or frequency capping approach in Klaviyo if the overlap cannot be avoided through scheduling alone. Keep the calendar to one week only. </constraints> <format> Return a day by day table for the week, listing scheduled campaigns, active flows likely to trigger, and any overlap warning. </format>

You are an email marketing lead who runs a short debrief after every major campaign before planning the next one. <context> I just sent a campaign and want a structured debrief so I actually learn something from the result instead of just glancing at the open rate and moving on. </context> <inputs> - Campaign name and goal: [CAMPAIGN NAME AND GOAL] - Result versus goal: [RESULT VS GOAL] - Segment sent to: [SEGMENT SENT TO] - Anything unusual noticed: [ANYTHING UNUSUAL] </inputs> <task> Write a debrief question set to work through for the [CAMPAIGN NAME AND GOAL], given the [RESULT VS GOAL] and the [SEGMENT SENT TO], that surfaces what to repeat, what to change, and what to test next, taking [ANYTHING UNUSUAL] into account. </task> <constraints> Ask questions, do not just state conclusions, this is meant to prompt genuine reflection, not hand over an assumed answer. Keep it to eight questions or fewer so the debrief stays quick to run after every send. Group the questions into what worked, what did not, and what to test next. </constraints> <format> Return three short groups of questions labeled What Worked, What Did Not, and What To Test Next. </format>