The Clanker Support Journal · Est. 2026
Field notes on AI support
Announcements, practical guides, and the engineering decisions behind a support widget that answers from your docs — and knows when to step aside.
Every hosted plan now starts with a 7-day free trial
New hosted Clanker Support subscriptions now begin with 7 free days — the full plan, every feature, applied automatically at checkout. Nothing is charged until the trial ends, you can cancel anytime, and a 14-day money-back guarantee backs it all up.
We diffed our marketing site against our codebase. Six claims didn't survive
We put the homepage in one tab and the repo in the other and checked every falsifiable sentence against the code that would have to make it true. Six claims failed, one page undersold us, and an adversarial re-pass caught overclaims we wrote during the honesty pass itself. Every fix shipped in one public pull request.
Two messages, one sequence number: the concurrency bug that never threw
An escalation marker and the AI reply it interrupted landed in the same conversation with the same sequence number. No exception, no log line, both inserts succeeded, and the thread quietly rendered out of order. This is the read-then-write bug that passes every test, the three-part fix whose deploy order is the point, and the five-second code search that tells you whether your codebase has it too.
'Additive columns are always safe' is wrong on Drizzle, Prisma, and preview deploys
Everyone agrees an additive column is the one schema change that can't hurt you. Then a one-line ALTER TABLE on our user table turned out to be capable of 500ing every authenticated request — because Drizzle projects every mapped column, Better Auth reads the user table on every session check, and preview deploys skip migrations. Here is the two-PR discipline we ship our riskiest schema changes with, and the one column we keep out of the ORM entirely.
A 9-point AI SEO audit checklist, run on our own site first
Next.js merges route metadata shallowly, so every page built with our metadata helper — unless it passed a cover image of its own — shipped a Twitter card with no image for about a month. That was finding one of the SEO and AI-SEO audit we ran across our five domains this month, in two passes. Here is the whole audit as a checklist you can run on your own site, including the four findings that surprised us.
We set a cache trap for our own support agent — in our own llms.txt headers
URL knowledge sources are snapshots, and everyone knows snapshots go stale. What we missed is that the refresh itself can be served by any CDN cache between the crawler and the origin — so "Recrawl → success" can silently re-store the pre-deploy content. The trap on our own site was set by our own cache headers.
Changelog: July 2026, so far — the platform month
Two weeks in and July is already our densest month: an approved WordPress plugin, a Shopify app, agents that take actions, dark mode everywhere, and a smarter, chattier widget.
Add an AI support agent to Next.js, WordPress, Shopify, or any site
One hub for every install path we ship: the universal script tag, the React Server Components SDK, the WordPress plugin, the Shopify app embed, and the iframe. Working code for each, plus a candid guide to picking one.
Our AI support agent doesn't use RAG — here's the math
Clanker Support has no vector database. We put the entire knowledge base into the system prompt on every request, and for KBs measured in kilobytes, the math says that's the right call.
We moved our SaaS backend to workerd and every Node SDK broke
The Resend SDK, the Stripe Node SDK, and Better Auth's passkey plugin all got cut from our workerd build — each over something the package dragged in, not code we call. Here is each casualty, the fetch-and-crypto.subtle code that replaced it, and an honest accounting of whether it was worth it.
Salesforce buying Fin (Intercom): what it means for your support bill
The deal is signed, not closed, and Fin's pricing hasn't moved. Here's Salesforce's dated post-acquisition track record — and what to check in your contract before renewal.
Everything that broke while shipping an embeddable AI widget
A support widget runs inside a DOM you don't control. Here's every way host pages broke ours — :empty selectors, 62.5% root font-sizes, null currentScript — and the rule we extracted from each fix.
The best AI support agents in 2026 (real pricing compared)
The best AI support agents in 2026, compared on real pricing — per-resolution vs per-seat vs flat, which LLM each tool runs on, and open-source options.
The best Intercom alternatives in 2026 (an honest comparison)
Ten Intercom alternatives compared by pricing model — per-seat, per-resolution, flat monthly, and self-hosted — with honest cons and when to stay put.
Intercom Fin pricing in 2026: the real math behind $0.99
A primary-source teardown of Intercom Fin's $0.99-per-resolution pricing: billable outcomes, assumed resolutions, seat costs, and the real monthly math.
6 open-source Intercom alternatives you can self-host in 2026
Six open-source Intercom alternatives you can self-host, compared on license, stack weight, built-in AI, and model choice — checked July 2026.
The Clanker Support WordPress plugin is approved — here's how it was built
Clanker Support is now an approved WordPress.org plugin. The story of building it, getting through the plugin review (including the zip that was secretly a tar), and how to put an AI support agent on your WordPress site in under a minute.
Add AI customer support to your Next.js app with one Server Component
A step-by-step tutorial for @clankersupport/widget-rsc: install the SDK, drop one component into your root layout, then restyle it with CSS or rebuild the UI entirely with headless primitives.
Changelog: June 2026 — launch month
We launched on Product Hunt. Also: smarter escalation, a full dashboard restyle, workspace-wide search, annual plans, and a security hardening pass.
Clanker Support is live — and we're on Product Hunt today
Clanker Support is officially live and featured on Product Hunt. Here's what we built: an AI support agent that answers from your docs and hands off to a human the moment it can't.
Introducing Clanker Support: AI support that actually escalates
Today we're launching Clanker Support — a drop-in widget that answers from your docs and hands off to your team when the bot can't help.
How to reduce support tickets by 60% with an AI first-response layer
A practical guide to deploying an AI first-responder that handles the repetitive stuff so your team can focus on the conversations that matter.
Why we built on LLM Gateway instead of calling OpenAI directly
Our reasoning for using a model abstraction layer from day one — and why it's already paid off twice.
Setting up email threading for your support widget
A step-by-step guide to configuring inbound email so customer replies thread back into the same conversation.
Changelog: May 2026 — knowledge base improvements and new model options
Longer knowledge base support, model selection per project, and a handful of inbox quality-of-life improvements.
The case for self-hostable AI support
Why open architecture matters for tools that sit between you and your customers.