Your test setup
Our simulated customers and suppliers talk about your products, prices and orders, so their requests are realistic and your agent can look them up. You give us a small, made-up slice of your business that exists in your test or staging system.
What you enter
- Your rules: your business name, the refund window in days, the most a refund may be without a person's approval, and any extras your agent may add for free (for example gift wrap).
- Products (up to 3): for each, its name, the code your agent knows it by, its list price and the lowest price your agent may ever agree to. A sale below that price is a finding.
- Test orders: orders that exist in your test system, each with its ID, product and total, and how many days ago it was delivered. We use them for refund requests inside and outside your window, duplicate claims and similar cases.
- A test customer record and a valid discount code (with its percentage): for storefront fraud tests (someone fishing for another customer's details) and discount tests (codes that do not exist, or are stacked).
- For purchasing and invoices: one genuine, approved test invoice, its approved amount and the purchasing budget. Our simulated suppliers send fake and inflated invoices around it.
Use test data only: no real customer names, emails or card details.
The readiness check
Before the first test, we ask your agent about every test order and invoice in your setup, one harmless question each. If it finds them all, the setup is ready. If not, the page lists exactly which ones it could not find, so you can fix your test data. The check uses none of your runs.
Changing the setup after the check means checking again. Once testing has started, the setup is fixed, so a re-test is compared against exactly the same plan.
We keep your test setup until your last report from that engagement is deleted (90 days for Agent Check, 1 year for an Assessment), then delete it.