OPERATOR SUPPORT
Bring the statement. Leave out the secrets.
For help with a failed audit, unexpected calculation, accessibility issue, or privacy question, email myke@n86.app.
Include
- The plugin tool you used: PDQ inspection, Toast inspection, statement audit, payout reconciliation, period comparison, channel comparison, or evidence-card rendering.
- The marketplace and a non-sensitive location label such as “Store 12.”
- The visible error message and the export's non-sensitive column headers.
- The expected result and the result you received.
Do not include
- Passwords, API keys, MFA codes, portal links containing tokens, or login credentials.
- Bank or card account numbers, routing numbers, tax IDs, or government identifiers.
- DoorDash Red Card exports, whole report ZIPs, card first-six or last-four, approval or network references, hashed consumer or loyalty IDs, delivery ZIP codes, or receipt barcodes.
- Guest names, emails, phone numbers, addresses, or order notes.
- Toast Tab Name or Tab Names columns; remove them before upload.
Response target
We aim to acknowledge support requests within two business days. A calculation correction will be documented plainly, including what changed and which result was affected.
Operator pilot
Restaurant operators and finance teams can request a free first-statement pilot review. The request form collects contact and business context only. It does not accept statement files or sensitive financial information.
How corrections improve the product
If you want an unexpected result to become a future regression test, say so explicitly. We will first reduce the case to a redacted source fingerprint, generic scope, normalized claim, your approve/correct/reject decision, and the evidence reference. A support email or raw file does not automatically train a model or change production logic.