SupBot reads every customer conversation, knows your code and each customer's data, and answers, diagnoses or flags every request before your engineers have to.
"Every webhook from you has failed our signature check since about 08:40. We rotated the signing secret this morning."
312 deliveries to Northstar got 401 since 08:41webhooks/signer.ts:41 caches secrets for 24hHi Leo, we found it. After a secret rotation we kept signing with the previous secret for a while. We're clearing that now, and failed webhooks will be retried within the hour.
SupBot sits in your customer channels and decides, message by message, what needs doing.
Chit-chat and thanks are left alone. Questions, bugs and requests become cases, with the customer, IDs and history pulled in.
It searches your docs and code, checks that customer's records read-only, and works out the root cause with evidence.
Your team gets a ready reply to approve, edit or escalate. Nothing reaches a customer unless you allow it.
Other tools route the ticket. SupBot tells you why it broke: the likely cause, how confident it is, the evidence, and who's affected.
312 deliveries got 401 since 08:41webhooks/signer.ts:41 · commit a41c9e2Secret rotated at 08:38 UTCSupBot starts in Slack, where B2B customers already talk, and soon drops into your own product with an SDK. It reads the systems your engineers already use. Every connection is read-only, except draft PRs when you ask.
Each morning SupBot posts a summary to your team: who's waiting on you and for how long, drafts to approve, and what got resolved.
Northstar has waited longest, on failing webhooks. Two customers asked about CSV exports this week.
Waiting on you · 3 Northstar · Webhooks failing5h Kite · Bulk import timeouts2h Resolved since yesterday · 6Connect SupBot to your own Claude. Ask what needs approval, read a diagnosis, edit a reply and send it, without leaving the conversation.
Enforced in the product, not left to a prompt.
Code, logs and data are read-only. The one write is a draft PR, and SupBot never merges.
Every lookup is filtered to the customer in the conversation, by the tool itself.
Every workspace starts in Draft mode. Nothing goes to a customer without a person.
Below your confidence threshold, SupBot hands the case to your team instead of guessing.
Each tool call and query is recorded on the ticket. Secrets are redacted first.
Tokens and connection details are encrypted at rest, per workspace.
One plan for teams, with your own model key or ours. Enterprise when you need more.
Everything in SupBot, for your whole team.
For larger support teams with security and volume needs.
Using SupBot's model access? Here's roughly what a month costs. With your own key, you pay just the $20.
No. Access to your code and database is read-only. The only thing it can create is a draft pull request, when someone asks, and it never merges one.
Each conversation belongs to one customer, and every lookup is filtered to that customer by the tool before it runs. If SupBot can't tell who the customer is, customer data stays closed.
No. It reads every message but only acts when something needs doing. Thanks, chit-chat and your own team's messages are left alone.
Below the confidence threshold you set, it doesn't draft a reply. It flags the case for a person with what it found so far.
Slack today, including Slack Connect and internal support channels. Email, Telegram and a drop-in SDK for your own app are next, all landing in the same desk.
Connect Slack, point SupBot at your code, and see your first diagnosis in minutes.