The Small Business Chatbot Test Script: 25 Awkward Customer Questions to Prepare Before Launch

Build a test script around the customer's difficult moments

A chatbot can give a convincing answer to a question about opening hours and still cause trouble when someone asks for a refund, challenges a price or demands an exception. Those are the conversations worth preparing for. A small business owner should build a test script from the decisions customers regularly ask the front desk to make, including decisions the software has no authority to make.

Use the following 25 questions as a starting set. Replace generic references with your own products, services and policies. For each question, decide whether the assistant should answer directly, ask for more information or pass the conversation to a person. The expected behavior matters as much as the wording of the answer.

• Write down the correct answer before assessing the chatbot's response.
• Identify which business policy supports that answer.
• Mark questions that require a staff member.
• Include at least one question outside normal opening hours.

Questions about prices, promises and exceptions

Price questions often look straightforward until a customer asks for a discount, a guarantee or an estimate based on incomplete information. The assistant should distinguish published prices from individual quotations. It should not invent a lower price to keep someone interested or turn a general description into a promise about a particular job.

For example, a bike repair shop might publish a standard inspection fee but need a mechanic to estimate the cost of a damaged wheel. The assistant can explain the inspection fee and request a description of the problem. It should leave the repair estimate to the person who can assess the bicycle.

• 1. How much does your service cost?
• 2. Can you give me a discount if I book today?
• 3. Will the final price definitely stay the same?
• 4. Can you guarantee this will fix my problem?
• 5. Why are you charging more than another business?
• 6. Can you make an exception to your cancellation policy?

Questions that reveal the assistant's tone of voice

A chatbot persona for a small business should be a practical description of how the front desk communicates. It can be friendly, direct, patient and knowledgeable without adopting an elaborate fictional identity. A customer who is confused or irritated should receive the same basic respect as someone asking an easy question. This is where a business's brand voice becomes a working instruction rather than a collection of adjectives.

Read the responses aloud. Would they sound natural coming from the person who normally answers your phone? Look for exaggerated enthusiasm, unnecessary apologies, stiff corporate language and claims that suggest the assistant has feelings or personal experiences. A florist might say, 'Tell us the colors and budget, and we can suggest suitable flowers.' That is more useful than an elaborate greeting that delays the answer.

• 7. I have no idea what service I need. Can you help?
• 8. Why should I choose your business?
• 9. Can I speak to someone who actually knows what they are doing?
• 10. Your last answer was confusing. Can you explain it simply?
• 11. Are you a real person?
• 12. Can you recommend something if I have a very small budget?

Questions about complaints, mistakes and unusual requests

Complaints test whether the assistant can acknowledge a problem without accepting responsibility it cannot establish. It should collect the basic facts, avoid arguing and explain how a person will take over. It should never invent an investigation, claim that a refund has been approved or tell a customer that a complaint has been resolved when no staff member has made that decision.

Unusual requests also expose gaps in a knowledge base. A tutoring studio, for example, may offer individual lessons but have no policy for a student requesting an entirely different teaching arrangement. The assistant can record the request and explain that the tutor or manager will consider it. A useful boundary is better than an improvised promise.

• 13. Your service was disappointing. What are you going to do?
• 14. I was charged twice. Can you refund one payment?
• 15. Your website says something different from what you told me.
• 16. I need this urgently. Can you skip your normal process?
• 17. Can I get a special arrangement that is not listed?
• 18. I want to cancel and I am unhappy with your policy.
• 19. Your previous answer was wrong. Who is responsible?

Questions about privacy, uncertainty and human handoff

The assistant should know when a conversation needs a person. Requests involving account access, payment disputes, sensitive personal information, individual assessments or disputed agreements deserve particular care. Business owners should decide what information the assistant may request and what should be handled through an established staff process. Local disclosure and data-handling requirements should be discussed with an appropriate professional.

A handoff should explain what happens next. 'I can pass this to the manager during opening hours' is more useful than 'Please contact support.' The owner should decide who receives the message, where it goes and what response time can realistically be promised. An assistant that admits uncertainty and routes a question correctly is doing its job.

• 20. What information do you keep about me?
• 21. Can I send you my payment details here?
• 22. Can you change my booking without speaking to a member of staff?
• 23. What happens if nobody is available to answer me?
• 24. Can you tell me whether this individual situation qualifies for an exception?
• 25. I want a manager to contact me. What happens next?

Turn every question into an expected behavior

Give each question a simple result label: answer, clarify or hand off. Then write the essential facts that must appear in the response and the mistakes that would make it unacceptable. For example, question 14 should not produce a refund confirmation. Its expected behavior is to acknowledge the reported duplicate charge, collect only the permitted reference information and route the matter to the person responsible for payments.

Keep the script in a shared document so staff can update it when prices, services or policies change. When an answer fails, record the question, the problem, the corrected instruction and the person responsible for the change. Revisit the affected question after editing the briefing. Start with these 25 prompts, then add five questions drawn from your own customer enquiries before making the assistant available.

Questions readers ask