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.
Why this can grow a startup
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.
Company 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.
Source and metric
Source: Figma Learn: Comments on Community
Comments are turned on by default for Community files, plugins, and widgets, and can be changed any time during publishing or updates.
When to use it
Use this when Support, Brand, Marketplaces is relevant to comment loops, support ops, trust building and you can run a bounded test with a free 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.
Founder checklist
- Read Figma Learn: Comments on Community and identify what is directly supported.
- Choose one channel context: Support, Brand, Marketplaces.
- Define the test around Comments are turned on by default for Community files, plugins, and widgets, and can be changed any time during publishing or updates..
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Build creator and community systems around real incentives, trust, and repeat participation.