Support - OneShot

Channels

Channel	Use it for
[email protected]	Service issues and account questions. Include the request, job, receipt or goal ids involved.
[email protected]	Vulnerability reports, security questions and agreement requests.
Community chat	Questions and discussion with other builders. Not a staffed queue.

An organization can also raise a request from the console’s Support page with a severity and the ids involved, follow its status and read support’s replies there. The console shows the escalation contacts and support terms from the organization’s signed contract when it has one.

Severity levels

Severity describes observed customer impact. Reassess it as evidence changes. These definitions set no response clock.

Level	Definition	Example
S1	Payments broadly fail or every paid call fails, blocking paid use.	Payment settlement fails across otherwise valid paid requests, or all paid tool submissions fail.
S2	One tool family is unavailable while other families remain usable.	All browser jobs fail while research and messaging continue to work.
S3	One tool is degraded or slow with narrower impact.	Person profile enrichment accepts jobs but finishes slowly while other enrichment tools work.
S4	A question or guidance request without an observed service failure.	A developer asks how to recover a request using its idempotency key.

What to include

The ids involved, the environment, what you observed and when (in UTC), and what you expected. Keep credentials, payment authorizations and customer payloads out of the request.