Step 1
Collect the lead stages the team works with, the message attached to each stage, the owner responsible for replying, and the entry condition that moves a lead from one stage to the next.
Follow-up depends on whoever happens to remember the lead, so the same stage can be handled in a different order by different people. In this case, the immediate task is to define a consistent sales follow-up workflow. The workflow should produce the ordered stages with their messages, owners and stopping point, checked against the rules the team has stated.
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 a consistent sales follow-up workflow.
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: [lead stage definitions, the message attached to each stage, the named owner for each reply, and the entry condition that moves a lead between stages]. Sequence the touches so each one is triggered by the outcome of the previous touch rather than by elapsed time alone, and set an exception branch for a lead that replies, opts out or stalls so no stage is skipped and no lead is contacted twice on the same step.
Return the workflow and follow-up schedule 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 lead stages the team works with, the message attached to each stage, the owner responsible for replying, and the entry condition that moves a lead from one stage to the next.
Sequence the touches so each one is triggered by the outcome of the previous touch rather than by elapsed time alone, and set an exception branch for a lead that replies, opts out or stalls so no stage is skipped and no lead is contacted twice on the same step.
Deliver the workflow as an ordered stage list with its follow-up schedule and a defined stopping point, then walk one real lead through every branch and confirm against the merchant's records that each owner, message and exit condition fires as stated.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
No, every stage still needs a named person. Automation moves the record and sends the prompt, but only an owner can read the context, answer a reply, or decide that a lead should leave the sequence early.
Only as many as the decision steps recorded for the offer. Each touch needs a reason to exist, and after the defined last touch the lead should exit to a review state rather than continue on a timer.
Set a priority in advance, usually customer reply over scheduled send. Without a rule the system can send two messages the same day, which reads as duplicated outreach and costs the owner the thread.
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.