You own a number, not just an inbox
Somebody asks you what support costs, or why churn moved. You need figures you can defend line by line, not a blended rate a vendor defined.
Three setup steps, an afternoon at most, and nothing to integrate. This page is the detail: what you actually do, what happens afterwards, and who the product is wrong for.
200 messages free, no card, and a hard cap rather than a surprise charge.
Before you spend an afternoon
It suits a particular kind of team, and saying which one is cheaper for both of us than finding out in week three.
Somebody asks you what support costs, or why churn moved. You need figures you can defend line by line, not a blended rate a vendor defined.
The agent answers by quoting your own documents. If your answers exist anywhere in writing, it has something to work from — and it can draft articles from your website to start you off.
Opening hours, delivery, refunds, how to change a detail on an account. Repeat questions are the volume an agent actually removes.
This product's defaults are cautious: it hands over rather than guesses, and declines rather than invents. If you would rather be fast than right, it will frustrate you.
Two minutes
There is no card and no password. You give a company name and an email address, we send a one-time link, and you are in. The trial is 200 messages and a hard cap — when it runs out the agent stops and says so. It cannot become a charge you did not choose.
Nothing is billed until you pick a plan yourself, from inside the account. The cheapest is $49 a month for 2,000 messages, with overage in blocks of 1,000.
What the plans includeThat is the whole form. No card, no password to choose and later forget.
One-time and short-lived. If it does not arrive, check the address — a link is only sent to an address that has an account, and the page says the same thing either way so that nobody can use it to find out who has one.
Three steps, tracked, with the next one always shown down the left.
Your first hour
These are the same three steps the account itself tracks, in the same order. Do them in order: the first one proves the account works before you spend time on the other two.
Add your website's address and copy one line of code onto it. No integration project and no engineering quarter — it is a script tag and a list of the origins allowed to use your key.
In the account: Install the chat · about five minutes. If the chat does not appear, it is almost always the origin list rather than the tag.
Hours, prices, where you are, what you do not do. It answers from this. Point it at your website and it will read it and fill in what it can find, then wait for you to say yes to each box — nothing is used until you approve it.
In the account: Business profile · ten minutes, less if it reads your site. The boxes you leave empty are the questions it will hand to you.
It drafts help articles from your own website and you approve the ones that are right. Every answer it later gives cites one of these documents and the revision it came from.
In the account: Help articles · half an hour to start, ongoing after. Approve a few good articles rather than many rough ones. It quotes what you give it.
Your first week
Setup is the short part. The week after is where a support agent either earns its place or quietly becomes a worse contact form.
Those are people who asked and left with nothing. Each one is either a missing article or an article that does not say what people think it says. It is the shortest route to a better number.
Flagged on purpose, because an answer with no document behind it is the one most likely to be wrong. Either write the article or tighten the profile so the question gets handed over instead.
A handover is not a failure — it is the correct outcome for anything touching an account or a payment. But a repeated handover on the same question usually means one article would remove it for good.
You will have a real message count by now. Put it into the calculator rather than guessing from the pricing page.
Worked examples, not customers
Support Proof has no customers to quote yet, so there are none quoted here. What follows is arithmetic: three situations with figures that add up, which you can redo with your own numbers. When there is a real account willing to be written up, it will replace this and say whose it is.
A shop with a help centre and the usual mix of questions.
| 612 | answered from your own articles, each citing the document and revision |
| 383 | handed to your team — account changes, refunds outside policy, anything it could not source |
| 142 | abandoned: asked, got nothing useful, left. The number most tools fold into “resolved” |
| 63 | declined, because the answer would have been outside the policy you wrote |
1,200 in total. The 142 is the list worth reading first: those are people who arrived with a question and left without an answer.
The publish gate, doing the thing it exists for.
| 18 | questions that article used to answer are re-asked against the new text |
| 17 | still have an answer |
| 1 | does not — “how long do I have on an annual plan?” lost its paragraph |
| 0 | customers find out, because the publish is blocked and the editor is told which question broke |
Without the gate this surfaces weeks later as people asking the same question and leaving.
“Can you waive my late fee?”
| 0 | guesses assembled from nearby paragraphs |
| 1 | handover, with the conversation so far, to whoever is on your queue |
| 1 | line in your report: declined, outside policy |
The alternative is an agent that invents a concession you then have to honour or retract.
When you are ready
200 messages, no card, and a hard cap. If it is wrong for you, you will know inside an afternoon and it will have cost you nothing.