<<<
Chronological Index
>>> <<<
Thread Index
>>>
[registrars] 1001 Transfer Failure Reasons
Here is part of an actual email from
a customer of a reseller to a reseller (to us)
which illustrates a few of the points that you have
made, and adds a few. The reseller and customer are
located in the Netherlands:
-- We contacted the owner of the domain name (name) and they came up with
-- the following answer:
--
-- ========================================
-- Hallo Robert,
--
-- Indeed we received a request.
-- But we didn't know why we were asked AND more important
-- TO WHOM THE CHANGE WOULD BE. So we rejected te request.
--
-- (Ok, I thought it might be you, but this is the real live,
-- they asked us to agree but they didn't told us why we should)
--
-- Govert
-- ====================================================
Larry Erlich
http://www.DomainRegistry.com
Paul Stahura wrote:
> End users do not respond all the time.
> I bet that if you sent a message that said
> "reply to this email and you get million dollars"
> the majority would not respond.
> A no response does not mean that the registrant did not
> want a million dollars or the name transferred.
> A no response could mean any of these things:
> 1) The registrant wants the name transfered but is out-of-town
> and cannot get email.
> 2) The registrant wants the name transfered but the email
> in the whois for the admin contact is not the same
> as the registrant's contact email address or is simply wrong.
> 3) The registrant wants the name transfered and the email
> in the whois is correct but the losing registrar made a mistake
> in sending it, or the registrant's email provider was down and
> the mail didn't get bounced back to the losing registrar for a few days.
> 4) The registrant wants the name transfered but they've shut
> off all email from the losing registrar because the losing registrar
> spams them all the time.
> 5) The registrant wants the name transfered but they don't speak
> any of the languages in your email, so they ignore it.
> 6) The registrant wants the name transfered but they purchased the
> name via a reseller of yours and therefore the registrant
> does not know the losing registrar from Adam, and so they ignore
> your email to them.
> 7) The registrant wants the name transfered but they use your system
> so infrequently they do not know how to change their email
> address from that one they stopped using years ago.
> 8) The registrant wants the name transfered but they put
> a fake email address in the whois so they would not get spammed
> by all these marketing companies out there who blast email
> to addresses they find in whois contacts.
> 9) The registrant wants the name transfered, so they went through
> the gaining register's processes, then get an email from you,
> and ignore it, because they already went through the gaining
> registrar's process.
> 10) The registrant wants the name transfered, but your system
> for accepting the reply emails is down and you never get their
> ACK reply message.
> 11) The registrant wants the name transfered, but the registrar
> did not collect the email address of the registrant and the
> registrant and the admin contact are two different companies
> who rarely communicate (only "The name and postal address of
> the registrant" is required to be collected by the registrar)
> ....
> 101)
> ...
> 1001) etc.
>
> Do all your processes changes cover all these likely instances?
> a "no answer" = ACK does, and at a zero additional cost.
>
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|