AI chatbot or another support hire? How to think about it

The question usually isn't 'chatbot or human' — it's which parts of your support volume actually need a human judgment call, and which parts are just retrieval: finding the right fact and stating it clearly.

A useful exercise is to pull a week of support tickets and sort them into two piles. Pile one: questions with a single correct, factual answer that already exists somewhere in your documentation, policies, or product pages. Pile two: everything that requires judgment, empathy, troubleshooting, or a decision only a person should make.

For most businesses, pile one is bigger than expected — often well over half of total volume. That's the pile a trained chatbot handles well, immediately, without hiring, training, or scheduling.

Pile two is where a person still matters, and probably always will. The goal of adding a chatbot isn't to remove your team from the equation — it's to stop spending their time on pile one, so more of their day goes to pile two, where their judgment is actually the point.

In practice, this usually means a chatbot doesn't replace a planned hire so much as it changes what that hire spends their time doing — less repetition, more of the work that actually needed a person in the first place.