Reply #2 by backlinktalk
Editorial follow-up: test awkward inputs, not just neat examples
Try missing contact details, contradictory dates, a very long message, duplicated enquiries and text that tells the system to ignore its normal instructions. The output should preserve uncertainty and route the case for review where appropriate.
Use invented test data when real customer information is unnecessary. Record expected behaviour before running each case. A demonstration that works on three polished examples is different from a workflow that handles ordinary messiness. Include a failure path and manual fallback in the customer's acceptance review.