01
Step 1
Pull every open lead with its last contact date, the current owner, the outcome still pending and any urgency the inquiry itself records.
Back to topic
Spark playbook scenarios · Spark: AI Store Assistant
Set meaningful follow-up reminders for open leads
Open leads sit in the pipeline without a next action date, so reminders fire at random intervals or not at all. In this case, the immediate task is to set meaningful follow-up reminders for open leads. The workflow should produce a reminder schedule tied to each lead's last contact, current owner and pending outcome, using the merchant's own records.
Topic
Lead Outreach and Follow Up
Target keyword
shopify lead follow up reminders
Copyable AI prompt
A prompt you can drop directly into Spark
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.
ai-prompt.txt
Act as a Shopify operations specialist.
Help me set meaningful follow-up reminders for open leads.
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: [open leads with their last contact date, current owner, pending outcome, and any urgency recorded on the inquiry]. Set each reminder against the last contact date rather than the date the lead arrived, apply the agreed interval, and raise an exception for any lead with no owner or no pending outcome, since a reminder without either is fired into an empty queue.
Return the reminder schedule with the outreach draft 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.How to solve
A recommended resolution workflow
Split the work into input, judgment, and deliverable phases. Verify each step's output before moving to the next.
02
Step 2
Set each reminder against the last contact date rather than the date the lead arrived, apply the agreed interval, and raise an exception for any lead with no owner or no pending outcome, since a reminder without either is fired into an empty queue.
03
Step 3
Deliver a dated reminder schedule with the outreach draft attached to each row, stop reminders the moment a lead replies or exits the sequence, and verify against the merchant's records that every scheduled row carries an owner and a next action.
FAQ
Common questions when running this scenario
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
How soon should the first reminder fire?
Count from the last contact date, using the interval the team has agreed, shortened where the inquiry records urgency. Counting from the arrival date instead stacks several reminders on the same day for leads that were already touched.
What if a lead has no owner?
Assign one before scheduling and list unowned leads as exceptions. A reminder with no named owner is usually dismissed when it fires, which quietly turns a live lead back into a dormant one.
Should reminders stop after no reply?
Yes, once the defined sequence ends, stop and move the lead to a review state. Continued contact without a response rarely changes the outcome, and it adds noise that hides the leads that did reply.
Related scenarios
Continue with adjacent or same-topic scenarios
Start with scenarios under the same topic, then expand into cross-topic matches suggested by similarity.
Next step
Want these AI scenarios embedded directly into daily operations?
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.