A merchant receives damage complaints scattered across email and support tickets, with no single place showing which cases are real damage and which are late parcels. In this case, the immediate task is to surface damaged-shipment reports for follow-up. The workflow should produce one line per case with the evidence attached and the owner who must act.
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 surface damaged-shipment reports for follow-up.
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: [damage complaints with their arrival channel, order and carrier references, the condition described, customer photos and messages, and each carrier's claim rules with required evidence and filing deadlines]. Classify each case as confirmed damage where the account and the supplied evidence describe the item's condition, as a transit delay where the complaint concerns timing rather than condition, and as awaiting evidence where the carrier requires material the record does not yet hold, then assign each case to the carrier claim path or to the internal owner named in the merchant's records and set its deadline from the carrier rule.
Return a damaged-shipment list with evidence and follow-up actions 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, for the merchant-defined window, every damage complaint with the channel it arrived on, the order and carrier reference, the condition the customer describes, the photos or messages supplied, and the carrier's claim rules including the evidence required and the filing deadline that applies.
Classify each case as confirmed damage where the account and the supplied evidence describe the item's condition, as a transit delay where the complaint concerns timing rather than condition, and as awaiting evidence where the carrier requires material the record does not yet hold, then assign each case to the carrier claim path or to the internal owner named in the merchant's records and set its deadline from the carrier rule.
Deliver one row per case with its classification, the evidence attached, the owner and the next action, keep cases awaiting evidence open in their own section rather than closed, and reconcile the row count against the complaint sources searched so no reported case is silently missing.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
Follow the carrier rule on record, and where evidence is required note it as missing, keep the case open and send a request, because closing it removes the only chance to recover inside the deadline. Where the carrier accepts a written description alone, the case proceeds without a photo.
Both, on separate tracks, with the customer acknowledged inside the merchant's stated response time while the carrier claim follows its own process. Using one track makes the customer wait on the carrier, and the boundary is a case where safety or recall rules require an immediate merchant response.
Damage is a condition claim with its own evidence and deadlines, while a delay is a timing question resolved by the next scan. Mixing them hides the action each case needs and lets claim deadlines pass inside a queue of late parcels.
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.