- Impact
- 82
Hello,
I listed my domain name 4-t.com on flippa last week and purchased the domain name upgrade.
The name did not show up on the domain page as you pay for. I quickly contacted the support email and they got back to me later on that night. They "fixed the error" but my domain then started on the list of upgrades from the point of when I made the purchase. So, it was #7 on the list and not #1 on the list as any upgrade would start from. They basically replied with 'tough" and it was close enough to #1 and didnt warrant any type of credit. I was kind of upset bc I feel if you pay for an upgrade you should get that full time. NOW today with only 2 days left I ordered the upgrade again (They assured me this was not a glitch and all things were dandy, and it never happens) BUT guess what, not listed again. I paid in full and not listed, now I have to wait for support to fix the "error" and I guess I have to just deal with where and when the name shows up.
I just wanted to make everyone aware that this error has now happened twice and frankly you have to "deal with it"
I listed my domain name 4-t.com on flippa last week and purchased the domain name upgrade.
The name did not show up on the domain page as you pay for. I quickly contacted the support email and they got back to me later on that night. They "fixed the error" but my domain then started on the list of upgrades from the point of when I made the purchase. So, it was #7 on the list and not #1 on the list as any upgrade would start from. They basically replied with 'tough" and it was close enough to #1 and didnt warrant any type of credit. I was kind of upset bc I feel if you pay for an upgrade you should get that full time. NOW today with only 2 days left I ordered the upgrade again (They assured me this was not a glitch and all things were dandy, and it never happens) BUT guess what, not listed again. I paid in full and not listed, now I have to wait for support to fix the "error" and I guess I have to just deal with where and when the name shows up.
I just wanted to make everyone aware that this error has now happened twice and frankly you have to "deal with it"







