A chatbot waits for you to type. An operator works on its own schedule, lives in every channel your team uses, wakes up when something happens in your tools, remembers what it learned last time, and asks before it does anything risky. Six capabilities — only one of which is "chat."
If a tool can only do one of these, it's a chatbot. If it can do all six, it's an employee.
Same operator. Same memory. Same playbooks. Field crews on SMS, partners on Slack, clients on email — one consistent piece of work across every channel.
Monday morning recaps, Friday billing chases, monthly closes, quarterly reviews — set up once, runs forever. The work that always slips because nobody had time? That.
Form submitted. Payment failed. Email arrived. Calendar event in 7 days. EOB came back. The operator listens to your tools and acts the moment something needs doing — not later, when you remember.
Most products give you a list of "supported integrations." We start there — then wire in the niche carrier portal, the obscure ERP, the in-house thing your last consultant built. If it has an API or a portal, it talks to it.
Knows your clients, your house voice, your pricing rules, last week's edits. Doesn't ask you the same question twice. The 200th claim is materially better than the first — because the operator remembers the 199 before it.
You set which actions need a human in the loop — money out, contracts going live, client-facing sends. Everything else just runs. Every action is logged, reversible, exportable for compliance.
A general-purpose chat tool is a brilliant pencil. Your firm doesn't need a sharper pencil. It needs the work to happen while you're with a customer.
| Capability | Firmcraft | ChatGPT Team | Copilot |
|---|---|---|---|
| 01 · Lives in every channel your team uses | ✓Yes — Slack, Teams, SMS, email, WhatsApp, more | —One web app + mobile | —Side panel inside Office |
| 02 · Runs scheduled work without being asked | ✓Yes — cron-like, with holiday + conflict handling | —You have to start every chat | —You have to start every chat |
| 03 · Wakes up on events in your tools | ✓Yes — webhooks, forms, inbox, calendar | —Doesn't listen to anything | ~Within Office only |
| 04 · Connects to your weird tool | ✓Yes — custom connector in week one | —You build it yourself | ~Microsoft stack only |
| 05 · Remembers your firm across sessions | ✓Yes — persistent memory, learns from edits | —Generic memory feature | —Per-document only |
| 06 · Approvals + audit log for sensitive actions | ✓Yes — per-action rules, exportable log | —Not designed for this | —Not designed for this |
| Where it runs | ✓Your environment — your data, your audit trail | —Multi-tenant cloud | —Multi-tenant cloud |
The capabilities aren't separate features — they compose. Every interesting playbook touches several. Here's a real one, from a dental practice we work with.
"Insurance claim submission" looks like one thing. Behind it: all six capabilities firing in sequence.
"Patel claim — porcelain crown, tooth 14, did Friday. Submit?"
Last 200 D2750s with this carrier — narrative phrasing, attached docs — pulled from memory.
Two integrations. One a modern API, one a clunky vendor portal we drove with a browser.
Claims over $1,000 require partner approval. Form drafted, attachments staged, awaiting OK.
Webhook on the carrier portal. The moment EOB lands, operator wakes up and continues.
Approved · denied · pending · underpaid. Drafts appeals on every denial. Sent at 4pm sharp.
Bring one workflow that's been bugging you. We'll map which of the six capabilities it needs, scope a playbook, and tell you honestly if it's something you should pay us for or just write a Zapier flow.