Help, from docs to a human
Most questions are already answered in the documentation. When they are not, a ticket reaches us — and a human takes over when the assistant cannot close the case.
Read the docsBefore you open a ticket
Three stops that resolve most cases faster than any ticket can.
1. Check the status
If something looks broken everywhere at once, look at the status board first — it is the first check, before a ticket.
2. Ask the docs assistant
The assistant on the Docs page answers from the documentation itself and points at the exact section.
3. Try troubleshooting
The troubleshooting hub covers the four problems builders meet most, each with its first fix.
How support works
One door, three steps. There is no general support inbox and no phone queue — tickets are the model, so nothing gets lost in an email thread.
-
Ask the assistant
Inside your account, the support assistant answers first, from the docs. Many cases end here, in seconds, at any hour.
-
Open a ticket
If the assistant cannot close it, your conversation becomes a ticket in the in-account portal — with the context already attached, so you never repeat yourself.
-
A human takes over
Tickets that need judgment — billing questions, account problems, platform bugs — are escalated to a person on an explicit path. You can always ask for the human.
What support covers
Published plainly, so you know where a question belongs before you ask it.
In scope
Billing and subscriptions. Account access and settings. Platform bugs — something in GateBuild itself misbehaving. Feature guidance: how a capability works and how to use it. The connectors we offer. GitHub sync.
Out of scope
Debugging the code inside an app you built. That is not a brush-off: the builder chat is the right tool for most of it, and for the rest the community and the partner directory are where app-level help lives. Support will point you to the right one rather than close the ticket cold.
Support by plan
The tier describes whose desk your ticket lands on. We do not publish response-time promises — a tier is a routing commitment, not a stopwatch.
| Plan | Support level | What that means |
|---|---|---|
| Free · Starter | Standard | Docs assistant first, ticket portal, human escalation on the standard path. |
| Builder · Pro | Standard | The same door, with full coverage of the plan's gated features — connectors, workflows, GitHub sync. |
| Elite | Premium | Tickets are routed ahead of the standard queue to the senior support desk. |
| Business · Enterprise | Priority | Priority routing plus a dedicated account team that knows your workspace. |
Status
The live state of this build's own surfaces. This board belongs to the internal test build — at public launch it becomes the platform status page.
Feedback & roadmap
At public launch, GateBuild's feedback board is public: anyone can submit a feature request, vote on what others have asked for, and follow the roadmap as items move from requested to planned to shipped.
Community channels
Where builders will talk to each other — and where app-level help lives alongside the community.
Discord
The community server: builder chat, app showcases and peer help. Opens at public launch.
The public subreddit for questions, builds and feedback. Opens at public launch.
Support questions
How do I reach a human?
Open support inside your account and ask. The assistant answers first; if it cannot close your case — or the moment you ask for a person — the conversation escalates to the human team as a ticket, with the context attached.
Why is debugging my app's code out of scope?
Because the people who can actually help are elsewhere: the builder chat understands your app's code and history, the community has builders who have hit the same wall, and partners do app-level work professionally. Support's job is the platform itself — accounts, billing, bugs in GateBuild, and how features work.
Do you publish support hours or response times?
No. The docs assistant answers at any hour; human tickets are handled by tier, and we would rather describe the routing honestly than print a response-time promise we have not staffed yet.
Something is down. Where do I look first?
The status board on this page. It is the first check before a ticket: if a surface is listed as degraded, we already know, and the board is where its state changes back.
Stuck less. Building more.
Docs for the answers, tickets for the rest — and a product that needs both less often than you'd think.
Start building