Support
Email support@steel.dev about your account or billing, and ask code questions in #help on Discord. Scale and Enterprise add a dedicated Slack channel, and Enterprise also adds a 911 email for urgent production incidents. Send the session ID and the full error with each question, so that Steel can reproduce the problem. The support that each plan includes is also on Pricing.
Channels
| Channel | Where | Plans | Use it for |
|---|---|---|---|
| Email support | support@steel.dev | All plans | Account and billing questions, a suspended account, and problems that need private details |
| Community | The #help channel on Discord | All plans | Public questions about code and integrations |
| GitHub | The project's repository on github.com/steel-dev | All plans | Bugs in Steel Browser, the SDKs and other open-source projects |
| Dedicated Slack channel | A Slack channel for your organization | Scale, Enterprise | Questions from your team to Steel |
| 911 email | An email address for your organization | Enterprise | Urgent production incidents |
| Sales | Contact sales | All plans | Enterprise, custom limits and reserve browser pools |
| Privacy | compliance@nenlabs.xyz | All plans | Requests about your personal data |
Enterprise also includes support and uptime SLAs, set in your contract. The status of Steel's services is at status.steel.dev.
Get your Slack channel and 911 email
When your organization starts a paid Scale plan, Steel creates a Slack channel for your team and the Steel team. The person who upgraded the plan gets two messages at their email address:
- An email with the subject "Welcome to Steel Scale", which names the channel.
- A Slack Connect invitation to the channel. Accept it to join.
If the invitation does not arrive, reply to the welcome email. If your team is on Scale and has no channel, write to support@steel.dev.
On Enterprise, the Slack channel and 911 email address come with your contract. To get them, contact sales.
What to include
Send these details with each question. They let Steel find your session and reproduce the problem:
- The session ID, which is the session's
id, a UUID. Send one ID for each failed session. - The time of the failure, in UTC.
- The full error: the whole response body with its
error,codeandmessage, or the full message and stack trace from your library. - The options that you passed to create the session, such as
useProxy,timeoutorsolveCaptcha. - The Steel SDK or library that you use and its version, and whether you use Steel Cloud or self-host Steel Browser.
- What the session should have done, and the fewest steps that reproduce the failure.
Debug a failed session shows how to find the failing step first.