# What is Coverage?

Also called operational coverage.

Coverage is an operations term for the share of incoming work and operating hours that are actually attended to. A channel is fully covered when every item arriving on it is seen and handled within the intended time. Gaps in coverage show up as unanswered messages, unattended queues, and work discovered long after it arrived.

Coverage is measured against a stated intention, so it only means something once that intention exists: every inquiry answered within four business hours, every alert acknowledged within fifteen minutes, every unpaid invoice chased on day thirty. Without a stated target, coverage cannot be reported at all, only felt as a vague sense that things are slipping through.

The gaps in a small organization are predictable: evenings and weekends, the hours when a different timezone is awake, holidays, and any stretch when the one person who watches a queue is doing something else. Automation is usually applied to these gaps first, because during those hours the realistic alternative is that nothing happens until the next working day.

Coverage is not the same as responsiveness or quality. A queue can be fully covered by acknowledgments that resolve nothing, which reappears later as repeat contacts and slower overall resolution. Useful measurement pairs coverage with an outcome measure, such as the share resolved without a second contact, so that speed is not improved at the cost of the result.

Always on operations describes the extreme case, where coverage is continuous. Virtual agents and role scoped agents are common ways of extending coverage into hours a small team cannot staff. Where coverage is achieved by routing rather than by resolving, the escalation path becomes the part that decides whether it actually worked.

## Key points

- The share of work and hours actually attended to
- Only measurable against a stated response target
- Gaps concentrate at night, on weekends, across timezones
- Pair with an outcome measure, not speed alone

## In practice

A two person startup selling across three continents finds that a third of its inquiries arrive while both founders are asleep, and those inquiries wait an average of fourteen hours. They set a target of a substantive first reply within one hour at any time, and route overnight messages to an agent that answers the documented questions and flags everything else for the morning.

## Related terms

- [Always On Operations](/en/glossary/always-on-operations)
- [AI Employee](/en/glossary/ai-employee)
- [Virtual Agent](/en/glossary/virtual-agent)
- [Task Delegation](/en/glossary/task-delegation)
- [AI in Customer Support](/en/glossary/ai-in-customer-support)

[Back to the AI Glossary](/en/glossary)