Back to topic
Spark playbook scenarios · Spark: AI Store Assistant

Draft a reactivation email campaign

One blanket discount was planned for the whole lapsed list even though the products those customers buy follow different seasonal timing. In this case, the immediate task is to draft a reactivation email campaign. The workflow should produce a campaign plan with sequence, subjects and send timing checked against the merchant's own offer rules.

Topic
Customer Churn and Winback
Target keyword
shopify winback email campaign
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 draft a reactivation email campaign.
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 eligible inactive segment with last order dates and product timing, the applicable offer rules and approvals, the stated seasonal timing, and the campaign calendar]. Plan the sequence, subjects and send timing so each variant reaches customers when the product they last bought is due again rather than on one date for the whole list, keep every offer inside the merchant's stated rules and approvals, and split the list by purchase context only where the records support a difference.
Return a reactivation email campaign inside a winback plan 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.
Use in Spark
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.

01

Step 1

Collect the eligible inactive segment with each customer's last order date and product timing, the offer rules that apply including whatever needs approval, the seasonal or product timing the merchant has stated, and the campaign calendar the send has to fit around.

02

Step 2

Plan the sequence, subjects and send timing so each variant reaches customers when the product they last bought is due again rather than on one date for the whole list, keep every offer inside the merchant's stated rules and approvals, and split the list by purchase context only where the records support a difference.

03

Step 3

Deliver the campaign inside the winback plan with the sequence, subjects, send dates and offer for each variant, verify the recipient list against the eligible segment to confirm nobody outside it is included and no eligible customer is silently dropped, and flag anyone whose eligibility the records do not settle.

FAQ

Common questions when running this scenario

Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.

Should the whole list receive the send on one date?

Only when the products share a repurchase timing; where they do not, the send dates follow each group's cycle, because a single date reaches part of the list before it is due and part of it long afterwards.

How is each offer checked before the send?

Against the merchant's stated offer rules and approvals, variant by variant, with the rule recorded next to the offer; an offer that needs approval and lacks it is reported as blocked rather than sent with the risk of honouring an unapproved discount.

What belongs in the pre-send check?

Recipient count against the eligible segment, suppression and opt-out matches, the offer applied per variant and a rendered test of each message, so a mismatch is caught before the send rather than after customers receive the wrong version.

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.