# Figma Community comments and support contact as trust surface

> Treat comments and support contact as part of the public product page, because Figma makes support details mandatory and leaves comment threads visible to every future buyer.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/figma-community-comments-and-support-contact-as-trust-surface/
- Source: [help.figma.com](https://help.figma.com/hc/en-us/articles/1500002628062-Comments-on-Community)
- GrowthDex source hub: [Figma Learn: Comments on Community](/sources/figma-learn-comments-on-community-help-figma-com/)
- Last checked: 2026-05-30T22:20:00Z
- Rarity: rare
- Budget: free
- Channels: Support, Brand, Marketplaces
- Stages: comment loops, support ops, trust building, public feedback


## Why this can grow

Public comments are not a nuisance to hide from. They are one of the clearest trust signals on a resource page. Figma requires support contact information when you publish, turns comments on by default, and notifies creators when feedback arrives. That creates a visible operating standard: people can see whether the creator answers real questions, fixes confusion, and stays present after launch. In crowded resource marketplaces, that can matter more than another design flourish.

## 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 figma community comments and support contact as trust surface can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Support and Brand channel.
3. Use the evidence from help.figma.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

Figma requires an email, website, or help center link as support contact when publishing, allows comments from Community members by default, and notifies creators about comments on their published resources.

## Adjacent tactics in the same lane

- [Chrome Web Store verified publisher URL and support hub](/growth-ideas/chrome-web-store-verified-publisher-url-and-support-hub/) - 3 shared channels
- [HubSpot marketplace support email and language before scale](/growth-ideas/hubspot-marketplace-support-email-and-language-before-scale/) - 3 shared channels
- [Help center custom domain before support links spread](/growth-ideas/help-center-custom-domain-before-support-links-spread/) - 2 shared channels, 1 shared stage
- [Slack Marketplace public support path with 2-day SLA](/growth-ideas/slack-marketplace-public-support-path-with-2-day-sla/) - 2 shared channels, 1 shared stage

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The Community page should teach the tool before the install](/blog/the-community-page-should-teach-the-tool-before-the-install/) - creator-led growth, marketplaces, brand trust

## Advisory

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