Step 1
Collect the recurring request types ranked by how often they appear, the approved policy answer behind each, and the order fields a reply must quote such as order reference, dispatch status and the delivery window shown in the record.
Order-status questions dominate the inbox, and answers written on the spot commit to different refund wording depending on who replies. In this case, the immediate task is to draft consistent replies to common customer requests. The workflow should produce a support operating workflow and sample ticket outcomes tied to each request type.
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 draft consistent replies to common customer requests.
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: [recurring request types by frequency, the approved policy answer for each, and the order fields a reply must quote]. Write one approved reply per type that uses the same wording for the same facts and takes every value from the order record, and record for each type the conditions under which an agent must answer personally instead.
Return sample ticket outcomes inside a support operating workflow for every request type 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 recurring request types ranked by how often they appear, the approved policy answer behind each, and the order fields a reply must quote such as order reference, dispatch status and the delivery window shown in the record.
Write one approved reply per type that uses the same wording for the same facts and takes every value from the order record, and record for each type the conditions under which an agent must answer personally instead.
Deliver the sample ticket outcomes inside the support workflow with each reply shown against a real ticket, then check every reply against the policy text it came from and flag any sentence committing to something the policy does not guarantee.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
The same facts produce the same commitments in the same words, even where greetings differ; a reply that adds a promise the policy does not make is a defect however helpful it reads, because the customer will hold the store to whichever version they received.
They are split into one reply per topic or handed to an agent, since merging two policies into one message creates a combined commitment neither policy supports; the ticket keeps both topics recorded so the second one is not lost.
The role that owns the underlying policy, with the effective date recorded against the reply; replies built on a superseded policy are retired rather than edited in place, so a customer's earlier answer can still be explained.
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.