01
Refusing is a feature
A bot that says “I don't know” and logs the question is more useful than one that invents a policy. We tuned for that on purpose, and we measure the refusal rate.
Company
Somewhere in your documentation sits the answer to the question a customer is about to ask. They will not find it, so they will email you instead, and you will answer it for the ninth time this week. ChatBrace exists to close that gap and to be honest about it when it cannot.
100 free messages · No card required
Six decisions that shape everything else. They are on this page so you can hold us to them.
01
A bot that says “I don't know” and logs the question is more useful than one that invents a policy. We tuned for that on purpose, and we measure the refusal rate.
02
Messages cost us money; rendering a design does not. So messages are metered and every one of the twenty-four designs is free on every plan, trial included.
03
Paid plans are never cut off for going over quota. A chatbot that goes silent during your busiest week costs you more than an overage line on an invoice.
04
The widget is 3.9kb gzipped against a 15kb budget our CI enforces. It loads on your site, so it behaves like a guest on someone else's page.
05
Every message records its tokens, cache hit rate, latency and exact cost. If we can see it, you can see it.
06
Every design discloses it before the conversation starts, and it cannot be switched off. That is an obligation, not a preference.
The model answers from the text you give it. Vague documentation produces vague answers, and out-of-date documentation produces confidently wrong ones. The unanswered-question log is there to make that visible quickly.
It will not read tone, spot an angry customer or make a judgement call on a refund. Give it the repeat questions and route the rest to a person — that is the split that actually works.