tiny.help
tiny.help · For SaaS teams
Live chat for SaaS, with support guides written from your code
Your coding agent reads the repo and writes the support guides. You read them. Then an assistant answers customers from those guides and your docs, links the page it used, and stops the moment you start typing. From $9 a month, and never billed by the answer.
14 days free. No seats to count, no per-resolution fee.
The knowledge base is the hard part. Your agent writes it.
Every help desk ships with an empty knowledge base, and at a small company it stays empty, because the only people who know the answers are shipping the product.
Connect Claude Code, Codex, Claude or ChatGPT and it reads your codebase feature by feature, writes one guide per area with a source line under every claim, checks each claim back against the code, and strips anything internal. Then it stops and asks you to read the folder.
The guides live in your repo. When the product changes, the agent updates them and pushes them again.
In your project’s folder
claude mcp add --transport http \
tinyhelp https://desk.tiny.help/mcpCodex: codex mcp add tinyhelp --url https://desk.tiny.help/mcp. Then say:
Set up tiny.help for https://yourapp.comYou sign in, pick a plan and read what it wrote. Nothing is uploaded until you say so.
It answers how-to questions, and knows when not to
The assistant is off until you switch it on. Once it is, it sticks to what your guides and docs say.
Only your material
No general knowledge about products like yours, so it can’t invent a setting, an endpoint or a price. Every answer links to the page behind it.
Billing goes to a person
Refunds, cancellations, discounts, legal threats and security reports skip it entirely. It never promises a fix, a date or a credit.
It stands down when you type
Start replying and it stops, mid-thread. No switching it off to take over, and no arguing with your own bot in front of a customer.
Know who is asking
Signed-in users can arrive already named. Set window.tinyhelp before the widget’s script tag and the conversation carries their name, email and whatever else you pass: the plan, the account, the MRR. It shows beside the thread and on the Live page, which lists everyone in your app right now and the page they’re on.
Your own Help button can open the chat too, with the question already typed: window.tinyhelp.open('Upgrading to Pro').
<script>
window.tinyhelp = {
name: 'Priya Sharma',
email: 'priya@example.com',
meta: { plan: 'Pro', mrr: 49 }
};
</script>
<script src="https://tiny.help/w.js" data-key="wk_…" async></script>Work the ticket where the code is
A lot of SaaS support is a bug report in disguise. The same connection that writes your guides lets your agent read the inbox: pull a thread into your terminal, find the line, draft the reply in your voice. It only sends once you say so.
From your phone it is the same desk, installed in two taps, with a push when something arrives.
- One inboxEvery product, every conversation, with notes, @mentions and saved replies for the team.
- Email both waysStep away and it becomes email. Reply from your inbox and it lands back in their chat.
- Assign with an @mention“@sam can you take this?” pins it to the top of Sam’s inbox until it’s done.
Per seat, then per answer
That is how the big desks bill. Three people on Intercom’s cheapest tier, billed annually, with its AI switched on, against three people here.
Three Essential seats $87, Copilot $87, Fin at its 50-outcome minimum $49.50. More answers, bigger bill.
3 sites, 3 people, every feature. The assistant is included, however many questions it answers.
Growing past three people? Studio is $79 a month for six sites and unlimited people. Just you and one product? Solo is $9. Intercom figures are from their public pricing, broken down on our comparison page.
- Card up front, nothing charged until day 15
- Your conversations never train an AI model
- GDPR and NZ Privacy Act 2020
Questions.
Do I need Claude Code or Codex?
No. The assistant that answers your customers runs on our account and is included on every plan. A coding agent is what writes the guides from your repo and keeps them current, and it is the quickest way to get set up. Claude or ChatGPT in the browser works too, from docs you already have. See the setup, tool by tool.
Does it work in a single-page app?
Yes. Set window.tinyhelp after sign-in and change it when the plan changes; the widget reads it fresh rather than once at load, and it notices route changes, so the desk names the page someone is actually on.
Our app has a strict Content Security Policy. What do we add?
https://tiny.help to script-src, frame-src and connect-src. The chat runs in a frame served from tiny.help, and the widget makes one small request for the Live page.
What happens when the assistant doesn’t know?
It says so, rather than guessing, and hands the conversation to you with a push to your phone. It asks once for an email address, so if the customer has gone by the time you reply, your answer reaches them by email and their reply threads back in.
How is this different from Intercom?
Price shape, mostly. Intercom charges per seat, then $0.99 for each outcome its AI resolves. tinyhelp is a flat monthly price with the assistant included. Intercom also does far more: product tours, workflow builders, SLAs, a help centre, many more channels. If you need those, stay. The full comparison.
Your docs are already in the repo
Connect your agent, read what it writes, and the answers are live by this afternoon.
From $9 a month, every plan is everything. Cancel in one click.