| Contact rate is the percentage of active users who contact support in a given period, calculated by dividing unique support inquiries by monthly active users (MAU). |
The term carries two meanings. In outbound sales, contact rate measures outreach attempts that reach a live prospect. This page covers the inbound support definition, used by app-first companies in gaming, fintech, and e-commerce.
Contact rate is the cleanest proxy available for product friction and support demand. When it rises unexpectedly, something broke in the product experience.
The Contact Rate Formula
Support contact rate formula:
| Contact Rate = (Unique Inquiries ÷ MAU) × 100 |
Unique Inquiries: the count of distinct users who submitted at least one support request in the period. Count users, not tickets. One user submitting three tickets counts as a single inquiry. Using total ticket volume inflates the rate and masks how broadly a problem affects your user base.
MAU: users who were active in your app during the same window, sourced from your product analytics tool.
MAU is the right denominator for app-first products. Total registered users and install counts include dormant accounts that never encountered the product, which dilutes the rate and makes real friction invisible. MAU keeps the denominator honest and ensures month-over-month comparisons hold up.
Example: An app with 50,000 MAU and 1,200 unique users contacting support in a month has a contact rate of 2.4%.
Outbound contact rate formula
Sales and SDR teams define it differently: Contact Rate = (Successful Contacts ÷ Outreach Attempts) × 100. This measures how often outbound calls or messages reach a live prospect. The rest of this page covers the inbound support definition only.
How to Calculate Contact Rate
- Choose a time window. Monthly is the standard. It aligns with MAU and provides enough volume to detect meaningful trends without the noise of shorter windows.
- Pull MAU from your product analytics tool. Match the period exactly to your support data window. Mismatched windows produce misleading rates.
- Pull the count of unique users who contacted support in that window. Not total tickets. This is a common mistake. Each user counts once, regardless of how many tickets they submitted.
- Apply the formula and track it as a trendline. A single reading tells you very little. Direction and velocity are what matter.
Contact rate is most useful as a directional metric over time, not a single absolute number.
How to Reduce Contact Rate
Four levers move contact rate down. In-app self-service (contextual FAQs and help articles surfaced inside the product at the right moment) removes the need to escalate before users ever reach an agent. AI deflection handles repetitive, high-volume query categories automatically and prevents them from reaching the queue. Proactive in-app messaging resolves friction at the moment it appears, before users file a ticket. And upstream product fixes, driven by ticket theme analysis, address root causes rather than symptoms.
Running all four in parallel compounds results faster than treating them as sequential projects. Each lever reduces contact volume independently; together, they address friction across every stage of the support funnel.
