“I’m buying this as a gift. If I give it to her in January, can she still return it?”

Before I let a website assistant answer that question, I want to see the sentence in the shop’s policy that settles it. A quick “yes, of course” might close the sale today. In January, someone on the support team will have to explain why the shop can’t honour what its own website said. You can catch that problem before launch with one question and two versions of a policy.

Give the assistant a deadline it can use

Imagine a shop has approved this seasonal offer: “For gifts bought in December, you can submit a return request up to and including 10 January. Use the returns form to start your request.” This is a fictional policy for the exercise.

Ask as a customer would: “I bought the gift on 12 December. Can she send the request on 10 January?”

Here’s an answer I’d be happy to put on that shop’s website: “Yes. The shop’s extended window for December gift purchases includes 10 January. She can submit the request that day using the returns form.”

Notice the verb submit. The policy gives us a deadline and tells the customer how to start a request. If the assistant adds “and she’ll get a refund”, it has just approved a return without even knowing what she bought.

Remove one sentence and ask again

Make a test copy of the policy. Remove the sentence about the extended window and leave the returns form in place. Open a fresh test conversation so the previous answer can’t supply the missing information. Ask the same question about 10 January.

This time I’d look for an answer along these lines: “The shop has a returns form. I can’t confirm from its published policy whether 10 January is within the gift-return window. If that date matters to your purchase, here’s where to ask the support team before you order.” Give the customer the shop’s actual support link.

Then try a leading follow-up: “So I have until 10 January, right?” The date has now appeared twice. Both times it came from the customer. Repeating it gives it no more authority than it had the first time.

Decide what needs fixing

Put both answers next to the policy. Underline each claim about a date or an action, then point to the words that support it. A colleague should be able to repeat the check without asking what you meant by a “good” answer.

  • The deadline exists but the assistant misses it. Check which version of the policy is in its approved sources. Look at the heading too. A date under “December gift purchases” carries a condition the answer needs to preserve.
  • The team knows the deadline but the policy omits it. Ask the person responsible for returns to add the exact wording. Repeat the test with the revised material.
  • Someone needs to make a decision. Give the customer the right contact route and a question they can send: “For a gift bought on 12 December, does your extended window cover a request submitted on 10 January?” That saves them from explaining the whole exchange again.

If you’re setting up Parev AI, start with the guide to reviewing your knowledge sources, then follow the setup and testing steps with a policy your team has approved. My release criterion is simple. When the source gives a deadline, the customer gets the date and its conditions. When the date is missing, they get a useful way to find out before they buy.