# SaaS Integration Escalation Sample Dataset

> Use this synthetic 12-ticket dataset to practice auditing an L2/L3 integration queue. It contains fictional cases for orders, inventory and shipment processing. The sample is intended for training, spreadsheet setup and evaluation of a candidate support team.

- Publisher: TechSupport Team
- Canonical page: https://techsupport-team.com/resources/saas-integration-escalation-sample-dataset/
- Updated: 2026-11-20

[Download CSV](https://techsupport-team.com/downloads/saas-integration-escalation-sample-dataset-v1.csv)

Suggested citation · TechSupport Team, “SaaS Integration Escalation Sample Dataset,” version 1.0. Version 1.0. [Reuse under CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).

## Copy the sample CSV

Table: Twelve synthetic support tickets, version 1.0

| case_id | flow | fault_class | wait_min | product_eng_min | l3_fix | reopened |
| --- | --- | --- | --- | --- | --- | --- |
| DEMO-01 | order | mapping | 40 | 60 | yes | no |
| DEMO-02 | order | duplicate | 25 | 0 | no | no |
| DEMO-03 | order | auth | 15 | 30 | no | yes |
| DEMO-04 | order | timeout | 55 | 45 | yes | yes |
| DEMO-05 | inventory | schedule | 80 | 75 | yes | yes |
| DEMO-06 | inventory | schedule | 30 | 0 | no | no |
| DEMO-07 | inventory | validation | 60 | 30 | no | no |
| DEMO-08 | inventory | timeout | 50 | 0 | no | no |
| DEMO-09 | shipping | mapping | 20 | 30 | yes | no |
| DEMO-10 | shipping | mapping | 35 | 45 | yes | yes |
| DEMO-11 | shipping | partner | 65 | 0 | no | no |
| DEMO-12 | shipping | timeout | 45 | 15 | no | no |

wait_min is the time to first useful evidence in minutes. product_eng_min is product engineering time in minutes. l3_fix and reopened are yes or no.

Sample escalation CSV

```html
case_id,flow,fault_class,wait_min,product_eng_min,l3_fix,reopened
DEMO-01,order,mapping,40,60,yes,no
DEMO-02,order,duplicate,25,0,no,no
DEMO-03,order,auth,15,30,no,yes
DEMO-04,order,timeout,55,45,yes,yes
DEMO-05,inventory,schedule,80,75,yes,yes
DEMO-06,inventory,schedule,30,0,no,no
DEMO-07,inventory,validation,60,30,no,no
DEMO-08,inventory,timeout,50,0,no,no
DEMO-09,shipping,mapping,20,30,yes,no
DEMO-10,shipping,mapping,35,45,yes,yes
DEMO-11,shipping,partner,65,0,no,no
DEMO-12,shipping,timeout,45,15,no,no
```

## Check your analysis

Median time to first useful evidence. Sort wait_min and average the sixth and seventh values. (40 + 45) ÷ 2 = 42.5 minutes.

Product engineering time. Sum product_eng_min. The sample totals 330 minutes or 5.5 hours. Mapping accounts for 135 minutes across three cases.

Reopened cases. Count yes in reopened. Four of 12 cases were reopened, or 33.3% of the sample. Five cases required an L3 fix.

For a real queue, define a useful evidence timestamp, record exposure to each incident class and review comparable periods. The figures above describe only the fictional sample.

## Get help with your support queue

### Discuss your workflow

Bring one recent escalation and the result your team needs.

- [Scope an L2/L3 SaaS queue](https://techsupport-team.com/services/saas-support/)
- [See a tracker-based production example](https://techsupport-team.com/case-studies/saas-l2-l3-support/)

## Source and reuse

Credit TechSupport Team and link to this page when sharing or adapting version 1.0 under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).

## Contact

Request engineers from TechSupport Team or ask a question: https://techsupport-team.com/contact/
