01
Step 1
Gather the event definitions with the properties each one carries, the segment rules, the approved messages, the eligibility conditions that admit a customer, and the suppression list already honoured across channels.
Back to topic
Spark playbook scenarios · Spark: AI Store Assistant
Build a lifecycle email sequence with entry and exit rules
Welcome, browse abandonment and post-purchase flows overlap, so one person can receive three messages in a day and none the following week. In this case, the immediate task is to build a lifecycle email sequence with entry and exit rules. The workflow should produce an email automation map and test scenarios covering duplicate events and shifting states.
Topic
Email Marketing Automation
Target keyword
shopify automated email sequences
Copyable AI prompt
A prompt you can drop directly into Spark
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.
ai-prompt.txt
Act as a Shopify operations specialist.
Help me build a lifecycle email sequence with entry and exit rules.
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: [event definitions with their properties, segment rules, approved messages, eligibility conditions, and the cross-channel suppression list]. Map each entry trigger to its wait, its branch and its exit, resolve what happens when a customer qualifies for two flows on the same day through a written precedence order, and test duplicate events to confirm one customer cannot be enrolled twice for the same event.
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.How to solve
A recommended resolution workflow
Split the work into input, judgment, and deliverable phases. Verify each step's output before moving to the next.
02
Step 2
Map each entry trigger to its wait, its branch and its exit, resolve what happens when a customer qualifies for two flows on the same day through a written precedence order, and test duplicate events to confirm one customer cannot be enrolled twice for the same event.
03
Step 3
Deliver the lifecycle map with test scenarios covering a duplicate event, a state change mid-flow and a suppressed contact, then verify each scenario against the supplied records and list any branch with no defined exit.
FAQ
Common questions when running this scenario
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
How is a same-day double qualification resolved?
A precedence order written into the map decides which flow holds the customer while the other records the hold; the held flow may resume only if the customer still qualifies once the first ends, so the overlap produces one message rather than two.
What does a state change mid-flow require?
Re-evaluation at the next wait point against both the entry and the exit conditions, since the customer who entered may no longer match; messages already queued are cancelled rather than sent late, and the cancellation shows in the contact history.
How is suppression applied across channels?
The suppression list is checked at send time, not only at entry, because consent can change while a customer waits inside a flow; opting out of one channel does not remove consent for another unless the merchant's policy says it does.
Related scenarios
Continue with adjacent or same-topic scenarios
Start with scenarios under the same topic, then expand into cross-topic matches suggested by similarity.
Next step
Want these AI scenarios embedded directly into daily operations?
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.