Some callers want a human, and they are entitled to. How a system handles that moment says more about it than anything in the feature list — partly because it happens constantly, and partly because it is where the worst experiences live.
The three ways it goes wrong
Refusing. A system that will not hand over, however politely, turns a mild preference into anger. Nobody has ever been talked out of wanting a person by a machine explaining that it can help.
Pretending. Worse. Claiming to transfer, playing hold music, and returning to the same automated voice. Callers work this out and it is the interaction that generates genuine hostility.
Silence. The transfer is attempted, nobody picks up, and the caller sits in dead air not knowing whether the call is still connected. This is the most common failure and the least designed-for.
What should happen
Hand over on the first clear ask. Not the third. If someone says "can I speak to a person", the next thing should be an attempt to connect them, not a negotiation.
Say what you are doing. "I'll put you through now" — so the silence that follows is explained.
Have a real answer when it fails. This is the part worth pressing any vendor on. When nobody is free, or it is eleven at night, or the handoff drops, the caller should be told plainly and given something to do. The honest version is: nobody is available right now, here is the business number to call directly, or leave a number and someone will ring back.
What should never happen is the caller discovering the failure by listening to nothing for forty seconds.
That fallback is how we built ours — if the transfer does not connect, the caller is told and given the business phone number rather than left holding. Live call transfer has the detail.
The after-hours version
At two in the afternoon, "can I speak to someone" has a good answer: transfer.
At two in the morning it does not, and the only decent response is honesty. Nobody is here, we open at nine, leave a number and we will ring you first thing — or if it is urgent, here is what to do.
A system that attempts a transfer at 2 AM and then sits in silence is worse than one that says plainly that everyone has gone home. The rules for asking for a person should differ by time of day, and it is worth checking that they do.
When the system should offer first
A good system does not wait to be asked. It should hand over on its own when:
The question is about an allergy or anything medical. No exceptions, no improvising. Someone will call back.
It is a complaint. Nobody who has had a bad experience wants to describe it to software first.
It has failed twice. If it has misunderstood the same request twice, a third attempt will not help. Offering a person at that point is the difference between a caller who felt handled and one who felt trapped.
The request falls outside what it should do. A price that depends on inspection, an unusual booking, a large party with conditions.
Offering before being asked is what makes an automated system feel competent rather than obstinate.
What the caller should never have to do
Say it more than once.
Press a hidden key. Pressing zero is a habit people learned from phone trees, and it should work, but it should not be the only route.
Explain the whole thing again to the person. If a transfer happens, whoever picks up should have the context. Failing that, the system should have told the caller they will need to repeat themselves, so it is expected rather than infuriating.
Testing it in three minutes
Call whatever you are evaluating and say "can I speak to someone please".
Count how many times you have to ask. Listen for whether it explains what is happening. Then — the important one — call outside opening hours and do the same thing, and listen to what happens when there is nobody to transfer to.
That second call is the one that separates systems. Most vendors have designed the happy path and not the other one, and the other one is the one your callers will meet on a Sunday evening.