Step 1
Collect the audience segments in use, the customer events recorded against them, the approved message library and the permissions in force for each contact and channel.
A merchant has customer events and an approved message library but no rule for which lifecycle moments to automate. In this case, the immediate task is to design lifecycle email marketing automation. The workflow should produce an email automation map and test scenarios, with each trigger, timing and stop rule traceable to the merchant's records.
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 design lifecycle email marketing automation.
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 audience segments in use, customer events recorded against them, the approved message library, and the permissions in force for each contact and channel]. Admit a lifecycle moment to automation only where the records show a repeatable event, an approved message that fits it and a definable end, then set its trigger, timing and stop rule from those records rather than from the calendar.
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 audience segments in use, the customer events recorded against them, the approved message library and the permissions in force for each contact and channel.
Admit a lifecycle moment to automation only where the records show a repeatable event, an approved message that fits it and a definable end, then set its trigger, timing and stop rule from those records rather than from the calendar.
Deliver an email automation map and test scenarios where every trigger, timing and stop rule cites the record supporting it, then confirm each flow exits as defined and report moments rejected for insufficient evidence.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
A moment backed by a recorded event that recurs across contacts, an approved message that fits it and a condition that ends it; interest or seasonality alone does not qualify, because neither can be verified against the store's own records.
Anchor it to the event timestamp in the record and to the merchant's stated expectations rather than to a send schedule, so the same moment produces the same delay for every contact and any timing without a stated basis is recorded as provisional.
Exit to a defined state and stop sending, whether the goal was met or the contact became ineligible; flows that simply run out of messages without an exit condition keep contacts in automation with no purpose.
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.