Step 1
Collect the events available after a first order such as payment, fulfilment, delivery confirmation and second purchase, the segment rules in use, the approved message library, and the exit conditions the merchant has stated.
First-time buyers get little guidance after checkout, and no ordered flow carries them toward a second purchase. In this case, the immediate task is to create a nurture sequence for new customers. The workflow should produce an email automation map and test scenarios, ordering each message from the first purchase and ending at the stated stop condition.
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 create a nurture sequence for new customers.
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: [post-purchase events including payment, fulfilment, delivery and second purchase, segment rules, approved messages, and stated exit conditions]. Order the messages against those events rather than fixed day counts so each send waits for the event that makes it relevant, and place the exit check before every send so a customer who has already bought again or unsubscribed leaves the flow.
Return an email automation map and test scenarios 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 events available after a first order such as payment, fulfilment, delivery confirmation and second purchase, the segment rules in use, the approved message library, and the exit conditions the merchant has stated.
Order the messages against those events rather than fixed day counts so each send waits for the event that makes it relevant, and place the exit check before every send so a customer who has already bought again or unsubscribed leaves the flow.
Deliver the email automation map with one test scenario per branch, then walk each scenario through the supplied records and confirm no customer receives two messages from this flow for the same event.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
Event-based wherever the event exists, because a message about delivery sent before delivery reads as noise; day-based timing is a fallback for events the store cannot observe and is flagged so its results are not read as the event version's.
The flow waits rather than moving ahead, and after the merchant's stated waiting limit the message goes out with wording that does not assume delivery happened; sending the next step early answers a question the customer has not reached yet.
Not the new-customer flow, since a second purchase moves them to the next sequence and re-entry would repeat an introduction they have already had; re-entry needs an explicit rule and a suppression check against recent sends.
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.