Find the right place for your question.
Get to the right answer faster by starting in the right place. Use guides for learning, community for discussion, status for known issues, or email for private problems.
Community
Best for feature requests, public troubleshooting, and discussions other builders can learn from.
Direct support
Best for account, billing, organization, or private issues that shouldn't be shared publicly.
Where should this question go?
If you're learning the product, start with guides. If you want public discussion, go to the community. If the issue may be platform-wide, check status. If it's private, email support.
Start with guides if the question is about setup, concepts, or how Workunit works.
Use the community if public context will help other builders or shape the roadmap.
Check the status page first if the issue might affect many users or many workflows at once.
Email support when the problem needs private context, billing details, or direct intervention.
Most questions fall into four categories.
Use community for ideas and public bug reports, pricing for plan questions, status for known issues, and support email when the case needs private handling.
Post in the community to shape the roadmap and let others add context.
Use public reports when the issue is reproducible and doesn't involve private data.
Check pricing first, then email support if your question is unusual or account-specific.
Specific requests with links, steps, and expected behavior get resolved faster.
What makes a support request easy to act on
Before reaching out, check whether a guide or the status page already has your answer. If not, include the exact page, the expected behavior, and any useful workunit or project links.
The exact page or workflow
Tell us what you were trying to do, not just the symptom.
What happened instead
Include the message, broken step, or odd behavior you saw.
What you expected
That helps us tell whether something is broken or just unclear.
Useful links or IDs
Organization, project, workunit, task, or discussion links help us find the problem quickly.
Most common next steps
You can also jump directly to pricing, changelog, privacy, and terms depending on the answer you need.
Learn setup, workflows, and product concepts.
Check plan limits and upgrade paths before asking commercial questions.
Check whether the issue is already known.
See whether recent changes explain the behavior you're seeing.
Use the policy pages when the question is legal, privacy-related, or about data handling.
Two paths, one answer.
Email us when the issue is private, billing-related, or specific to your account. Use GitHub Discussions when the question is public or useful to other builders.