What was promised
Every reply and commitment on a case, in order, unchanged since it was sent.
A support case closes, then comes back as a dispute, a warranty claim or an auditor's question. Tabellix keeps the case, its attachments and every step taken by people and AI agents on a record that still verifies years later.
Most cases are never looked at again. The few that are decide disputes.
Every reply and commitment on a case, in order, unchanged since it was sent.
Every change to status, priority, owner or resolution, by whom, and why.
Which replies an agent drafted, what it changed, and where a person stepped in.
Whether a file a customer uploaded was checked before anyone on the team opened it.
Whether a customer's personal data can be erased while the case history stays intact.
A complete copy of the case for the customer, a partner or an auditor, that they can check themselves.
Each reply and status change is an event record, locked at capture and bound to the case. A correction is an amendment with a reason, and the original stays visible.
Every change is written to a hash-chained ledger in the same transaction as the change, so the history shows who did what and any later change is detectable.
Every tool call carries the person and the agent session. When an agent reads a customer's text its session trust drops and it may write less, and high-risk actions wait for a person to confirm out of band.
Every upload is scanned for malware and served only after the scanner answers clean. Downloads are served with active content blocked, and each is logged before the first byte.
Personal data about each customer sits under that customer's own key. Erasure destroys the key and keeps the case, its links and its history, and the audit trail still verifies.
A disclosure releases a case with its members as a signed bundle that verifies offline, and the accounting shows what each recipient received.
| Record | Kind | What it holds |
|---|---|---|
| Support case SC-88412 | case record | Status, priority, owner and resolution as its lifecycle; replies, attachments and approvals as ordered members; retention counted from closure. |
| Customer reply | event record | Author, channel, time and text, locked at capture. |
| Response target missed | event record | The target, the time it was missed and the case, sent by your platform through the API. |
| Escalation to engineering | case record | Linked to the support case; the fix, the verification and the sign-off as lifecycle steps. |
| Knowledge base article KB-0219 | document | Versioned, reviewed and released; a case links to the version it cited, and that link never moves. |
| Uploaded log file | document | Kept as its exact bytes, scanned before anyone opens it, its digest checked on every read. |
No. Your ticketing product keeps its queues, screens and automations. Tabellix is the record underneath: it receives cases and events through one contract and sends committed events back through signed webhooks that carry no content.
Only with the customer's approval. A support session is requested with a reason and a ticket, bounded in time, and approved by the customer's own approvers with a fresh sign-in. Support staff never read decrypted files, and every read lands on the customer's audit trail. It is off by default.
Your agent policy decides allow, confirm or deny for each action and each lifecycle event, so closing a case can wait for a person's confirmation. Under the flexible preset, an agent's signature always says it was the agent's.
As long as each case type requires. Retention is set per type, the longest period that applies wins, a hold for a dispute blocks disposition, and a person approves each disposal.
Tell us what you build and who audits it. We'll show you how Tabellix fits into your product and how it answers your auditors' most common questions.