Support & Contact
We are happy to help. Most questions have a quick answer in the docs, and for everything else you can reach the TechForcz team directly.
Before you reach out
A lot of common issues are already covered, and self-service is usually the fastest path:
- Start with the Troubleshooting section. It walks you through isolating a fault to the right tier before you dig in.
- Check the FAQ for short answers to the questions we hear most often.
How to contact us
Email us at info@techforcz.com and we will take it from there.
What to include
The more context you give us up front, the faster we can help. Please include:
- A clear description of the symptom, what you expected versus what you saw.
- The time it occurred, with your time zone.
- The affected collector or the Ozone Orchestrator route where you saw the problem.
- Any error id shown in the console.
Never paste full tokens, passwords, or secrets into a support request. An error id or a redacted snippet is enough for us to trace it.
Severity expectations
When you open a request, let us know how it is affecting you. We use these levels to prioritize:
| Severity | What it means |
|---|---|
| Critical | Production monitoring is down. No telemetry is reaching the Ozone Orchestrator. |
| High | Monitoring is degraded. Partial data loss, or a core feature is not working as expected. |
| Normal | A general question, a minor issue, or a request that is not blocking your work. |
We triage in priority order and confirm receipt so you always know your request landed. Specific response and resolution times, where they apply, are set out in your service agreement.