Support

Use Operade support when documented recovery does not resolve a reproducible product problem, when workspace activation is required, or when a public capability does not match its documented behavior.

Contact options#

Use the contact form or write to sales@operade.com. These are the only support routes published in Documentation V1. The documentation does not state a guaranteed response time, support tier, phone number, or separate help center.

Before contacting support#

Retry only the safe recovery described by the relevant troubleshooting guide. Collect the UTC time, public error code, HTTP status, request path or dashboard area, workspace identifier, and safe resource identifiers. State what you expected, what occurred, and whether the result is consistent in a fresh Test Chat or request.

For an API issue, include the HTTP method, path template, credential type, and content type. For an agent-runtime issue, include the Agent, Branch, Version or draft context, Conversation identifier, and last visible Activity type. For Telegram, include the channel and update identifiers but not provider credentials.

Information to remove#

Never send API keys, session cookies, Telegram bot tokens, webhook signing secrets, named Secret values, raw Authorization headers, or URLs containing credentials. Remove customer messages, prompts, Knowledge content, and Tool payloads unless an approved support reply explicitly requests a narrowly scoped example.

Use placeholders such as YOUR_API_KEY when showing a request shape. A screenshot should be checked for browser cookies, query values, workspace member email addresses, and confidential conversation content before it is shared.

What happens next#

Support may ask for one smaller reproduction, a safe identifier, or confirmation that the issue still occurs after refreshing state. Do not delete a Draft, revoke a working credential, recreate a channel, or change production traffic merely to make a report smaller unless that action is already the documented recovery.

Start with Errors and recovery for API and concurrency failures, Monitor troubleshooting for conversation behavior, or Authentication troubleshooting for credential failures.