Help me prepare a helpful retail sales conversation for this customer situation. Use only product facts, policies, and customer details I provide. Do not invent stock availability, discounts, warranties, safety claims, product comparisons, financing terms, delivery dates, or customer needs. Do not use pressure tactics or imply scarcity unless it is confirmed. [PRODUCTS AND POLICIES] [CUSTOMER SITUATION] [STORE CONTEXT] [MY GOAL FOR THE CONVERSATION] [KNOWN OBJECTIONS OR CONSTRAINTS] First, identify what information is known, what must be discovered, and what cannot be promised. Then produce:
1. A 20-second opening that invites the customer to explain their project or intended use without trapping them in a yes-or-no question. 2. Six discovery questions in a sensible order. Cover use case, user, environment or fit, priorities, budget range only when appropriate, timing, and decision constraints. For regulated, health, child-safety, or technical products, include a question that identifies when a specialist or manufacturer guidance is needed. 3. A needs-to-products guide with two or three recommendation paths: good fit, premium or expanded fit, and a lower-cost or lower-commitment option when supported by the assortment. State the tradeoff for each path and do not rank products using facts I have not supplied. 4. Short responses to the stated objections using acknowledge, clarify, evidence, and next step. Do not argue with the customer. 5. A closing that offers one concrete next action appropriate to the context: compare two items, check fit, arrange a demonstration, verify inventory, place an order, or give the customer time with a written comparison. 6. A brief handoff note template if another associate, department, or service team must continue the sale. Keep the tone conversational and respectful. Before answering, check that every product claim comes from the supplied facts and that each recommendation follows from a customer need rather than a commission or inventory preference. Flag facts an associate must verify in the store system. Ask up to 3 clarifying questions only if a required input is missing. Output the conversation playbook in the sections above.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [PRODUCTS AND POLICIES] | List the products or categories, verified features, prices or ranges, return or warranty policies, and facts that need system verification. | Trail running shoes: Ridge 2 has wide sizing and a rock plate; Summit Lite is lighter with less protection. Prices are $140 and $125. Returns accepted unworn within 30 days; inventory must be checked in the POS. |
| [CUSTOMER SITUATION] | Describe what the customer has said, their intended use, people involved, stated preferences, and any known budget or timing. | Customer runs 3 to 5 miles on rocky local trails twice a week, says their current shoes feel narrow, and is buying before a trip next month. |
| [STORE CONTEXT] | State the store type, service model, inventory constraints, fitting or demo options, and any specialist support available. | Specialty running store with gait observation, fitting bench, and a manager available for technical footwear questions. |
| [MY GOAL FOR THE CONVERSATION] | State the appropriate outcome, such as helping a customer compare, book a consultation, place an order, or return later with information. | Help the customer leave with the right pair or a clear comparison after trying both models. |
| [KNOWN OBJECTIONS OR CONSTRAINTS] | List price, fit, compatibility, timing, policy, accessibility, safety, or decision-maker concerns already raised. | Customer says $140 feels high and wants to know if either shoe will prevent ankle injuries. |
How to use
- Enter verified product information and store policies; do not rely on memory for returns, warranty, inventory, or safety claims.
- Describe the shopper's intended use in their own words, because the discovery questions should uncover gaps rather than repeat a script.
- Check the recommendation paths against actual availability and replace any claim the model flags for POS or manufacturer verification.
- Follow up with: “Adapt this playbook for a shopper who is browsing with a partner who makes the final purchase decision.”
Variations
Retail product comparison
Use this when a customer is deciding between two or three known items.
Create a customer-friendly comparison for [PRODUCT A], [PRODUCT B], and [PRODUCT C] using [VERIFIED SPECS], [CUSTOMER NEEDS], and [STORE POLICIES]. Make a table with use case, material differences, tradeoffs, price, care or compatibility, and facts to verify. Then write 5 discovery questions and a neutral recommendation statement. Do not call an item “best” without a stated customer priority, and do not invent inventory or warranty terms. Check that each comparison point comes from verified specs. Output the table and conversation script.
Retail objection handling
Use this when associates hear the same price, fit, or trust objections repeatedly.
Write retail objection responses for [PRODUCT CATEGORY] using [VERIFIED FACTS], [COMMON OBJECTIONS], [STORE POLICIES], and [CUSTOMER TYPE]. For each objection, provide an acknowledgement, one clarifying question, a factual response, and a respectful next step. Include boundaries for claims an associate must not make, particularly safety, medical, technical, or financing claims. Do not use artificial urgency. Check every policy and product statement against the supplied facts. Output a pocket-sized objection guide with responses under 70 words each.
Clienteling follow-up
Use this after an in-store interaction when the customer has consented to follow-up.
Write a retail follow-up message to [CUSTOMER] after they considered [PRODUCTS], using [CONVERSATION NOTES], [VERIFIED AVAILABILITY], and [PERMITTED CONTACT POLICY]. Keep it under 90 words and remind them of the need or preference they stated, the items compared, and one optional next action. Do not imply that stock is reserved, claim a discount, or use personal details beyond the notes. Check that the message honors contact consent and does not make unsupported product claims. Output email and text-message versions.
Tips
- Start with intended use and fit before presenting products; the customer often has a different decision criterion than the product category suggests.
- For price objections, clarify the comparison point and show a verified tradeoff rather than defending the price.
- Never make injury-prevention, medical, safety, or compatibility claims beyond approved product language; bring in a specialist when the choice carries material risk.
- A written comparison is a useful close for a customer who is not ready to buy, because it preserves the facts they need to decide later.
FAQ
Can AI write a retail script for any product category?
It can structure discovery and recommendation paths, but product facts and policy claims need to come from approved store sources. High-risk categories also require the right specialist or manufacturer guidance.
How many questions should an associate ask before recommending a product?
Ask enough to establish the use case, constraints, and priority, then make a relevant suggestion. Six prepared questions does not mean every customer needs all six.
Should a retail sales script always end in a purchase ask?
No. The right close may be a fitting, comparison, inventory check, consultation, or permission to follow up. It should match the customer's readiness.