Aug 2 is real: EU users must be told they're chatting with an AI before the conversation starts. Fines up to €15M or 3% of turnover.
If you embedded a support bot on your site, that obligation is YOURS, not just your vendor's.
Clanker Support discloses by default.
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, https://t.co/PtyKKAEFCr 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.
Clanker Support is for the founder who:
- ships fast and can't afford a support team yet
- is drowning in the same 10 questions over and over
- wants AI support that won't embarrass them in front of customers
If that's you, this took me months so it'd take you 2 minutes.
Our support agent tells customers when it's out of its depth. On purpose.
No fake "agent is typing…" No stalling. A real handoff notice, then a human.
This is what the visitor sees:
@ClankrSupport
Most AI support bots dead-end the moment they don't know the answer.
Watch what ours does instead - real product, real time, one take:
AI support that actually escalates.
FIFA has infinite budget and their AI support still can't do the one thing every user eventually asks for: talk to a human.
We built @ClankrSupport to just… do that.
We shipped the Clanker Support WordPress plugin — then https://t.co/Kj4QwPBdiY rejected it with "the plugin has no name."
The cause? Our build script made a zip that was secretly a tar.
tar.exe on Windows happily writes TAR format and slaps a .zip name on it. So we threw out every archiver and wrote our own zip writer on Node's zlib.
Now it's approved and live in the directory 🎉
Watch a chat widget book a Zoom call, pull UPS tracking, and file a return in one conversation, zero tab-switching.
@calcom + @Shopify actions soon on @ClankrSupport
Showing > telling.
Here's Clanker Support running live on Clanker Support app.
I asked it 4 things a real user would ask.
Watch it pull the right answer every time — and admit when it doesn't know. No edits, no retakes.
People keep asking why it's called "Clanker."
It's the dismissive sci-fi slang for robots. Everyone says it about chatbots already — "ugh, another clanker."
So I named it that on purpose. Own the joke. Then build the one clanker people don't hate.
We just shipped a React Server Components SDK for @ClankrSupport
One component in your @nextjs root layout = an AI support agent on every page.
No script tags. No layout shift. Headless when you want your own UI.
🧵
We built 4 free tools for support teams, no sign-up, no email gate:
→ AI support savings calculator
→ CSAT calculator, with industry benchmarks
→ Canned response generator
→ llms.txt generator
Free forever. Bookmark them (link below)