Contact support safely
Audience: a service owner or authorized delegate. Use the support path shown in Client Panel. For public contact options, use the 8Labs contact page. This guide does not promise a response time or change your service policy.
Check before reporting
Section titled “Check before reporting”- Check the status page for an active incident.
- Confirm the correct service account and workspace.
- Read the relevant troubleshooting task.
- Record the time, including your time zone.
- Describe the expected result and what happened instead.
Send the minimum useful evidence
Section titled “Send the minimum useful evidence”Include the affected service reference through the private support channel, the operation, and a redacted error. For connectivity, state whether SSH, RDP, and the browser console fail independently. For telemetry, state the selected range and whether the observation is stale or unknown. For payment, use the private invoice reference and confirmation time. Avoid a second payment while the first is investigated. For access, state the missing task and workspace; do not send an invitation link.
Never send these items
Section titled “Never send these items”Do not send guest passwords, private SSH keys, API bearer tokens, recovery codes, cookies, or console launch URLs. Do not publish raw network captures, browser storage exports, environment files, or entire unredacted logs. Screenshots can expose terminal output, IP addresses, email, billing details, and identifiers. Crop and replace sensitive details with opaque redaction before sharing. Blur alone is not reliable privacy protection.
If support requires a more detailed diagnostic, ask what it collects, where to send it, and how long it is retained. Do not execute an unverified privileged log collector because a public message requests it.
Escalation boundaries
Section titled “Escalation boundaries”Host outages, missing IP assignments, broker failures, and unavailable entitlements require operator investigation. Do not change production networking, force stop a server, reinstall, or pay again merely to gather evidence. If credentials were disclosed, revoke or rotate them through the appropriate account path and tell support privately.