Clanker Support

You installed a chat widget. Checked the dashboard a week later: 3 conversations. Two were you, testing it. The widget isn't broken, it's being ignored. Which is worse, because nothing shows up in an error log. 5 small fixes that turns your widget into a real conversation

Most AI support widgets lock you into their cloud. Clanker Support is open-source and self-hostable — and now listed on G2, Capterra, and AlternativeTo so you can actually compare it against the big players.

Your support widget can talk now. @ClankrSupport just got voice chat, customers ask out loud, it answers out loud, straight from your docs. No guessing, and when it can't answer, it hands off to your team with the full conversation attached.

I threw 12 languages at our AI support agent. Spanish, Japanese, Arabic . It answered every single one in the customer's language. There's no language setting. There's no language dropdown. It just… answers. And as of this week, it does it out loud. 🔊

My SaaS analytics showed 0 signups for 30 days straight. I assumed the launch was dead. Then I actually dug in. Quick postmortem on how my tracking lied to me.

Saw an ecommerce operator on Reddit share that adding a chat widget to their checkout and cart pages cut abandonment by 15%. Their data on what people ask at checkout: "does this work with my setup" "what's the return policy" "is this the right plan for me" 30 second questions. But unanswered, they become abandoned carts. Here's the part nobody talks about though: two of those three are policy and money questions. Put a normal AI chatbot there and it will eventually invent a return policy 10 seconds before someone pays. That's not a support ticket anymore, that's a chargeback with a screenshot attached. Checkout is the worst possible place for a bot that guesses. It's why Clanker only answers from your actual docs. No matching source, no answer, straight handoff to a human. At most spots on your site that's a nice-to-have. At checkout it's the whole point. One script tag, loads light so it won't slow the page it's supposed to be saving.

Want better AI support without any tool? Steal this: Audit your last 50 support tickets. The top 10 repeated questions = the docs you're missing. Write those 10 answers well. That alone deflects most of your volume. (Or feed those docs to a clanker and let it answer them for you.)

We usually save the changelog for month-end. July's first two weeks didn't fit in a month: — Clanker Support is an approved WordPressplugin — Shopify app, built + deployed — the agent now does things: order lookups, Cal.com bookings — dark mode that mirrors your site's toggle — say "human" and the escalation button appears — official Next.js package on npm

The whole install is this: <script src="..."></script> One line. It inherits your site's vibe, sits in the corner, and starts answering. No iframe jank, no SDK, no "talk to our solutions engineer." I optimized the boring stuff so you don't have to think about it.

Old way: pick a support platform, migrate everything, train a bot for weeks, pay per seat, pray. Clanker way: paste your docs URL, copy one embed snippet, live in an afternoon. I'm not saying the old tools are bad. I'm saying you probably don't need all that yet.

Clanker Support didn't start as Clanker Support. It started as "llmchat" — a generic name for a generic idea. The product only got good when I got specific: not "an AI chat thing," but "the support bot that doesn't lie to your customers." Narrow your promise. Then keep it.