# 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.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/cross-functional-support-sessions-before-roadmap-guessing/
- Source: [intercom.com](https://www.intercom.com/blog/customer-support-sessions/)
- GrowthDex source hub: [Intercom Blog: How customer support sessions help us stay close to our customers (even as we scale)](/sources/intercom-blog-how-customer-support-sessions-help-us-stay-close-to-our-cu/)
- Last checked: 2026-05-29
- Rarity: rare
- Budget: low
- Channels: Support, Product, Education
- Stages: voice of customer, support-led growth, roadmap quality, cross-functional ops


## Why this can grow

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.

## 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

1. Define one narrow startup segment where cross-functional support sessions before roadmap guessing can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Support and Product channel.
3. Use the evidence from intercom.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## 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.

## Adjacent tactics in the same lane

- [Weekly Slack theme digest from support threads](/growth-ideas/weekly-slack-theme-digest-from-support-threads/) - 2 shared channels, 2 shared stages
- [Staged rollout milestones in shared launch channel](/growth-ideas/staged-rollout-milestones-in-shared-launch-channel/) - 2 shared channels, 2 shared stages
- [Customer Advocacy design-brief pass before build](/growth-ideas/customer-advocacy-design-brief-pass-before-build/) - 2 shared channels, 2 shared stages
- [Automated support-friction categorization with trend dashboard](/growth-ideas/automated-support-friction-categorization-with-trend-dashboard/) - 2 shared channels, 2 shared stages

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The feedback queue should show what it heard](/blog/the-feedback-queue-should-show-what-it-heard/) - support-led growth, product operations, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.