Reach the platform team through the support channel
If you want to ask about the product, report an issue, or discuss how the system is evolving, the support address is the cleanest current contact point.
Product questions
Ask about writer flows, public pages, shared company and project behavior, or the current platform direction.
Support
Report bugs, access issues, or confusing behavior in the portfolio and public-page flows.
Coordination
Use the contact channel if you need to discuss rollout, moderation, or future product packaging.
Best reasons to get in touch
The platform is still moving quickly, so concrete messages are more useful than generic outreach.
Access or onboarding
Questions about getting into the writer-side workspace or understanding the current entry points.
Public content issues
Problems with public pages, broken links, inaccurate context, or moderation-related concerns.
Product feedback
Feedback about the work, project, company, translation, or admin experience.
What helps most in a message
A little structure makes support faster and more accurate.
- Include the page or route where the issue happens.
- Describe what you expected and what happened instead.
- If relevant, mention whether the problem affects public pages, writer tools, or admin moderation.
Use the support address
That is the most reliable current contact path exposed by the app configuration.