Bitaic Support
Use Bitaic Support when documentation, product troubleshooting, or account guidance does not resolve a monitoring, alerting, integration, billing, or access issue.
Start Here
Start with the path closest to the issue. If the issue remains unclear, send support the context needed to reproduce the path from configuration to alert state.
- Troubleshooting: triage monitoring failures, run diagnostic checks, verify alert delivery, and collect escalation details.
- Search: find products, commands, configuration fields, setup topics, and troubleshooting entries.
- Products: review the product page for the affected monitoring signal.
- Integrations: check alert routing through Slack, Microsoft Teams, email, PagerDuty preview, webhooks, and API keys.
Contact Support
Email support@bitaic.com with the affected workspace, product area, target name, alert state, last check time, and diagnostic output you collected. Use the subject to identify the impact level.
Escalation Levels
| Impact | Use when | What to include |
|---|---|---|
| Critical | Production monitoring is unavailable, a critical alert route is not reaching responders, or you suspect credential, token, or data exposure. | Severity, affected workspace, alert or request IDs, first observed time, recent changes, and mitigation already started. |
| High | A critical target has stale telemetry, incorrect state, repeated false critical alerts, or degraded alert delivery. | Product area, target, last healthy state, diagnostic command output, screenshots, and integration destination. |
| Normal | You need help with setup, configuration, account management, billing, product feedback, or docs feedback. | Workspace context, page URL or product area, expected behavior, current behavior, and relevant configuration without secrets. |
Service Status
Report suspected Bitaic service issues through support. Bitaic communicates service-impacting incident context through in-product notices or direct support replies when available; this docs site does not publish a separate status-page escalation path.
Feedback
Send docs corrections and product feedback to support@bitaic.com. Include the page URL, product area, expected behavior, current behavior, and a short description of the change that would help your team.
For active outages, safety issues, or suspected security incidents, start your organization's incident-response process first. If a Bitaic token, webhook secret, integration credential, or alert route may be affected, rotate or disable the affected item, preserve IDs and timestamps, then contact support with the escalation packet.