Growth idea action plan
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.
Ian's take
From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.
Action plan
- Define one narrow startup segment where support funnel tried to resolve gap review can create a measurable lift.
- Turn the tactic into one offer, page, campaign, or workflow for the Support and Help Center channel.
- Use the evidence from intercom.com to set the first version of the message, format, and audience.
- Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
- Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.
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: Intercom Help: Conversational support report (intercom.com)
GrowthDex source hub: Intercom Help: Conversational support report
Last checked: 2026-05-30
Adjacent tactics in the same lane
If this page is close to your problem, these tactic pages usually belong in the same working set.
- Retroactive proactive message tagging for support analysis same source · 1 shared channel
- Ticket-to-search ratio as self-serve failure signal 2 shared channels · 1 shared stage
- Subject-field article suggestions before ticket submit 2 shared channels · 1 shared stage
- Generative answer box with click-through sources 2 shared channels · 1 shared stage
Related GrowthDex essays
- Support starts paying off before the ticket exists support, activation, brand trust
Read GrowthDex essays
The Blog turns real growth tactics into plain-English case studies by niche, channel, and buying situation.
Why this is worth your time
GrowthDex starts with tactics that founders, marketers, and product teams have actually tried. Each essay turns the evidence into a practical move you can test without pretending one case study is a guarantee.
Ian Goh has helped grow consumer platforms across Southeast Asia, India, and MENA. His work includes scaling Tiki to 100M+ users, doubling BIGO's MENA revenue in 7 months, and increasing OYO's direct booking share across 6 Southeast Asian markets.
- Helped scale Tiki to 100M+ users.
- Doubled BIGO's MENA revenue in 7 months.
- Raised OYO's direct booking share by 50% across 6 Southeast Asian markets.
Want help turning this into a growth system?
If you want someone to pressure-test this against your real market, Ian works with founders on growth, market entry, and operator-led distribution.
Work with Ian on growth advisory