As for your second point, all that is based on trust in the company that they're not storing in plain text and opening it to the CEO...which I hope is the case for most companies. I was more trying to give a sense that I'm really not happy giving my password to any person. When it's a web form, you just have to have trust or the whole idea of passwords is broken.
Your first point is just innuendo, right?
Now, having seen some of the alternative systems suggested, I think I agree.
I instinctively do not want to give my password to anyone. And that's a great habit to get into, and we want regular people to get into that habit. That would make phishing less useful.
In this case it seems they're trying really hard to protect your domain from harm. But yes, I've been mostly persuaded.
* Tier 1 customer service people do not have plaintext access to customer passwords, and
* Tier 1 customer service people do not have the ability to manipulate customer accounts without their passwords (and thus consent).
On the scale of security/customer-service interactions at service providers, this sounds like MONUMENTAL EPIC WIN. What exactly am I missing here?
And,
How on earth could you possibly input a password into some random text field in an application that you would not provide to the CEO of the company hosting that text field?