How to Write a Klaviyo Flow Email Sequence from a Lifecycle Brief
Klaviyo flows invent 42 percent opens and 10 percent off. The brief had a 2 hour wait. Leave OFFER NONE.
The matching generator is the Klaviyo Flow Email Sequence from a Lifecycle Brief (No Invented Open Rates) (Klaviyo Flow Email Sequence From Lifecycle Brief No Invented Open Rates) prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).
Map trigger and waits from the brief only
Write a Klaviyo flow email sequence from a lifecycle brief. No invented open rates, click rates, or list sizes. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.
Paste these fields before you hit run:
Lifecycle brief (trigger, waits, offer facts): [Brief]
Email count I lock: [Count]
Subject character cap: [SubCap or 50]
Words I must not use: [Banned]
What I must never invent (open rates, list size, extra offers): [Never]
Output format: [Format]
Language: [Lang]
From-name I lock (or UNKNOWN): [From]
Discount I allow (or NONE): [Offer]
That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.
Honor email Count and subject caps
Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.
Walk the Generate list in order:
- Honesty ledger: Brief nouns, Count, SubCap, From, Offer, Lang. Forbidden: invented open rates, invented list size, extra SKUs.
- Flow map: trigger from Brief. Waits from Brief only. If a wait is missing, write WAIT UNKNOWN.
- Emails: exactly Count. Subject under SubCap. Body from Brief and Offer only.
- From: quote From or write FROM UNKNOWN.
- Refuse list: Mailchimp journey names, Instagram captions, invented 42 percent opens, invented 12k list.
- Offer: quote Offer or write OFFER NONE. Do not invent 10 percent off.
- Never: do not write 'this flow converts at 8 percent'.
- Compliance pass: quote Banned and Never hits. Cut them. Print subject counts. Format as Format.
If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.
Keep FROM UNKNOWN if no from-name was locked
Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.
Honor the constraints as hard stops, not vibes:
- Klaviyo flow from Brief. Not Mailchimp and not captions.
- Never invent open rates, click rates, or list sizes.
- Honor Count and SubCap.
- No emojis.
When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.
Refuse open rates list sizes and Mailchimp names
Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.
Tags on the card (klaviyo flow email sequence, no invented open rates, lifecycle brief klaviyo) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.
Fill the card, then run
Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.