Firmcraft
← Back to home ·  Capabilities
Beyond chat

Most "AI tools" do one thing.
Operators do six.

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.

The six capabilitiesEach demonstrated below
F
Slack
Teams
SMS
Email
Telegr.
WhatsApp
01 · Multi-channel

Lives wherever your team already messages.

Same operator. Same memory. Same playbooks. Field crews on SMS, partners on Slack, clients on email — one consistent piece of work across every channel.

  • Slack · Teams · Discord · Mattermost · Matrix
  • SMS · Email · WhatsApp · Signal · Telegram · iMessage
  • Voice notes in, voice replies out — on every channel that carries audio
Mon 7amPermit watcherweekly
NowMonthly QBO close — Q1 batchrunning
Fri 4pmFriday recapweekly
Daily 6pmEOD reconciliationdaily
QuarterlyClient review packsscheduled
02 · Scheduled work

Runs on its own clock, not yours.

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.

  • Cron + natural-language scheduling
  • Pause, resume, edit any job
  • Delivery to any of your messaging channels
FORMNew lead from websitequalify + book
STRIPEPayment failed · cust 4421retry + email
EMAILCOI request · Wilshire LPdraft + send
CALHearing in 7 days · Patelprep brief
EOBDenial · claim 882041draft appeal
03 · Event-driven

Wakes up when something happens.

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.

  • Webhooks from any tool
  • Inbox + form + calendar listeners
  • Reacts in seconds, not days
QBO
Stripe
HubSpot
DocuSign
Drive
Calendly
Eaglesoft
NetSuite
Zoho
Slack
Twilio
+ yours
04 · Any tool, any API

Speaks to your weird tool, too.

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.

  • 40+ tools out of the box
  • Custom connectors in week 1
  • Browser-driven where no API exists
VoiceMaya signs emails "warmly," not "best."
ClientWilshire LP wants 2-hour COI turnarounds.
PricingImplant pre-auth packets need 3 perio probes.
WorkflowPartner reviews appeals before EL goes out.
05 · Memory + learning

Gets sharper every time it runs.

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.

  • Per-firm persistent memory
  • Learns from every correction
  • Voice + style stays consistent
PENDING APPROVAL · 1 ACTION
FC
Drafted appeal for denial #882041 — $710 underpaid. Ready to submit to Delta Dental portal.
SENDS · CLAIM_APPEAL.PDF
06 · Approvals + audit

Asks before it sends, signs, or pays.

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.

  • Per-action approval rules
  • Checkpoints + /rollback — undo any action
  • Searchable audit log, exportable as CSV / JSON
  • SOC 2 in progress · HIPAA-ready posture
Why it's a different category

What ChatGPT can't actually do for you.

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.

CapabilityFirmcraftChatGPT TeamCopilot
01 · Lives in every channel your team usesYes — Slack, Teams, SMS, email, WhatsApp, moreOne web app + mobileSide panel inside Office
02 · Runs scheduled work without being askedYes — cron-like, with holiday + conflict handlingYou have to start every chatYou have to start every chat
03 · Wakes up on events in your toolsYes — webhooks, forms, inbox, calendarDoesn't listen to anything~Within Office only
04 · Connects to your weird toolYes — custom connector in week oneYou build it yourself~Microsoft stack only
05 · Remembers your firm across sessionsYes — persistent memory, learns from editsGeneric memory featurePer-document only
06 · Approvals + audit log for sensitive actionsYes — per-action rules, exportable logNot designed for thisNot designed for this
Where it runsYour environment — your data, your audit trailMulti-tenant cloudMulti-tenant cloud
In practice

One workflow uses all six at once.

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.

01

Front desk @mentions the operator in Slack

"Patel claim — porcelain crown, tooth 14, did Friday. Submit?"

Multi-channel
02

Operator remembers Dr. Chen's coding style

Last 200 D2750s with this carrier — narrative phrasing, attached docs — pulled from memory.

Memory
03

Reads chart from Eaglesoft, files via Delta portal

Two integrations. One a modern API, one a clunky vendor portal we drove with a browser.

Any-tool
04

Asks Dr. Chen before submitting

Claims over $1,000 require partner approval. Form drafted, attachments staged, awaiting OK.

Approvals
05

Listens for the EOB — could be tomorrow or next week

Webhook on the carrier portal. The moment EOB lands, operator wakes up and continues.

Event-driven
06

Friday afternoon: weekly report on every claim

Approved · denied · pending · underpaid. Drafts appeals on every denial. Sent at 4pm sharp.

Scheduled
Ready to see it on your work?

The 20-minute call is the demo.

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.