Step 1
Collect the current unfulfilled orders with their due context, the team ownership rules naming who handles which stage or location, and the notification channels available to each owner.
Alerts reach the team without saying which order needs action or who should act, so they are routinely ignored. In this case, the immediate task is to define actionable alerts for unfulfilled orders. The workflow should produce alert definitions and routing rules, each one naming the order, the reason for attention and the next step for its owner.
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 define actionable alerts for unfulfilled orders.
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: [current unfulfilled orders with their due context, team ownership rules naming who handles which stage or location, and the notification channels available to each owner]. Write each alert so it names one order, the reason it needs attention and the next step for its owner, and route it only to that owner's channel, suppressing any alert whose order carries a documented hold until the hold clears.
Return alert definitions and routing rules 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 current unfulfilled orders with their due context, the team ownership rules naming who handles which stage or location, and the notification channels available to each owner.
Write each alert so it names one order, the reason it needs attention and the next step for its owner, and route it only to that owner's channel, suppressing any alert whose order carries a documented hold until the hold clears.
Deliver alert definitions and routing rules with the severity levels, the escalation path and the response window per level, then test each alert against real open orders and confirm the intended owner receives it.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
The order reference, the stage where it is stuck, the elapsed time and the one action expected, because an alert reporting only a count leaves the reader to find the order and decide the response unaided.
Enough to separate a routine reminder from a commitment already breached, set against the merchant's stated windows; more levels than the team can act on differently only relabel the same queue.
Escalate to the next named owner once the stated response window passes with no state change, and log the escalation, so unresolved work gains visibility instead of repeating the same message to an inbox nobody reads.
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.