The operations team wants alerts inside its WeCom workspace, but the event types, groups and recipients were never recorded together. In this case, the immediate task is to plan operational alert delivery to a WeCom destination. The workflow should produce the alert specification and message templates, with each route verified against the supplied 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 plan operational alert delivery to a WeCom destination.
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 alert types, the destination groups or applications, the recipients and their roles, the stated integration prerequisites including the authorised connection and destination identifier, and the accepted message format]. Map each alert type to one destination by severity and function, draft the payload in the accepted format with a mention or role tag for the responsible team, and flag any alert type whose connection, destination identifier or recipient is missing rather than assuming it will be configured later.
Return the alert specification and message templates 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 alert types, the destination groups or applications, the recipients and their roles, the prerequisites stated for the integration including the authorised connection and the destination identifier, and the message format the channel accepts.
Map each alert type to one destination by severity and function, draft the payload in the accepted format with a mention or role tag for the responsible team, and flag any alert type whose connection, destination identifier or recipient is missing rather than assuming it will be configured later.
Deliver the alert management specification and message templates, then verify every route against the supplied records by confirming that each alert type has a destination, a recipient and a payload whose every field exists in those records.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
A missing authorised connection, destination identifier or recipient, and any alert type without all three is marked as a draft rather than presented as working. A message with no recipient produces no failure signal, so the condition simply goes unnoticed.
A single group mixes payment faults with routine stock notices, and the routine volume buries the urgent ones. Routing by severity and function means each group receives only what its members can act on, and the mention in the payload reaches the responsible team directly.
The payload carries a mention or role tag for the responsible team and names the affected object and the change in the first line, so the message is actionable even from the notification preview. Longer context stays in the linked ticket or system.
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.