Why our AI rep never guesses an order number

An order holds a name, a delivery address and a list of what someone bought. Sharing any of that with the wrong person is a privacy problem for your customer and a trust problem for your store. An AI rep needs a clear rule for when it may look an order up, and Merrows has one.

A Merrows rep needs one of two things before it looks anything up: the order number, or the email address on the order. If the customer has given neither, the rep asks.

A message that only mentions an order, such as "look up an order", is not treated as an order number. The check runs on what the customer actually wrote or said, so the rep never acts on a number it was not given.

A customer who opens with "where is my order" hears one quick question back: the order number or the email used at checkout. Once the rep has it, it finds the order in your store and reads back the status, the tracking and the expected delivery date.

If nothing matches, the rep says so and asks the customer to check the details, or passes them to your team with the conversation attached.

A rep that picks the most likely order to save a question could read one customer the details of another. A rep that reports a delivery date it did not fetch tells your customer something your store cannot stand behind. One short question avoids both, and customers expect it: it is the same check a good support agent makes.

A Merrows rep follows the Playbook your business wrote. Where a step needs a fact, the step asks for it, and the rep never fills a gap with a plausible value. The check is on for every store using Merrows, on every channel, with nothing to switch on.