Composer prompts to test and practical starting points

Hey everyone,

I put this list together for anyone opening Composer and thinking, “Okay, but what should I actually ask it?”

The short answer: start with one clear job, give Composer the context it needs, and use follow-up questions to get from a broad finding to a practical next step. There isn’t one best prompt for every account. Composer works from the data, setup, and content available in your account, so always review what it returns before you act.

If you’re new to Composer, this Composer community overview is a good place to start. Composer can analyze and audit existing marketing, QA a campaign, and draft new campaigns or flows for you to review. It recommends, drafts, and audits; you make the edits and the final send decision.

What’s the best way to prompt Composer?

I keep coming back to a simple three-step pattern:

1. Go wide: Ask Composer to find the highest-priority opportunity.
2. Get narrow: Choose one finding and ask why it was flagged.
3. Take action: Ask for a numbered plan of what to review or change.

For example:

1. Wide: Audit my flows and tell me what needs attention first.
2. Narrow: Tell me more about the highest-priority issue. Why was it flagged?
3. Action: Give me a numbered plan for addressing this issue. What should I review in Klaviyo?

That follow-up step matters. A broad prompt can help you find where to look, but a focused prompt usually gives you a more useful answer.

11 Composer prompts to copy and adapt

1. Which flow issues should I investigate first?

Audit my flows and tell me what needs attention first. Give me the top 5 findings and explain why each matters. If you can’t verify a finding from my account data, say so.

Composer’s flow audits are recommendations, not automatic changes. Review the findings and make the edits yourself. For more detail, see how to audit with Composer.

2. Why did Composer flag this flow issue?

Tell me more about [ISSUE OR FLOW NAME]. What in my account supports this finding? Separate confirmed details from hypotheses, then give me a numbered list of settings or content to review.

This is a useful follow-up when an audit sounds plausible but you want to see what data supports it.

3. How is one flow performing at the message level?

Analyze [FLOW NAME] over the last 90 days at the message level. For each message, report recipients, open rate, click rate, placed order rate, and revenue per recipient if available. Identify the messages that appear weakest relative to others in this flow, and explain what data supports that comparison. If a metric or time range is unavailable, say so rather than estimating.

For a cleaner result, start with one flow instead of asking for a large account-wide report. You can also review flow message performance in Klaviyo’s reporting tools with Understanding flow analytics.

4. Are any live flows conflicting?

Are any of my live flows conflicting with each other or stacking messages too closely? Name the flows involved, explain what overlap or timing issue you found, and tell me what data supports it. If you can’t determine the audience overlap, say so rather than estimating.

Keep this request focused on flows. Don’t assume the audit covers every upcoming campaign or every possible cross-campaign collision. The Composer public beta discussion has more context on flow audits and what Composer can review.

5. Did signup-form performance change?

Check signup rate for the last 7 days, overall and by signup form. Compare each form with its trailing 4-week average and flag meaningful spikes or drops. Name the forms most responsible for each change, and note any data gaps. Don’t infer a cause unless the data supports it.

The last sentence is doing important work here. A change in signup rate is a finding; it isn’t automatically an explanation.

6. What purchase patterns appear around discount campaigns?

Analyze the last 180 days of purchase behavior alongside campaign send history. Compare orders placed within 48 hours of a discount campaign with orders outside that window. Report the share of orders and average order value for each group, and show how the share of discounted orders changes month over month. Compare repeat purchase rates for customers whose first order used a discount code with those who paid full price. Describe patterns as associations, not proof that a campaign caused a purchase, and note any data gaps.

This kind of prompt can surface patterns worth investigating. It can’t prove that a campaign caused a purchase, so keep that distinction in the final readout.

7. How do I QA a campaign before sending it?

QA this campaign before I send it. Check its links and tracking, audience and exclusions, send configuration, A/B test setup, and compliance basics. Separate issues that could block the send from lower-priority polish items. Identify the exact setting or content that needs review; don’t make the final send decision for me.

Composer audits one campaign at a time. I’d still run a preview with a real profile and send a test before launch. This pre-send QA checklist walks through the full sequence.

8. Can Composer review one email or SMS message?

When you’re viewing the message or template you want to review, try:

Audit this [EMAIL/SMS] for accessibility, deliverability, compliance, and content quality. Check links, alt text where relevant, message length, opt-out requirements where relevant, and the primary CTA. Give me the highest-priority findings first and identify the exact element affected.

Content audits cover a single email or SMS/MMS message at a time. For compliance-related findings, review the requirements that apply to your business before making changes. See what Composer can analyze and create.

9. How can I build a campaign from a brief?

Create an email and SMS campaign for [AUDIENCE] about [PRODUCT OR EVENT]. The goal is [GOAL], and the offer is [OFFER, IF ANY]. Provide 3 subject lines, 3 preview texts, email copy with one primary CTA, and one SMS version under [YOUR CHARACTER LIMIT]. Use a [TONE] tone. If key details are missing, ask before drafting.

Composer can draft email, push, SMS, and MMS campaigns from a natural-language brief. It starts with your customers, data, and campaign context, then brings the draft back for you to review and edit. Check the product details, offer, links, audience, and consent settings before using the draft. Here’s the Help Center guide for creating campaigns with Composer.

10. How can I draft a flow from a goal?

Design a new flow to [GOAL, e.g., win back customers who have not purchased in 90 days]. Include the trigger and entry filters, channels and number of messages, delays, objective of each message, and a recommended exit condition. Flag assumptions about my existing flows. Present the result as a numbered build plan for me to review.

For a more specific result, name the channels and timing you want, such as “2 email messages and 1 SMS message; send the first message after 1 hour.” Composer drafts the flow and messages; review the structure and content before setting anything live. See how to create flows with Composer.

11. What changed between two campaign periods?

Compare campaign performance for [PERIOD 1] and [PERIOD 2]. Report delivered volume, open rate, click rate, conversion rate, revenue, unsubscribe rate, and spam complaint rate where available. Show the percentage change for each metric. If data is missing or the periods aren’t directly comparable, say so rather than estimating. Do not make recommendations unless I ask.

Then, if you want to move from reporting to prioritization:

Based on those results, what are the 3 opportunities worth investigating first? Tie each one to a specific finding and label assumptions clearly.

What should I add when a Composer answer feels generic?

Keep the conversation going. Usually, one more piece of context is enough to make the next answer more useful:

• Name the audience more precisely, such as “lapsed VIP customers” instead of “customers.”
• Add the product, offer, date range, or metric you care about.
• Ask for fewer findings: Give me the top 3 only.
• Ask Composer to separate what it can verify from what it is inferring.
• When working from an existing template or draft, describe what you want changed instead of restating the full brief.

That lines up with Klaviyo’s prompt best practices for Composer: use natural language, provide relevant context, and refine the answer in the same conversation.

What should I check before acting on a Composer answer?

Before you publish, send, or change anything, I’d check:

• Prices, discounts, product details, dates, links, and other factual claims.
• Audience, exclusions, consent, and segment logic.
• Whether estimated impact or causal explanations are being treated as hypotheses.
• Every line of generated copy, including personalization and SMS length.
• The exact settings Composer recommended, then re-run the audit after edits if you want a second review.

Composer can help you find the work and get moving faster. It doesn’t replace your review or judgment, and there’s no “send as-is” button hiding in the bushes. For more ideas, browse Klaviyo’s AI Prompt Library.