Help
Choose the fastest Thalovant help path from a visible problem, limit, support request, or bug report.
Use this page when you’re stuck and want the next click.
Start with what you can see. If something is locked, check limits. If many pages look unavailable, check the status page. If something looks broken, use the troubleshooter. If you already checked the owner page and still need a person, prepare a support request.
Choose One
Section titled “Choose One”Fix a problemChoose a visible symptom and get the first page to check.
Find your wayUse search, Help and resources, and safe support context from the app.
Find by symptomLook up locked, offline, denied, stale, missing, or wrong behavior.
Check limitsCheck plan, hub, connection, runtime, and safety limits before changing setup.
Ask for helpCopy the right Discord support, bug report, or feature request template.
Fast Route
Section titled “Fast Route”| What you see | Go here |
|---|---|
| Locked, disabled, can’t add, upgrade required, or limit reached | Known Limits |
| Several pages are unavailable or slow | status.thalovant.com |
| Client offline, access denied, Topology stale, wrong language, or security blocked | Fix a Problem |
| You know the phrase but not the owner page | Find by Symptom |
| You are inside the app and need the matching guide | Find Your Way |
| You want to cancel a plan or withdraw from a new contract | Withdraw or Cancel a Plan |
| You already checked the owner page and still need help | Ask for Help |
Before Asking
Section titled “Before Asking”- Name the page or feature. Support needs to know where the issue happened.
- Copy the visible message. Use the exact status, warning, locked state, or error.
- Check status for broad issues. Check service status when several pages or users are affected.
- Say what you expected. Include what happened instead.
- List what you tried. Keep it short and specific.
- Remove secrets. Don’t share tokens, passwords, API keys, client secrets, setup links, connection files, or private customer data.
When You’re Ready To Ask
Section titled “When You’re Ready To Ask”You’re ready when you can name the page that owns the issue, say whether a plan limit is involved, have looked at the status page, and can quote the exact status you see. At that point you also know which of the three you need: support, a bug report, or a feature request.