311 Toronto Contact Centre: Operations BI
Channel shift, service level, follow-up demand, intraday demand, a 12-month call-volume forecast and an Erlang C staffing model for a contact centre handling about 1.3 million contacts a year, built end to end from public data.
What the data says
Four findings and the operating decision each one points to.
Channel shift
Digital channels are taking share from the phone queue. Self-service (web and mobile) has more than doubled its share since 2022.
Contacts per month, by channel group
View as table
Share of contacts, by channel group
View as table
Service and follow-up demand
The phone queue has met its 80/75 target three years running, but the margin is thin. Follow-up "where is my request?" contacts peak every summer.
Phone service level vs. target
View as table
Follow-up contact rate
View as table
Forecast and staffing
A damped Holt-Winters model forecasts monthly phone volume 12 months out. It feeds an Erlang C model that sizes the peak-hour team needed to hold 80/75.
Phone contacts per month: actual and 12-month forecast
View as table
Staffing what-if (Erlang C)
When and why people contact 311
Demand is a weekday, business-hours pattern. Billing questions lead the general inquiries, which makes them the clearest self-service opportunity.
Average service requests per hour, by weekday and hour
View as table
Top general inquiries
View as table
Top service-request types, last 12 months
View as table
Data governance
Every KPI above has a written definition, and every load runs automated quality checks. The raw service-request CSV is unquoted, so about 35,000 rows a year split on a comma inside a division name; the pipeline detects and repairs them, and logs every rejected row.