Fixed lost domain thanks to Epik team

[Dondomainer]

I hown this domain since $2014, then in 2017 i transfer the domain to epik.com on 2017, now in 2019-01-25, i pay the renew 17.98 USD.

now, in 2019-06-18, i Updating nameservers for all my domains, including, toolsco.com. I forget it for a few days, and today when i try to visit the domain nothing happens, it surprises me, i remembered that I had changed the NS. well, when i go to my epik account the domain had disappeared.


contact the epik team and they tell me that the domain was sold in their market for $25 (WTF!!)


They say i sold my domain for $25 on the market.


This is my task manager

this seems like it happened on 2019-06-20

In the end epik help me to recover my domain. For me this is the best time that an register do the right for me. All the best for epik.com....with that service only need lower the price for t domain transfer.lol

 

[Rob Monster]

I edited that part out -- it was a little feisty. The mic drop is good though.

I actually called the client here. He now has my cell phone so the next time he has a panic, he can contact our support team first, and if he does not like their answer, he can call me directly.

All systems go at Epik. I coached the client about how to handle cases like this. He offered to pull the thread. I think the thread has education value:

1. Check your prices for clerical errors when listing.

2. Hold your domains at registrars that will have your back when you screw up.

3. Always check with your registrar before you throw them under the bus.

 

[Rob Monster]

I am highly impressed. Please when are you guys doing a promo?

We have a $2.99 .CO promo for the next 2 days. It is awesome.

More promos here:

https://www.epik.com/promos/

Thanks for asking.

 

[xynames]

So the title should be

Epik.com sold my domain due to my mistake for $25

Which is just another of the countless “jumping the gun” threads at NP where the title is misleading and the OP turns out to be at fault.

I don’t think the Monster stepped in to help solely due to this thread he probably would’ve helped even without the publicity.

Glad this one turned out well.

 

[Rob Monster]

Nah, the title should be:

I totally screwed up but Epik had my back. Thanks Epik.

 

[xynames]

True but he couldn’t have known in advance of creating the thread that it would end up that way.

So probably he should’ve created no thread and just contacted you first.

 

[Haris]

@Rob Monster A lot of emails I receive from Epik land in my junk folder so maybe that's why @gipson feels he didn't receive any emails.

 

[Ollie3000]

I actually called the client here. He now has my cell phone so the next time he has a panic, he can contact our support team first, and if he does not like their answer, he can call me directly.

Quality customer service here @Rob Monster

Very Impressed!

 

[Spex]

Great thread, bad title.

I, for one, will walk away educated after reading this and will be checking all my BINs asap

 

[Rob Monster]

So the title should be

I don’t think the Monster stepped in to help solely due to this thread he probably would’ve helped even without the publicity.

Glad this one turned out well.

You and I might not agree on all topics at NamePros, but you are correct on this point -- we do our best to fix industry problems to the extent that we are in a unique position to help.

While you know that I have a Christian worldview, the idea of doing right by others is universally agreed across the major faiths, as well as among enlightened people in the secular world.

 

[xynames]

Where we get into the gray area, and let's hope this isn't tested in the future, is if OP had erroneously entered say, $250. Would that qualify for the "too good to be true" reversal?

 

[Rob Monster]

Where we get into the gray area, and let's hope this isn't tested in the future, is if OP had erroneously entered say, $250. Would that qualify for the "too good to be true" reversal?

The error policy is a tough one. It is invoked pretty rarely.

We invoked it here because the clerical error is obvious here in the "25.888" pricing. So the usability error is arguably in the software, which is why we'll take this one and are adding error trapping to prevent such incidents.

The other time we invoked it in 2019 were:

1. A customer abused the expiry cycle, by waiting until day 43 to transfer domains out of Epik. We had sent domains to Snapnames on day 36 of expiry, and so a bunch of Snapnames auctions got unwound. We plugged that gap too. The auth code changes on day 35.

2. A customer had listed Course.net for $1895 -- it was a domain that they had deleted, and which we restored without restore fee. In the restore price, the default BIN price had not been removed, and so someone came along and bought it. As we often do courtesy restores, we closed that loophole too.

The codebase of Epik.com is increasingly vast. BitMitigate.com and Sybil.Li also added both tech and talent as well as sophisticated customers that have addressed problems that most domainers don't think about on a daily basis but ultimately helps them.

 

[MSN-Domains]

Transferring into Epik.com this week. Anybody who takes a interview on a vineyard is my kind of man.

 

[Rob Monster]

Transferring into Epik.com this week. Anybody who takes a interview on a vineyard is my kind of man.

Although the lighting was not great for that interview, it was too nice a day to not do that one outside.

 

[DomainRecap]

Seriously, kudos to Rob for standing up for this one, and in an incredibly quick and efficient manner.

 

[carob]

The number entered was actually 25.888, which perhaps you intended to mean 25,888, using a European notation form for a US dollar price. This was your clerical error. It happens.

Some platforms do not accept figures with punctuation, so confusion about decimals and commas is prevented.

 

[Rob Monster]

Some platforms do not accept figures with punctuation, so confusion about decimals and commas is prevented.

Yup, we added error trapping for this case in the last hour:

Epik engineers just do it.

 

[Bernard Wright]

I just woke up. I’m in the same time zone as Rob, and his first post was at 6:29 AM. So, he was on the case by 6ish. *** I’ve edited out a snarky remark here. But I would like to point out that Rob has responded to a very serious accusation against Epik an a professional manner.

I’ll echo that the thread title could use a revision.

 

[Bob Hawkes]

What an incredible response from @Rob Monster at Epik. I hope the OP appreciates how this goes well beyond any reasonable expectation given the facts of the case.

I know we do not all read TOS as carefully as we should, but this is important information:

In the meantime, we invoked our error clause (transparently posted on our site under refund policy) in order to reverse the domain back to you. This is the reason why registrars have 60-day transfer locks. We do waive this lock for cases where we are sure there is no risk of fraudulent conveyance.

I would like to agree with @xynames that we have way too many threads with sensationalistic titles made in haste before the facts are known or the company or individual has a chance to respond.

While it is wonderful this worked out, we should all be vigilant when entering data and in promptly checking our email confirmations.

Thanks once more, Rob, for a response that is a model for our community, and delivered incredibly fast.

Bob

 

[Dondomainer]

@Rob Monster Thank you very much for your call and your prompt help to recover my domain.

 

[Dondomainer]

What an incredible response from @Rob Monster at Epik. I hope the OP appreciates how this goes well beyond any reasonable expectation given the facts of the case.

I know we do not all read TOS as carefully as we should, but this is important information:


I would like to agree with @xynames that we have way too many threads with sensationalistic titles made in haste before the facts are known or the company or individual has a chance to respond.

While it is wonderful this worked out, we should all be vigilant when entering data and in promptly checking our email confirmations.

Thanks once more, Rob, for a response that is a model for our community, and delivered incredibly fast.

Bob

is just sensationalistic titles just because it's not your domain.