Support channels
Pick the channel that matches the urgency and shape of your question.
Community Slack
Real-time chat with the CHeKT team, partner engineers, and other developers. Usually the fastest way to get unblocked.
Best effort — most questions answered within an hour during US business hours.Join Slack →Email support
For account, billing, and longer-form technical questions. Available on Plus, Business, and Enterprise plans.
Response within 24h (Plus), 4h (Business), 1h (Enterprise).Email us →GitHub Discussions
Public Q&A and feature proposals. Searchable, indexed, and great for problems that may help other developers.
Maintainers respond within one business day.Open Discussions →Office hours
Weekly live video call with the CHeKT API team. Bring your code, ask anything, leave with a working integration.
Every Wednesday, 14:00 UTC. Free for all developers.See the schedule →Before you ask
We want to help fast, and these four things let us skip the back-and-forth.
- What you're trying to do
- One sentence describing the goal, not the symptom. "I'm building an AI verification app that…" beats "my code doesn't work".
- What you've already tried
- Saves us asking the obvious questions. Even "I haven't tried anything yet" is helpful.
- The request_id of the failing call
- Every API error includes one. We can trace exactly what happened in our logs from a single request_id.
- Relevant code or curl snippet
- With API keys redacted. The most useful 5 lines, not the whole repository.
Severity levels
For paid plans, we triage every issue against four severity levels. Mention the severity in your subject when you email — it sets the right escalation path.
Site monitoring is broken, alarms aren't reaching operators. We page on these 24×7.
Significant feature broken, customers affected, but operations continue. Business-hours pager.
Bug or unexpected behaviour that doesn't block monitoring. Same-day response.
"How do I…" or "Could you add…". Next-business-day response.