Public Support Growth Loop
Turn private support into a shared learning space that feeds content and product improvement.
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 6
- Confidence
- 99%
Replace isolated one-to-one support with a shared customer environment where questions, answers, and peer assistance remain visible. The shared space begins as a support channel rather than an artificially manufactured community, giving customers a concrete reason to join. Observe the questions and problems that appear there, support users directly, and transform recurring needs into educational content that attracts similar prospects. Feed the same evidence into product development so common friction is removed and successful workflows become easier. New content brings more users into the product, those users enter the community for support, and their experience generates the next round of content and product improvements. At greater scale, unify Slack, email, and conventional support tools behind one operational view while preserving the customer-facing community.
Origin
Clay shut down its early Intercom widget, directed customers into Slack for support, and developed a loop connecting content, community support, and product feedback.
Core principles
- 01Let customers learn from questions asked by other customers.
- 02Keep support conversations visible enough to create shared knowledge.
- 03Convert recurring questions into content and product improvements.
- 04Route demand, support, and development through one reinforcing loop.
- 05Add operational tooling as volume grows without destroying the community.
How to run it
- 1
Create a Shared Support Space
Establish a customer channel where appropriate questions and answers are visible to other users.
Pro tip Position it initially as the fastest place to get useful help, not as a vague networking community.
Watch out Keep private account, security, and billing matters in confidential channels.
- 2
Make Participation the Default
Direct early customers into the shared space when they need support so the channel reaches useful density.
Pro tip Provide clear onboarding instructions and response expectations.
Watch out Forcing participation without timely support creates resentment rather than community.
- 3
Support in Public
Answer questions clearly and encourage knowledgeable users to contribute where appropriate.
Pro tip Write answers so future readers can understand them without the original context.
Watch out Do not allow peer advice to substitute for authoritative help on risky issues.
- 4
Convert Questions Into Content
Identify repeated problems and turn their solutions into educational material that attracts similar prospects.
Pro tip Use the customer's own language in topics and headlines.
Watch out Do not expose identifiable customer details without permission.
- 5
Feed Friction Into Product
Translate repeated support problems into product fixes, onboarding improvements, and clearer defaults.
Pro tip Track frequency and severity so engineering receives prioritized evidence.
Watch out Do not treat documentation as a permanent substitute for fixing avoidable friction.
- 6
Unify at Scale
When volume grows, connect community, email, and support systems into one queue for the support team.
Pro tip Preserve the public learning surface even if agents work from a consolidated backend.
Watch out Operational scaling should not silently eliminate the peer visibility that powers the loop.
In the wild
Clay stopped using its in-app Intercom widget as the primary early support surface and required customers to join Slack for help. Questions became visible to other users, while the company used the resulting feedback to improve content and product. As the community grew, Clay restored additional support channels but routed them into one unified operational view.
→ The support channel developed into a large customer community while continuing to supply product and content feedback.
Common mistakes
Manufacturing Community Without Utility
A community needs an immediate functional reason to exist; support gave Clay's members that reason.
Keeping Insights Inside Support
The loop breaks if recurring questions never reach content creators or product builders.
Scaling Into Fragmented Queues
Adding email and Intercom without a unified operational view forces support staff to monitor disconnected systems.
Is it for you?
Best for
It is best for early self-serve products whose customers share workflows and can safely help one another.
Not ideal for
It is not ideal for sensitive, confidential, or account-specific support that should not appear in a public customer channel.
From the transcript
“So we shut down Intercom and we basically said, if you want to get help from us, you have to join our Slack.”
“But it's just like this feedback loop of building content that drives Top of Funnel, supporting the people who come through in this community, and…”
From the episode
$500M Founder Shares Unorthodox Growth Tactics (That Worked!)