Sample call center data
1,000 × 10rows × columns in the 1,000-row file
Updated 3 November 2026. Fictional U.S. businesses and people, generated with a fixed seed.
textnumberdateyes/no
Largest file10,000rows; also 100 and 1,000
Columns10with a data dictionary below
Dates2024-01-01 – 2024-12-31range in the file
LicenceCC0synthetic, free for any use
What is in it
Each row is one inbound call in 2024: date and time, agent, queue, reason, seconds on hold, handle time, whether it was resolved and the 1-5 survey score (blank when the caller skipped the survey).
First rows
point at a column to light it up
| call_idtext | datedate | timetext | agenttext | queuetext | reasontext | wait_secondsnumber | handle_secondsnumber | resolvedyes/no | satisfactionnumber |
|---|---|---|---|---|---|---|---|---|---|
| CL-300001 | 2024-02-11 | 19:18 | Nicholas Sanchez | Returns | Damaged item | 13 | 491 | TRUE | 3 |
| CL-300002 | 2024-07-25 | 14:00 | Anthony Rodriguez | Returns | Return label | 118 | 500 | TRUE | 4 |
| CL-300003 | 2024-12-23 | 10:16 | Aisha Miller | Billing | Refund request | 70 | 628 | TRUE | |
| CL-300004 | 2024-09-26 | 18:21 | Nancy Thompson | Sales | Upgrade | 72 | 208 | TRUE | 4 |
| CL-300005 | 2024-12-15 | 19:00 | Linda Martin | Technical | Login problem | 61 | 650 | TRUE | 3 |
| CL-300006 | 2024-01-29 | 19:49 | Nancy Thompson | Billing | Plan change | 160 | 644 | TRUE | 5 |
| CL-300007 | 2024-05-01 | 12:24 | Nancy Thompson | Sales | Upgrade | 1 | 364 | FALSE | |
| CL-300008 | 2024-04-02 | 15:09 | Daniel Roberts | Technical | Bug report | 48 | 417 | TRUE | 4 |
| CL-300009 | 2024-06-13 | 16:00 | Nicholas Sanchez | Sales | New account | 197 | 607 | TRUE | 4 |
| CL-300010 | 2024-12-21 | 15:43 | Joseph Johnson | Technical | Login problem | 100 | 344 | TRUE | 5 |
Average wait by queue
seconds, 1,000-row file
Show as a table
| queue | value |
|---|---|
| Technical | 112.8 |
| Returns | 103.3 |
| Billing | 100.8 |
| Sales | 100.7 |
Data dictionary
| Column | Type | Meaning |
|---|---|---|
| call_id | text | Call number |
| date | date | Call date (2024) |
| time | text | Start time, 24-hour HH:MM |
| agent | text | Fictional agent name |
| queue | text | Billing, Technical, Sales or Returns |
| reason | text | Reason code within the queue |
| wait_seconds | integer | Seconds on hold before an agent answered |
| handle_seconds | integer | Talk + after-call work, seconds |
| resolved | boolean | Resolved on this call |
| satisfaction | integer | Post-call survey 1-5 (blank if no answer) |
Practice questions
answers checked in SQL and in Python
Average wait (seconds) and resolution rate by queue?
Billing 100.8 s, 86.2% resolved; Returns 103.3 s, 87.6% resolved; Sales 100.7 s, 85.7% resolved; Technical 112.8 s, 67.9% resolved
SQL
SELECT queue, ROUND(AVG(wait_seconds),1), ROUND(100.0*SUM(resolved)/COUNT(*),1) FROM call_center GROUP BY queue ORDER BY queueFile: call-center-1000
Average satisfaction for resolved vs unresolved calls (survey answers only)?
not resolved 2.57; resolved 4.10
Excel
=AVERAGEIFS(J:J,I:I,TRUE) (AVERAGEIFS skips blank survey cells)SQL
SELECT resolved, ROUND(AVG(satisfaction),2) FROM call_center WHERE satisfaction IS NOT NULL GROUP BY resolved ORDER BY resolvedFile: call-center-1000