Deflect half your tickets with an AI helpdesk stack
You're a founder (or a team of three) drowning in the same five questions, where's my invoice, how do I reset my password, does it integrate with X, and 'customer support' is eating the day you were supposed to spend building.
Wired & tested by Sameer + Ankit
Free · the verdict
Half your tickets are the same handful of questions asked a hundred ways. You don't need a $0.99-per-resolution AI agent on top of a per-seat helpdesk to kill them. You need three things: a help center that actually has the answers, one AI bot trained on that help center to answer before a ticket is ever created, and a shared inbox to catch the real humans who slip through. Wire them with Make so every question the bot fumbles becomes a new doc, and your deflection rate climbs while you sleep. Most of this runs free at your volume.
The stack
Help Scout
Chatbase (or eesel AI)
Make
Your knowledge base content
Slack
- Help ScoutThe spine: shared inbox + a Docs knowledge base + the Beacon widget (with AI answers) on your site. One tool is your help center, your support inbox, AND the deflection surface that answers people before they email you.
$ Real free plan: up to 5 users, 1 shared inbox, 1 Docs site, and the Beacon widget with AI answers, all at $0 (capped around 50 contacts/mo). Paid Standard from ~$22-30/user/mo when you outgrow the contact cap.
- Chatbase (or eesel AI)The AI deflection bot. Point it at your Help Scout Docs, your site, and your old tickets; it answers grounded, sourced questions in the widget so the repetitive stuff never becomes a ticket. Hands off cleanly to a human when it's stumped.
$ Chatbase paid from ~$40/mo (Hobby, 1,500 message credits) up to ~$150/mo (10k credits); free tier is a 50-credit toy that deletes inactive bots, so budget for Hobby. eesel is the swap if you want a free-task tier, then ~$0.40/ticket pay-as-you-go. Verify current credit math before you commit.
- MakeThe glue and the feedback loop. Routes the bot's escalations into the inbox, tags incoming tickets by topic, and (the magic) logs every question the bot COULDN'T answer so you turn gaps into new docs. The stack gets smarter on its own.
$ Free plan: 1,000 operations/mo, enough for early support volume. Core tier from ~$9/mo for 10,000 ops, roughly 3-4x cheaper than Zapier at the same volume.
- Your knowledge base contentNot a tool, the actual fuel. Help Scout Docs covers most founders. If you need a public, developer-grade docs site too, Docusaurus is free and open-source (you host it) and GitBook is the no-fuss hosted option. The bot is only as good as what it reads.
$ Help Scout Docs: included free above. Docusaurus: $0 (MIT license, you pay in hosting + setup). GitBook: free to start, paid from ~$65/site/mo if you need the premium polish. Most founders never leave the free Docs site.
- SlackWhere the humans who slipped past the bot land for a fast answer. The 5% of tickets that are real, weird, or angry get a person in minutes instead of a day, with the bot's transcript already attached.
$ Free plan is plenty: you only need a channel and an incoming webhook. You almost certainly already pay for this (or run it free), so it adds $0 to the support stack.
🔌 The wiring
- 1
Write the 15-20 articles that answer your actual top questions in Help Scout Docs. Pull them straight from your inbox: the five things people ask weekly are your first five docs. This is the work everyone skips and it's the whole game.
- 2
Drop the Help Scout Beacon widget on your site and in your app. Now visitors search your docs and get AI answers in-context before they ever open a ticket, that alone deflects a chunk of tier-1 volume.
- 3
Train Chatbase (or eesel) on your Docs site, your marketing pages, and an export of past resolved tickets. Set a strict 'only answer from sources, otherwise hand off' instruction so it never hallucinates a refund policy.
- 4
Set the bot's escalation rule: if confidence is low or the user asks for a human, it creates a Help Scout conversation with the full chat transcript attached, so your reply has context and isn't 'can you repeat everything?'
- 5
Wire Make to tag every new ticket by topic (billing, bug, how-to, feature request). After two weeks you'll see exactly which repetitive question to turn into the next doc, deflection is a flywheel, not a switch.
- 6
Add the loop that compounds: Make logs every question the bot answered with 'I don't know' into a simple sheet. That list IS your content backlog, write the doc, the bot learns it, the ticket never comes back.
- 7
Pipe genuine human escalations to a Slack channel with the transcript and the customer's plan, so the 5% that need a person get one in minutes. Reply from Help Scout so it threads with the customer's history.
✂ What to cut
Cut the per-resolution AI agent bolted onto a per-seat helpdesk. Intercom's Fin charges around $0.99 per resolution with a 50-resolution monthly minimum, ON TOP of a ~$29/seat helpdesk, so the better it works the more you pay, forever. Cut Zendesk's ~$50/agent/mo Advanced AI add-on and the whole enterprise 'CX platform' quote (the ones that land at five and six figures a year) until you genuinely have the volume to need them. Cut the standalone live-chat widget nobody's online to answer, the second knowledge-base tool when Help Scout Docs already ships one, and the 'AI SDR for support' that's really just a worse version of a bot reading your docs. The rule: deflection comes from good docs plus one grounded bot, not from stacking AI features you rent by the conversation. Buy the help center, wire the bot once, and stop paying a toll every time a customer gets helped.
The receipts
What it costs
$0-50/mo to start: Help Scout free, Slack free, Make free, with the AI bot (~$40 Chatbase Hobby, or eesel's free-task tier) the only near-certain spend until you outgrow the free contact and ops caps
Time to wire
an afternoon to wire it (the docs take longer, budget a few sittings to write your real top-20 articles, that's where deflection actually comes from)
What it replaces
A per-seat helpdesk plus a per-resolution AI agent (Intercom + Fin at ~$29/seat + ~$0.99/resolution, or Zendesk + ~$50/agent Advanced AI), which together run from a few hundred to several thousand a month once volume and resolutions stack up
Where it breaks
The bot is only as good as your docs, garbage in, confident wrong answers out, so the maintenance is writing content, not babysitting software. Watch the seams: Chatbase credits reset monthly with no rollover and a traffic spike can drain them, Make's free ops run dry if tickets surge, and a thin or stale knowledge base quietly tanks your deflection rate. Re-train the bot whenever you change pricing or ship a feature.
Members · the full blueprint
The wiring, the configs, the templates, the Loom.
The free version above is the map. The gated blueprint is the turn-by-turn: the importable Make scenarios (bot escalation to Help Scout, auto-topic-tagging, and the 'unanswered question to content backlog' loop, JSON to import, not just described), the bot system prompt that hands off instead of hallucinating, a starter pack of the 20 help-center articles every SaaS needs (with the exact titles that deflect the most), a Slack-escalation routing recipe, and a 10-minute Loom wiring the whole flywheel live so you can clone it without guessing field mappings.
▶
How Sameer + Ankit wired it
Frame 1 of 8
Steal next week's recipe.
One wired stack in your inbox every week. Free.