Step 1
Collect the stated goal of the sequence, the customer situations it has to cover, any ordering constraints such as a required first or final message, and the brand voice rules.
A planned sequence repeats the same argument in every message, so later emails add little once the earlier ones are read. In this case, the immediate task is to plan the content of a purposeful email sequence. The workflow should produce sequence content plans and a reusable structure, giving each message one job and cutting points already made.
First replace every [bracketed] placeholder with real store scope and constraints, then add any actual records or data you have, and paste it into your preferred AI assistant or Spark agent. Spark will follow this page's workflow to produce structured output and verification steps.
Act as a Shopify operations specialist.
Help me plan the content of a purposeful email sequence.
My store context is [describe the business, products and target audience].
My scope is [specify the affected products, pages, customers or reporting period]. Use these inputs: [the stated goal of the sequence, the customer situations it must cover, ordering constraints such as a required first or final message, and the brand voice rules]. Give each message exactly one job in the decision path, state the new information or action it carries, and cut any point already made earlier, marking a message for removal where it adds nothing beyond repetition.
Return sequence content plans and reusable structure for the specified task.
Show the relevant evidence or before-and-after examples and explain how I can verify the result.
If essential data is missing, ask for it and mark unsupported conclusions as unknown.
Do not invent metrics, product claims or customer facts.
For any publication, message, account or store change, use only connected tools within my explicitly authorized scope and report success only after verification; otherwise provide the draft or proposed steps.Split the work into input, judgment, and deliverable phases. Verify each step's output before moving to the next.
Collect the stated goal of the sequence, the customer situations it has to cover, any ordering constraints such as a required first or final message, and the brand voice rules.
Give each message exactly one job in the decision path, state the new information or action it carries, and cut any point already made earlier, marking a message for removal where it adds nothing beyond repetition.
Deliver sequence content plans and a reusable structure showing the goal, the job, the position and the exit condition per message, then check the whole sequence against the goal and report dropped arguments with their reasons.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
Write the job as a single sentence before drafting and let anything outside it move to another message or out of the sequence, because a message serving two jobs usually does neither well and leaves the next step unclear.
Give it to the earlier one and cut it from the later, since repetition reads as padding and costs attention for the argument that follows; where the later message then has no job left, remove it from the plan.
Define the outcome and the exit condition up front and test the drafted messages against both, so the sequence ends with an action the customer can take instead of trailing off after the last reminder.
Start with scenarios under the same topic, then expand into cross-topic matches suggested by similarity.
Ciwi Spark builds Shopify-native AI tools and agents around the workflows merchants actually run: research, ads, translation, and customer support. Stop rewriting the same prompts by hand.