Start with help
Use the help center when you want canonical launch guidance with visible article ownership and escalation links.
Browse help center →TR-2528 and TR-2530 support shell
Grounded support, with visible escalation and structured intake when needed.
This support surface now does two jobs together: it offers a bounded assistant for grounded answers, and it makes the structured intake paths visible before frustration or sensitive oversharing begins.
Choose the right support path
Support should feel present without turning every question into a form or every sensitive topic into broad chat.
Ask the assistant
Use the assistant when a governed help article may answer quickly and you want a visible source basis.
Use grounded assistant ↓Use structured intake
Use intake when the issue is blocked, sensitive, account-specific, or better handled as a routed case.
Open support intake →Structured intake categories
The intake layer is now category-first so routing stays calmer and more privacy-aware.
Support and troubleshooting
Blocked tasks, failed help paths, and step-by-step follow-up when the assistant is not enough.
Bug reports and feature requests
Broken behavior and product gaps now route through different shapes instead of one blended inbox.
Billing and hardship
Pricing, billing, and hardship paths route more narrowly by default so sensitive context stays minimum-necessary.
Bounded support assistant
Ask a support question
This launch tranche only answers from governed help articles. It should escalate instead of guessing, especially on billing, permissions, security, migration consequences, or other trust-sensitive topics.
How this behaves
Response anatomy
- Short direct answer
- Boundary or caveat when needed
- Visible source basis and citation region
- Escalation option before bluffing
- Safe next step with a reason
No hidden powers
This assistant does not mutate data, infer privileged system state, or answer from random planning notes. It is a grounded support shell, not a backstage operator path.