Updated: Nov 8
15 Klaviyo Composer Prompts for Better Campaigns, Flows and Retention Decisions
By Trayan Hristov · Thrivelia · Reviewed 29 October 2026
The best Klaviyo Composer prompts give it a specific job, the evidence to use and a clear stopping point. Start with one account question, inspect the answer, then ask for a draft or a proposed change. That makes it easier to spot an unsupported recommendation before it becomes a customer-facing message.
Composer is Klaviyo’s AI marketing agent. Its documented capabilities include account analysis, audits, campaigns, flows and segments. This guide contains Thrivelia’s recommended starting prompts, based on that documentation. They are examples to adapt, rather than results from a controlled performance test.
Set up the conversation before asking for more output
If Composer is available in your account, open it using Klaviyo’s sparkle icon. For a review of a particular campaign, flow or email, open that asset first and identify it by name in your prompt. Confirm that Composer is discussing the intended asset.
Klaviyo’s prompting guidance recommends conversational requests with a goal, relevant context and constraints. Keep useful follow-ups in the same conversation. Tell it exactly what needs changing when an answer misses the brief.
Replace every bracketed field below. Supply approved product facts, offers, URLs and dates; do not ask Composer to guess them. The time windows and message counts in these examples are starting choices for your team to review.
A reusable brief looks like this:
We sell [PRODUCT CATEGORY] to [CUSTOMER]. Help with [ONE TASK] for [ASSET OR AUDIENCE], using [DATE RANGE AND CHANNEL]. Our goal is [OUTCOME]. Use these approved facts: [FACTS, OFFER AND LINKS]. Return [FORMAT AND LENGTH]. Separate observations from hypotheses, identify missing information, and ask before saving changes or creating additional assets.
Diagnose the account before building more messages
1. Find three opportunities worth investigating
Use when: the team has plenty of ideas but no agreed priority.
Review email campaigns and flows for [START DATE–END DATE]. Identify up to three opportunities relevant to [FIRST PURCHASE / SECOND PURCHASE / CUSTOMER REACTIVATION]. For each, show the affected asset or audience, the account evidence and metric definition, what remains uncertain, and the next check needed. Distinguish observed problems from test ideas. Do not estimate a revenue uplift or make changes.
Review next: whether the finding identifies an actual customer problem. A low-volume flow can have volatile rates; a large revenue total can simply reflect a large audience. Use our Klaviyo audit checklist to investigate the priorities.
2. Investigate a welcome-flow drop-off
Review [WELCOME FLOW NAME] for [DATES]. Our concern is [OBSERVED SYMPTOM]. Check the trigger, entry and continuing eligibility, delays, message status and purchase exclusions. Identify which settings you can verify and which need a manual check. Show any available delivery, click and order evidence by message. Return the top three checks in order, with reasons. Do not rewrite the flow yet.
Review next: whether profiles entered and qualified before blaming the copy. Trace a controlled example through the flow. Our welcome-flow diagnostic explains that investigation.
3. Examine the path from first to second purchase
Help investigate second purchases among customers whose first order was in [COHORT DATES]. Use a [NUMBER]-day observation window and only include customers with that full follow-up period. State the order metric, customer definition and exclusions available in this account. If you cannot calculate the cohort accurately, list the missing inputs. Suggest three questions our post-purchase journey should answer. Do not treat attributed email revenue as proof of incremental sales.
Review next: the cohort calculation and product buying cycle. A recent buyer has had less time to return. These post-purchase strategy principles help turn a finding into a useful message.
Build the structure, audience and brief
4. Design a post-purchase flow before writing it
Propose the structure of a post-purchase flow for [PRODUCT CATEGORY], using our verified [ORDER METRIC]. Start with [NUMBER] emails. Explain the trigger, filters, delays, purchase exclusions, purpose of each message and overlap checks against [EXISTING FLOWS]. Use [APPROVED PRODUCT-USAGE GUIDANCE]. Return the structure and unresolved questions first. Wait for my approval before generating message content or saving a flow.
Klaviyo supports requesting a flow structure before its messages. Review the preview, then the editable draft. Creating the draft leaves its messages in draft; the team still needs to inspect the settings and content before activation.
5. Define a segment with explicit conditions
Propose a new email segment named [NAME]. Include profiles with email marketing consent who are eligible to receive email marketing, who placed exactly one order over all time, with that order in the last [NUMBER] days, and who clicked an email in the last [NUMBER] days. Exclude [EXISTING EXCLUSION SEGMENTS]. Use only available properties and metrics. Show the complete grouped conditions and count if available. Flag missing data and wait for review before saving.
Review next: every AND/OR group, consent rule, date window and exclusion. A plausible count does not prove the logic is right. Composer uses existing account data; it cannot invent an absent property. Klaviyo’s segment-creation guide explains the preview and save process.
6. Brief a campaign without defaulting to a discount
Draft one email campaign for [APPROVED AUDIENCE] about [PRODUCT OR CUSTOMER PROBLEM]. The objective is [OUTCOME]. Use only these facts and approved proof points: [DETAILS]. There is no discount. Use a [TONE] voice, one primary CTA to [URL], and no invented testimonials, scarcity or claims. Suggest a subject line, preview text and an editable email layout. Ask about any missing product facts first.
Review next: whether the email gives this audience a reason to act. “No discount” still needs a useful proposition: a product application, an answered objection or a relevant occasion. Composer can draft a campaign, but creating a campaign draft does not schedule or send it.
7. Coordinate an email and SMS campaign
Propose one email and one supporting SMS for [CAMPAIGN]. Use the approved offer [EXACT TERMS], valid [DATES AND TIME ZONE], linking to [URL]. Email audience: [SEGMENT]. SMS audience: [SMS-ELIGIBLE SEGMENT]. Give each channel a distinct job and propose timing without scheduling it. Identify overlap and recent-purchaser exclusions to review. Draft the email first, then SMS copy for review, showing any length or required-content concerns.
Review next: channel eligibility, offer parity and contact pressure. SMS must be configured in the account, including a sending number. Do not assume an email audience is also eligible for SMS, or that a copy review confirms every send requirement.
Improve creative with a specific revision brief
8. Match an approved brand example
Revise [DRAFT NAME] using this approved writing sample as the style reference: [SAMPLE]. Keep the offer, product facts and destination links unchanged. Use [TONE], avoid [BANNED PHRASES], and keep the body under [WORD LIMIT]. Explain three concrete changes to voice. Do not add claims that are absent from the approved facts. Show the revised version for review.
Review next: whether the writing sounds appropriate for the customer situation. A playful launch reference may be unsuitable for a delayed-order message. Choose the example deliberately.
9. Generate subject lines with different hypotheses
For [CAMPAIGN DRAFT], propose three subject-line and preview-text pairs. Give each a different hypothesis: [PRODUCT BENEFIT], [CUSTOMER QUESTION] and [APPROVED PROOF POINT]. Preserve the actual offer and avoid false urgency or unsupported personalization. Explain the difference between the hypotheses. Propose a test plan with a primary metric and guardrails; do not predict a winner or configure the test.
Review next: whether the versions test a meaningful difference. Small wording changes can be useful, but they will not answer whether customers respond better to a benefit or a specific objection. Choose a success metric aligned with the campaign’s objective.
When you want the test built: follow the idea-generation request with an explicit instruction to create a new email or SMS campaign content A/B test. Klaviyo’s Composer campaign guide distinguishes alternatives from a configured test. Creating the draft does not send or schedule it.
For example: “Create a new email campaign content A/B test using our approved subject lines A and B. Keep the body, offer, audience and links unchanged. Show both variations and the saved test settings for review. Do not send or schedule the campaign.” This is a follow-up to prompt 9, not a prediction of a winner.
10. Shorten an email without losing its meaning
Shorten [EMAIL DRAFT] to approximately [WORD LIMIT] body words. Preserve the product names, prices, discount conditions, deadline, essential qualifications and all destination URLs. Keep one primary CTA. Flag any information that cannot fit rather than silently removing it. Show the proposed revision and list what you cut. Do not save it yet.
Review next: the original and revision side by side. Check that a shorter headline has not changed the promise. For layouts built mainly from flattened images, expect additional manual editing and inspect the actual rendered email.
Review, learn and make the process repeatable
11. Run a focused pre-send review
Review the currently open campaign [NAME]. Check the offer against [APPROVED TERMS], CTA destinations, placeholder text, personalization fallbacks, audience and exclusions, and visible accessibility issues. Return blockers first and optional improvements second. For every finding, state the evidence and whether you verified it or it needs a manual test. Do not change or schedule anything.
Review next: click the links, preview representative profiles and send test messages to inspect rendering. Confirm the audience and send settings in Klaviyo. An AI review can support this work; the operator still needs to verify the final message.
12. Compare two sends without inventing the explanation
Compare [CAMPAIGN A] and [CAMPAIGN B] for [DATES]. Show available delivered volume, click rate, attributed orders and revenue, revenue per delivered message, unsubscribes and complaints. State definitions and attribution settings where available. Flag audience, offer, timing and volume differences that limit comparison. Separate observations, possible explanations and missing evidence. Do not claim one creative caused the difference or invent unavailable values.
Review next: whether the comparison is fair. A sale to recent buyers and an educational send to prospects answer different questions. Use the result to design the next investigation or controlled test.
13. Bring in a specific connected source
Use the enabled [APP CONNECTOR] to review [EXACT FILE, FRAME LINK OR SOURCE] for [DATE RANGE, IF RELEVANT]. Identify which source you accessed and summarize the facts or assets relevant to [CAMPAIGN]. Ask me to choose the audience, product and offer before drafting. If this connector cannot access the source or perform the action, explain the limitation rather than substituting another source.
Connect the app first under Customize → Connectors and confirm it is enabled. Referencing Figma, Canva or Shopify in a prompt does not grant access. Available actions depend on the connector; follow Klaviyo’s connector setup and usage guidance, then check the result against the original source.
14. Turn a useful report into a weekly task
Help set up a weekly analysis task for Mondays at [TIME AND TIME ZONE], comparing the previous complete Monday–Sunday period with the one before it. Report [CHOSEN METRICS] for [NAMED CAMPAIGNS OR FLOWS], with definitions, missing-data notes and up to three changes worth investigating. Show the task, schedule and output destination for confirmation before enabling it. This task is analysis only; it must not send customer messages or edit account assets.
Review next: the first report against the account and the exact reporting boundaries. Composer’s current getting-started guide documents scheduled analysis. Scheduling a report and scheduling a marketing send are separate actions.
15. Save a briefing process as a reusable skill
Help turn our approved campaign-briefing process into a reusable Composer skill, if available in this account. It should collect the goal, eligible audience, approved product facts, exact offer terms, destination URLs, voice reference and success metric. It should flag missing inputs, produce one brief for review, then wait for approval before generating content. Show me the proposed instructions before saving. Do not change our brand guidance or activate any campaigns.
Review next: run the process on one real brief and inspect which questions it missed. Keep reusable instructions short and specific. Update them when the offer rules, brand guidance or approval process changes.
Apply the brief to a signup form
Klaviyo added signup-form creation and editing in Composer on 6 November 2026. A proposal and a saved draft are separate states. Editing an existing form requires a single draft; use the form editor for forms in an A/B test. Accepting an update replaces the existing saved draft, so inspect any work already there.
Try a narrowly defined request: “Propose a signup form for [AUDIENCE], collecting [FIELD] into [LIST]. Use the approved offer [TERMS]. State the stored property, trigger and targeting. Show desktop and mobile previews. Identify any current draft that would be replaced, and wait for review before saving.”
Then submit a controlled profile and inspect the stored answer, promised incentive and first message. Our Ouidad case shows why these checks belong together; its historical form work does not establish use of Composer.
How to get more value from the prompts
Use one prompt to find or define the problem, one follow-up to examine the evidence, and a separate request to draft the agreed work. This gives the reviewer a clear decision at each step.
When an answer is vague, narrow the audience, time period or asset. When a draft is weak, correct the missing brief rather than generating many unexplained alternatives. Requests and revisions can consume capacity; check your current Composer plan and usage.
Before launch, confirm the offer, stock and product facts; inspect consent and exclusions; test personalization, links and rendering; and check the final campaign or flow settings. Review Klaviyo’s AI-use disclosure guidance linked from its creation documentation where relevant.
If you need a team to turn findings into a prioritised lifecycle plan and implementation, review Thrivelia’s services. Bring the account question and the work your team can already own.

.png)
Comments