Call center sample database for PostgreSQL
A ready-to-run PostgreSQL script with calls with queue, reason, wait and handle time, resolution and CSAT. Tested on PostgreSQL 15.18. Updated 19 November 2026.
Call center database for PostgreSQL
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).
This page has it as a PostgreSQL script: one table and 1,000 rows, with column types chosen for PostgreSQL, primary keys. The script drops the table if it exists, creates it and inserts the rows in one transaction, so you can run it again to reset the data. It is the same fictional data, seed 42, as on the call center dataset page, where it is also available as CSV and Excel.
We loaded this exact file into PostgreSQL 15.18 and ran every question below on it; the answers shown are that output. The same questions, written for SQLite, PostgreSQL, MySQL, SQL Server and DuckDB, return the same results on all five.
Load it
psql
createdb practice
psql -d practice -f call-center-postgresql.sqlpgAdmin or DBeaver
Create a database, open the Query Tool, open the .sql file and run it.
Tables and columns
call_center 1,000 rows
| Column | PostgreSQL type |
|---|---|
| call_id | VARCHAR(20) |
| date | DATE |
| time | VARCHAR(10) |
| agent | VARCHAR(30) |
| queue | VARCHAR(20) |
| reason | VARCHAR(20) |
| wait_seconds | INTEGER |
| handle_seconds | INTEGER |
| resolved | BOOLEAN |
| satisfaction | INTEGER |
Practice questions
answers from PostgreSQL 15.18
How many calls did each queue take, and what share was resolved?
SQL
SELECT queue, COUNT(*) AS calls,
ROUND(1.0 * 100 * SUM(CASE WHEN resolved THEN 1 ELSE 0 END) / NULLIF(COUNT(*), 0), 2) AS resolved_pct
FROM call_center
GROUP BY queue
ORDER BY calls DESC, queue;Yes/no columns are real BOOLEAN values, so they can be used directly in WHERE and CASE.
Result
| queue | calls | resolved_pct |
|---|---|---|
| Technical | 358 | 67.88 |
| Billing | 319 | 86.21 |
| Returns | 169 | 87.57 |
| Sales | 154 | 85.71 |
What are the average wait and handle times by queue, in seconds?
SQL
SELECT queue, ROUND(AVG(wait_seconds), 2) AS avg_wait, ROUND(AVG(handle_seconds), 2) AS avg_handle
FROM call_center
GROUP BY queue
ORDER BY avg_wait DESC, queue;AVG of an integer column returns a numeric, so no cast is needed.
Result
| queue | avg_wait | avg_handle |
|---|---|---|
| Technical | 112.80 | 525.53 |
| Returns | 103.25 | 322.46 |
| Billing | 100.77 | 337.89 |
| Sales | 100.70 | 340.27 |
How many calls arrive in each hour of the day? (time is stored as HH:MM text)
SQL
SELECT substr(time, 1, 2) AS hour, COUNT(*) AS calls
FROM call_center
GROUP BY substr(time, 1, 2)
ORDER BY hour;substr(text, start, length) cuts out part of a string.
Result
| hour | calls |
|---|---|
| 08 | 75 |
| 09 | 94 |
| 10 | 87 |
| 11 | 83 |
| 12 | 78 |
| 13 | 76 |
| 14 | 91 |
| 15 | 92 |
| 16 | 90 |
| 17 | 80 |
| 18 | 76 |
| 19 | 78 |
Which 5 agents have the highest average satisfaction (at least 20 calls)?
SQL
SELECT agent, COUNT(*) AS calls, ROUND(AVG(satisfaction), 2) AS avg_sat
FROM call_center
GROUP BY agent
HAVING COUNT(*) >= 20
ORDER BY avg_sat DESC, agent
LIMIT 5;LIMIT n at the end returns the first n rows.
Result
| agent | calls | avg_sat |
|---|---|---|
| Linda Clark | 48 | 4.10 |
| Daniel Roberts | 56 | 4.06 |
| Charles Bell | 30 | 4.00 |
| Mary Baker | 42 | 4.00 |
| Aisha Miller | 47 | 3.94 |
What are the top 5 call reasons?
SQL
SELECT reason, COUNT(*) AS calls
FROM call_center
GROUP BY reason
ORDER BY calls DESC, reason
LIMIT 5;LIMIT n at the end returns the first n rows.
Result
| reason | calls |
|---|---|
| Login problem | 97 |
| Refund request | 96 |
| Invoice question | 94 |
| Setup help | 91 |
| Bug report | 89 |
How many calls were there per month?
SQL
SELECT to_char(date, 'YYYY-MM') AS month, COUNT(*) AS calls
FROM call_center
GROUP BY to_char(date, 'YYYY-MM')
ORDER BY month;to_char(date, 'YYYY-MM') formats a date as year-month text.
Result
| month | calls |
|---|---|
| 2024-01 | 73 |
| 2024-02 | 89 |
| 2024-03 | 68 |
| 2024-04 | 88 |
| 2024-05 | 81 |
| 2024-06 | 75 |
| 2024-07 | 88 |
| 2024-08 | 94 |
| 2024-09 | 85 |
| 2024-10 | 78 |
| 2024-11 | 86 |
| 2024-12 | 95 |
PostgreSQL differences used here
- AVG of an integer column returns a numeric, so no cast is needed.
- Yes/no columns are real BOOLEAN values, so they can be used directly in WHERE and CASE.
- substr(text, start, length) cuts out part of a string.
- LIMIT n at the end returns the first n rows.
- to_char(date, 'YYYY-MM') formats a date as year-month text.