1. Best first channel
Use the in-app chat when it is available on the product or support page you are using. If you are reaching out about a legal, privacy, or formal policy matter, use the formal contact path on the relevant official page rather than placing sensitive details into a general support message.
For normal product support, keep the first message short and evidence-rich. Name the product, explain the expected result, show the actual result, and include screenshots or copied errors when they make the issue reproducible.
2. What support can help with
Support can help with access, account and pilot details, product selection, public release navigation, bug reports, public-page clarity, and general troubleshooting across the DeepBrainz product system.
3. What to include
Short, concrete requests are easier to triage than long stories without specifics.
- Product or page and exact URL
- Account email
- What you expected
- What happened instead
- Screenshot or copied error
- Whether this blocks urgent work
4. What not to include
Do not paste passwords, API keys, private credentials, or sensitive customer data into a support request unless the team gives you a secure path for it.