Teams that conduct extensive testing in production have no way to mark submissions as tests, which means test bookings pollute rep calendars, skew distribution counts, and inflate reporting metrics. There is also no API-level mechanism to run end-to-end tests through live routers without creating real calendar events, forcing developers to either test in a degraded environment or accept that test data will contaminate production data.

Chili Piper should support a test mode for submissions, either via a UI flag or an API parameter such as a nobooking boolean, that executes the full routing flow and returns a successful response without creating a calendar event or writing data to reporting. Test submissions should be clearly distinguishable from real ones and excluded from all metrics, distribution counts, and activity logs.

Without this, teams doing legitimate QA and integration testing in production either have to live with dirty data or constantly clean it up manually. A test mode is a standard capability for any platform being used in complex enterprise stacks where end-to-end testing is a regular requirement.