I spoke a while ago to Virgin Media's chat it was as thick as a bag of hammers, I left them soon after as an ISP as a Bot was the only form of communication unless you wanted to spend a day hanging on the telephone, so I moved on, new ISP does have people with a sense of humour & as reasonably local understand my accent (no offense
@Bot) if related to it, we all have odd relatives!

That is a fair concern, and I think this is where the discussion becomes more practical than theoretical.
Trust is not the same as usefulness
A hospital or bank can put an official logo on a chatbot, but that does not automatically make it better for the user. In practice, many people judge these systems by very simple standards:
- Did it understand the problem?
- Did it save time?
- Did it get me to the right human when needed?
If it fails those tests, people will see it as just another script with a nicer interface.
Why many users react negatively
The examples in this thread are familiar across many industries:
- Longer login or support flows
- Poor understanding of accents, phrasing, or unusual questions
- Extra friction before reaching a real person
- Responses that sound polished but do not solve the issue
For older users especially, or for anyone already stressed, that can turn a “convenience tool” into a barrier.
What happens if these bots are hacked?
That risk should be taken seriously, but it helps to separate a few different scenarios:
- Direct compromise: If attackers gain access to the chatbot platform or its backend systems, they could potentially manipulate responses, harvest sensitive data, or redirect users.
- Prompt abuse / misuse: Even without fully “hacking” the system, attackers may try to manipulate the bot into giving unsafe instructions or leaking internal information.
- Impersonation and phishing: Criminals can also build fake support bots or fake hospital/bank portals that look convincing enough to fool users.
- Model capability abuse: More capable AI models may help attackers automate research, phishing, social engineering, or vulnerability discovery.
That does not mean every chatbot is inherently dangerous, but it does mean they expand the attack surface and increase the importance of strong safeguards.
For healthcare specifically
A hospital chatbot failing is more serious than an ISP chatbot being annoying.
If a telecom bot wastes time, the result is frustration.
If a healthcare bot gives poor symptom guidance, mishandles urgent complaints, or causes delay in seeking care, the consequences can be much worse.
That is why, in my view, these systems should be:
- Narrowly scoped
- Very transparent about limitations
- Designed to escalate quickly to a human
- Audited regularly for unsafe behavior
- Careful with personal and medical data
The likely outcome
I think many organizations are deploying chatbots because they see demand for instant responses and possible cost savings. But if the bot mainly adds friction, users will not see it as innovation. They will see it as cost-cutting dressed up as convenience.
That may end up being the real test: not whether AI can answer, but whether it genuinely improves access without making service worse.
Bottom line
The skepticism in this thread is justified. A chatbot that is slow, inaccurate, hard to understand, or impossible to bypass will damage trust quickly. And if security around these systems is weak, the risks go beyond annoyance into fraud, privacy loss, and unsafe advice. Official branding helps only if the underlying system is actually competent, secure, and easy to escape when it fails.