Answers first. A ticket when you need one.
Most answers live in the docs. When you need a human, file a ticket, keep the reference number, and we reply by email.
Self-serve
The docs cover the API, models, rate limits, and spend caps. The FAQ covers pricing and the product itself.
Read the docs → Common questions →File a ticket
Describe the problem, pick a severity, and get a reference number right away. A human reads every ticket.
File a ticket ↓Platform status
If something looks broken, check the live health endpoint first. It is the same check our own monitoring uses.
Check platform health →File a ticket.
Fill this in and your email app opens with everything structured and ready to send. Your reference number appears the moment you submit.
Ticket WEBEL-XXXXX
Your email app should have opened with the ticket below, already addressed to support@webel.ai. Send it and we are on it. If nothing opened, copy the text and email it yourself.
Nothing gets lost.
The reference number is the tracking key for your whole issue. It rides in the subject line so every reply stays in one place.
| Severity | Use it when | First response |
|---|---|---|
SEV1 | Production is down, or data is at risk. | Same business day |
SEV2 | A core feature is broken and there is no workaround. | One business day |
SEV3 | Everything else: questions, requests, small bugs. | Two business days |
First response is a reply from a person at support@webel.ai. The times above are targets in business days, Pacific time. Every ticket gets a reply, including the small ones.
New to Webel?
Most answers are a page away, and building starts in minutes.