About Chatdrill: serious customer tools for small teams.
About Chatdrill in one paragraph — we build AI customer service software for teams who were told to choose between an enterprise suite priced for a support department and a chat bubble that does nothing else. We are building the thing in between.
- Founded 2026
- Remote team
- We answer our own support
Customer service software offered small teams two bad options.
Every small team we spoke to had made the same compromise — and every one of them was unhappy about it.
The enterprise support suite
Powerful, and priced for a department. An implementation project, a per-seat bill that grows faster than the team, and a settings screen nobody has time to learn.
The bare live chat widget
Cheap and quick to install, then it stops. No shared inbox, no automation, no idea who the visitor is, and a separate tool for every channel your customers actually use.
What we are building
One workspace with live chat, an AI agent, every channel, automation and visitor context — set up in an afternoon by the person who also answers the messages.
What we believe about AI customer support: AI when it can, humans when it matters.
Both halves of that sentence carry weight. Software should absorb the questions with one correct answer — and get out of the way the moment a person needs a person.
Repetition is a software problem
Nobody should type the return policy for the four hundredth time. That is what the AI agent is for.
Frustration is a human problem
An angry customer, an unusual case, a judgement call — a person handles those better, every time.
The handover is the product
Most tools treat escalation as a failure. We treat it as the feature that makes automation safe to switch on.
An answer needs a source
If the AI cannot point at where an answer came from, it should hand over rather than improvise.
25+
integrations live today, plus a REST API and webhooks.
6
customer channels in one shared inbox, from web chat to email.
Under 2h
median first reply on our own support, Monday to Friday.
2026
founded. Chatdrill is early, and this page says so.
No funding announcements, no award badges, no customer logos we have not earned. When those numbers change, this page changes.
One customer conversation platform, not five disconnected tools.
A question arrives, the AI answers what it can, a ticket is routed, a person resolves the rest, and the outcome feeds back into the knowledge base. That loop is the whole product.

An open edge for developers
REST API, webhooks and a JavaScript SDK, so Chatdrill fits the stack you already run.
How a small AI customer support company ships every week.
We are early. Fewer people, faster changes, and a direct line between the person with the problem and the person who can fix it.
Small on purpose
The person who builds a feature is usually the person who answers questions about it.
Ship weekly
Small changes go out continuously. Most fixes ship the week they are reported.
Talk to users directly
Every conversation in our inbox is read by someone who can change the product.
Say what isn't built
Roadmap items are described as roadmap items, never written as if they were live.
Five rules that keep our customer service software honest — and checkable.
Each one comes with the practice that proves it, because a value nobody can check is a slogan.
Claim only what runs in production
No borrowed certifications, no invented customer counts, no screenshots of features that do not exist.
Our security page lists what we have not done yet in the same size type as what we have.
AI with a visible exit
Automation should remove repetitive work, not build a wall between a customer and a person.
Every AI conversation reaches a human in one message, and the option is never hidden.
Small teams first
If a feature needs a dedicated administrator to be useful, it is not finished yet.
Setup is a script tag and a few settings — no implementation project, no onboarding fee.
Conversations are private
Support threads carry order numbers, addresses and complaints. They are somebody's private business.
We do not sell conversation data or train shared models on it without explicit consent.
Fix it, then explain it
When something breaks, the first message is what happened and what we are doing about it.
Incidents go on the status page while they are ongoing, not after they are resolved.
The one you can audit fastest is the first: read our live chat security and data protection page, where the uncertified controls are listed beside the certified ones.
The people behind Chatdrill and what they do.
We are small enough that titles would be theatre. Roles, not hierarchies — and everyone here spends time in the inbox.

Amara
Product

Daniel
Engineering

Priya
Engineering

Marco
Design

Lena
Support

Tomás
Growth
We run Chatdrill's own support on Chatdrill
Every message sent through our contact form lands in the shared inbox pictured beside this paragraph — the same product our customers use, on our own production account. Our help centre guides are written from the questions that arrive there. When something is unclear, we find out the same way you would.

Try the product this page is about.
Free plan, no card, and a real person on the other end of the widget.
No credit card required.