Cross-functional support sessions before roadmap guessing
Put engineers, marketers, sales, and product managers into live support sessions so roadmap debates start with actual customer language instead of secondhand summaries.
Why this can grow a startup
The request list gets flatter every time it is translated. Intercom found that support sessions gave teams direct exposure to live customer questions, the business context behind feature asks, and the patterns that never make it cleanly into a spreadsheet. That matters because a roadmap argument changes when the engineer or marketer has heard the same confusion in a real conversation instead of only reading the sanitized request title later. It also tends to improve docs, onboarding, and handoffs because teams stop treating support as a separate department that merely forwards pain.
Source-backed example
Intercom runs regular support sessions where people from engineering, marketing, sales, and other teams answer live customer conversations with support guidance, and new starters are encouraged to do one within their first few weeks.
Source-reported evidence
Source: Intercom Blog: How customer support sessions help us stay close to our customers (even as we scale)
Intercom says new starters from IC to VP level are strongly encouraged to complete a support session within their first few weeks.
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 29, 2026
When to use it
Use this when Support, Product, Education is relevant to voice of customer, support-led growth, roadmap quality and you can run a bounded test with a low 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 Product, using evidence from Intercom Blog: How customer support sessions help us stay close to our customers (even as we scale) 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.