> We tell them the system is set up with their security in mind. This way > they and ONLY they can get the password.
And they never ask who sent it to them if it wasn't YOU? And I'm the foolish one? If I receive an email from somebody who provides me with a service, I assume that it came from that person/company. ESPECIALLY if it contains sensitive info like my username and password for accessing *their* system.
Apples and oranges. My point was that the email is coming from the system. If you explain to the customer that their password is safely locked away in "the system" (you don't have to say what system or who owns it) but that you click a button instructing the system to mail the password to them, and that the system is designed this way to keep the password out of human hands to prevent abuse/insider fraud/other FUD buzzword, they get the picture that the minor inconvenience of waiting for an email is inconsequential... after all, they lost their password and wouldn't want someone else to be able to call up and have it reset.
You should explain this to your customers in a way that conveys that "the system" is setup to work in their best interest. I don't think most reasonable people would argue with that kind of a statement, especially if they are really the domain owner (and not someone trying to hijack it).
> > Any time I've dealt with the password issue, the customer has been > understanding, even HAPPY to hear that we can't get their passwords. And I > can certainly say I've never lost a customer over this issue.
It's good to know that all of your customers are technically-minded enough to be able to make all of their domain modifications themselves. I am not that lucky.
I wish! :-) But that's a more broad subject than what I'm talking about.
-Russ
