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.
What is 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.
Also: contact volume · tickets per customer
The absolute number says nothing
Four hundred tickets a month is a figure without meaning: with forty customers it is an emergency and with four thousand it is an exceptionally clear product. Only relative to the customer count is it useful for deciding, and only the trend is useful for forecasting.
Why it matters
What changes in a SaaS
It is the only support metric that predicts the future. If volume per customer holds steady, support will grow at the pace of the business and you will keep hiring. If it falls, support stops being a proportional cost. If it rises, there is a product problem no support tool is going to fix.
Contact rate in detail
What drives it up
New features — each one multiplies the possible questions — interface changes with no warning, stale documentation, and customers from a new segment who use the product differently. All four are avoidable, and all four tend to surprise.
Segment it by plan
It is the most revealing cut. If the small plan generates three times more questions per customer than the large one and contributes half the revenue, you have a pricing problem dressed up as a support problem.
The relationship with cost
Contact rate times customer count times real cost per ticket gives total support cost. It is the sum you should be able to redo at any moment, and the one that turns an argument about impressions into a decision.
How Intake handles it
Questions about contact rate
How is contact rate calculated?
Tickets in the period over active customers in that period. It is usually expressed per customer per month, or per hundred customers when the number is small.
What does a rising contact rate mean?
That each customer asks more than before. It usually comes from new features, interface changes with no warning or stale documentation, and none of the three is fixed by growing the support team.
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.
Deflection rate
Deflection rate is the percentage of questions resolved without a person getting involved, either because the customer found the answer themselves or because an automated agent closed it. It is the metric used to justify any investment in self-service or in AI.
AHT — Average handle time
Average handle time is the time an agent actively spends on a question: reading it, finding the context, answering it and logging whatever needs logging. It excludes waits, which is why it is the metric that best approximates what a given support volume costs in hours.
Onboarding
Onboarding is the process that takes a customer from signing up to getting their first real result with the product. It covers the initial setup, the data import, training the team and everything else needed for usage to become routine.
MRR — Monthly recurring revenue
MRR is the sum of recurring revenue a subscription business bills each month, normalising annual contracts to their monthly equivalent. It excludes anything that does not repeat — implementations, consulting, one-off charges — because its job is to measure the stable base.
PMF — Product-market fit
Product-market fit is the point at which a product solves a problem well enough, for enough people, that growth stops depending on pushing. You recognise it because demand pulls the team along rather than the other way round.
