Overflow and backlog
The backlog is what is pending.
Overflow is the state in which the team cannot handle what comes in within its usual time. A large, stable backlog is not overflow. One that grows every day is.
Why it matters
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.
Signs of overflow
They appear in this order, and the first ones give days of warning.
- The closure ratio has been below one for days.
- First response time rises with no change in the team.
- More second messages arrive from customers asking whether anyone has read them.
- Committed deadlines are missed.
- The hard conversations are left unpicked.
The usual causes
A launch, an incident, a pricing change, a campaign bringing customers in all at once, and somebody going on vacation.
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.
What you can do beforehand
If overflow arrives with every launch, the problem is coordination more than capacity.
Support finds out once it is already live. An internal heads-up two days ahead and three articles written in advance change the outcome.
