Below a certain volume, no. And I would rather say that than sell you something that sits idle.
The threshold is not revenue and it is not headcount. It is how many repetitive conversations you handle, and how many of them arrive when nobody is working.
The test
Can you name a question your team answers several times a day, where the answer is the same every time and lives in a system you already have?
If you cannot, the case is weak. Buy nothing, revisit in a year.
If you can name three, you are already paying for it. Just in salary and attention rather than in software.
Where the maths usually turns
Two places, in my experience, and neither is the one people expect.
Out of hours. This is the strongest case for a small business, because the alternative is genuinely nothing. Not a slower human, nobody. The enquiry sits until morning, and a meaningful share of the people who sent it have moved on by then. Sub-one-hour response is associated with substantially better retention than a next-day reply, and a small team simply cannot cover evenings and weekends without it costing more than it returns.
The same question forty times a week. Order status, opening hours, whether you cover a postcode, how to reset something. Individually trivial. Collectively they are somebody's whole morning.
Where it does not turn
If your enquiries are genuinely varied, high-value and low-volume, you are better off with a person. Twenty bespoke conversations a week that each need judgment is not an automation problem.
If your customer data lives in spreadsheets and inboxes with no shared identifier, fix that first. An agent with nothing to look up is a chatbot, and you already know how those went.
And if you are hoping it will replace a hire you cannot afford, be careful. It will absorb the repetitive contact, not the judgment.
The honest recommendation for most small businesses
Start with what your existing tools already offer. If you are on a helpdesk or CRM with AI features included, switch theirs on and see what it takes off your plate. That costs you an afternoon.
Come back for a bespoke build when you hit the specific wall that off-the-shelf hits: when the generic answer would be wrong, because your pricing or your process or your eligibility rules are particular, and a wrong answer costs you more than no answer.
That is the point where paying for integration starts to make sense, and not really before.
