Why on earth does the chat person need ask me my account number yet again? I am logged in to the website, they should be able to see that I am Account # 820914 and currently viewing Order # 788321.
Ensuring that this sort of context communication as the lowest bar for an in-app chat would go a long way towards making me prefer it to a conversation where I have to gather and route relevant information.
I imagine this might be similar.
I suspect the real answer is that when they finally hand you off to a live human being, that human is sitting in the boiler room of a third-tier contractor on a different continent than the main headquarters of the business, and they have no idea what you're currently looking at on your screen. It's technically possible to do this handoff with a complete picture of how the user got there, but that requires a degree of technical integration most companies don't seem to want to pay for.
But presumably you are talking to customer-service agents, not representatives, and what are they supposed to do about it? I share your frustration, but this seems to be just a recipe for spreading that frustration, not for resolving it.
(Unless you meant something else, e.g., you are professionally involved in call-center design, in which case I applaud your being a voice of sense in that domain, and thank you for it!)
Lately I have been facing a breakdown in business processes with my local electric utility that first disconnected my electricity because one of my tenants made a mistake. I think they finally understand that I have three services at two houses at one address, but I went through two periods since then of getting no electric bill for months (which I won’t let slide because the last time they stopped billing me I got disconnected.) Getting that fixed involved waiting three hours on hold which got me talking to regulators again. The crew building the new deck at the other house has also deferred work because they have been unable to get through to anyone there who can turn the service off temporarily so they can work near where the wire comes in.
Because their integration isn't very good.
Ones I've used, as long as you've configured a way to resolve the user, it pops right up in the service side of the chat system.
Be scared of those. They typically use client side JavaScript to read a cookie to know which username is active.
There is usually no verification of that info, so obviously it could be faked by a malicious client.
The docs say that, but it's way too easy to just trust the info rather than setup a properly secure solution.