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

Create reusable inquiry email templates

A few buyer questions keep arriving, and each reply is rewritten from scratch with wording nobody has reviewed. In this case, the immediate task is to create reusable inquiry email templates. The workflow should produce one template per recurring question type with variable fields, a stop condition and the approved claims and tone rules behind them.

Topic
Lead Outreach and Follow Up
Target keyword
ecommerce inquiry email templates
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 create reusable inquiry email templates.
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 question types, the approved wording and tone rules for each, the variable fields every template has to expose, and the merchant's stop condition for a thread].

Draft one template per question type, each with the same fixed structure of opening answer, evidence line and next step, and mark as an exception any question whose answer depends on a value the template cannot fill from the merchant's own records, routing it to a human reply instead.
Return the template set 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.
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 recurring question types with the wording the team has approved for each, the tone rules that apply to replies, and the variable fields every template has to expose, such as product name, quantity, lead time and the quoted price basis.

02

Step 2

Draft one template per question type, each with the same fixed structure of opening answer, evidence line and next step, and mark as an exception any question whose answer depends on a value the template cannot fill from the merchant's own records, routing it to a human reply instead.

03

Step 3

Deliver the template set with a follow-up schedule that names the interval and the stop condition for each thread, verify that every claim in every template traces back to a supplied record, and re-run the check after any change to the approved wording or offer.

FAQ

Common questions when running this scenario

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

How many templates are enough?

One per recurring question type, kept to the set the team can keep accurate. Adding a template for a question asked once creates wording nobody reviews, and an outdated template misleads more buyers than no template at all.

Can a template be sent without editing?

No, the variable fields have to be filled and the answer checked against the case. The template fixes structure and approved wording; it does not relieve the sender of confirming that the quoted value, stock state and timing still hold for this buyer.

Which claims need approval before use?

Any statement of price, availability, lead time, warranty or certification, because these commit the merchant. Write only what the supplied records support, and leave a placeholder wherever the value must be confirmed before sending.

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.