Robb Schrader

Not every AI job needs a chatbot

· AI & Business · Robb Schrader

Most people meet AI as a chatbot. You ask, it writes. That’s great for a reply, a script or a menu description. But a lot of the work in a local business isn’t writing at all. It’s sorting.

Is this call an emergency, or can it wait until Tuesday? Is this web form a real customer or spam? Is this review a complaint the owner needs to see today? Is this invoice from a vendor we actually use? Each one is a choice between a few answers.

There’s a kind of AI built for exactly that. Instead of writing a paragraph, it reads the message once, picks from the answers you gave it, and tells you how sure it is. Because it isn’t writing word by word, it can be a lot faster and cheaper to run than a chatbot doing the same job. The newer ones are being trained to be honest about that number: when one says it’s 90% sure, the goal is that it’s right about nine times out of ten.

That last part matters most for us. A tool that knows when it’s unsure can hand the hard ones to a person.

Where a contractor or restaurant can use it

  • Sort incoming calls, texts and forms: emergency, routine, quote request, spam. No heat, an active leak or a sparking panel goes to the on-call tech. The rest waits for morning.
  • Flag reviews: praise, complaint, or “the owner needs to see this today.”
  • Tag a restaurant’s catering and private-event requests by date, headcount and budget, so nobody has to dig through the inbox.
  • Check vendor invoices against what you normally order and flag the odd ones before they get paid.
  • Score your own past work: which quotes won, which jobs made money, and what they had in common.

The rule that keeps it honest

Set a line. Above it, the tool acts. Below it, a person decides. If it’s 95% sure a message is spam, file it. If it’s less sure, put it in front of a human. And if it ever calls something “routine” that turns out to be a burst pipe, move the line. AI that sorts should save us time, not make the calls nobody can take back.

What we can do this week

  • List the yes-or-no and pick-one questions you answer all day. Those are jobs for a sorting tool, not a chatbot.
  • Write the answer options down in plain words: emergency, routine, quote, spam. Clear options get clear results.
  • Test it on last month’s messages before you trust it with today’s. Count what it got wrong.
  • Keep a person on the edge cases. Anything below your line goes to a human, every time.
  • Save the chatbot for writing. Replies, scripts, follow-ups. Use the right tool for each job.

The question isn’t “can AI do this?” It’s “does this job need words, or just a decision?”

← All writing

Support this work

Everything here is free to read. If it helped, you can leave a tip.

Support