Overflow
Overflow is what happens when more conversations come in than the team can handle within its usual window. It is not a one-off failure: it is a state, and it usually lasts days, because what goes unanswered today piles on top of tomorrow.
What is overflow?
Overflow is what happens when more conversations come in than the team can handle within its usual window. It is not a one-off failure: it is a state, and it usually lasts days, because what goes unanswered today piles on top of tomorrow.
Also: volume spike · being swamped
Why it matters
What changes in a SaaS
Because it feeds itself. A customer with no reply writes again, and that second message takes the place of a new one. A swamped team generates part of its own volume, which is why getting out costs more than getting in.
Overflow in detail
The usual causes
A launch, an incident, a pricing change, a campaign bringing customers in all at once, and somebody going on holiday. Four of the five are foreseeable a week out, and support almost never gets told.
What to do once it is happening
Say so. An automatic notice acknowledging the situation and giving a realistic window cuts the follow-up messages, which are the part of the volume you can remove without resolving anything.
The lever before it happens
If overflow arrives with every launch, the problem is not capacity but coordination: support finds out once it is already live. An internal heads-up two days ahead and three articles written in advance change the outcome.
Questions about overflow
How do you know a team is swamped?
When the closed-over-opened ratio has been under one for days and the age of what is open is climbing. Response times say so later, once it has already accumulated.
Does hiring temporarily fix it?
It helps if the spike is documented work. If what is overflowing needs product knowledge, somebody new takes weeks to contribute and consumes the time of whoever is already there in the meantime.
Related terms
A term on its own is only half understood. These come up in the same conversation.
Ticket backlog
The backlog is the set of questions open and still unresolved at a given moment. More than its size, what gets watched is its trend: if more questions come in than get closed, the backlog grows, and it grows cumulatively even when the daily difference is small.
Contact rate
Contact rate is how many support questions a business generates relative to its size: normally tickets per customer per month, or per hundred active customers. It is the metric that says whether support will scale with the business or suffocate it.
Support queue
A queue is a set of conversations waiting to be handled by one specific group of people. Splitting the inbox into several queues — by channel, by language, by product or by customer type — is the usual way of dividing the work once a single list stops working.
SLA — Service level agreement
A service level agreement is the written commitment to respond within set deadlines. It fixes maximum times — usually first response and resolution — defines the hours in which they count, and normally states what happens when they are missed.
FRT — First response time
First response time is how long passes between a customer sending their question and receiving the first reply from a person. It measures the initial wait, not the resolution, and it is the metric that weighs most heavily on whether support feels good or not.
Ticket
A ticket is the record of a customer question inside a support tool. It groups every message in that conversation under one identifier and adds what is needed to manage it: status, owner, priority, tags and the history of what has happened.
