Support funnel Tried to Resolve gap review
Review the gap between 'Tried to Resolve' and 'Resolved' every week so self-serve content is judged by whether it actually prevents the human handoff.
Why this can grow a startup
A help center can look busy and still be failing. The useful question is not whether people searched or opened an article. It is whether they stayed out of the queue after trying. Intercom's Conversational Support report makes that visible by splitting people who attempted self-serve from those who actually resolved inside the same 24-hour support session. That gives support, product, and content teams a cleaner place to work than raw article views or ticket totals.
Source-backed example
Intercom's report separates customers who 'Tried to Resolve' with self-serve support from those who were actually 'Resolved' within the 24-hour session and shows when the same session still needed human support.
Source-reported evidence
Source: Intercom Help: Conversational support report
Intercom defines a support session as a 24-hour period and counts self-serve resolution when the customer does not start a conversation within that session.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
Source discovered: May 30, 2026
When to use it
Use this when Support, Help Center, Analytics is relevant to self-serve support, reporting, deflection and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Support and Help Center, using evidence from Intercom Help: Conversational support report as context—not as a promised result.
- Record a baseline for: Users who resolve the issue and complete the next useful action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.