Illustrative
Sample package summary and field guide
Quick answer
A made-up company, Northwind Support Co., shows what a finished package summary looks like. Every number and name here is fictional.
Illustrative · fictional company
Package summary#
| Item | Value |
|---|---|
| Company | Northwind Support Co. (fictional) |
| Source system | Help desk |
| Records | 184,000 tickets, 1.1M replies |
| Date range | Jan 2019 – Dec 2024 |
| Language | English |
| Format | JSON lines, one ticket per line |
| Removed | Names, emails, phone numbers, addresses, account IDs, attachments |
| Company approval | Signed off by the operations lead before release |
Field guide#
| Field | Type | Meaning |
|---|---|---|
| ticket_id | text | Random ID, not the original |
| created_at | date | When the request came in |
| category | text | Topic, e.g. billing or shipping |
| messages | list | Customer and agent turns, personal details replaced |
| resolution | text | Solved, refunded, escalated or closed |
| time_to_resolve_h | number | Hours from first message to close |
| csat | number | Satisfaction score 1–5, if collected |
How to use this#
- Compare it with your own systems in the inventory builder.
- Your real package is prepared only after you qualify and approve.
- Fields vary by system and by what the buyer needs.
See if your company qualifies
A short company assessment. No data uploads are needed.