TN
Tammy N

1 reviews | Active since Jun 2023

03 Jun 2023, 09:35

WORST EXPERIENCE EVER

I will never again purchase through dial a bed as they have the absolute worst customer service ever. Purchased 2 beds seperately on Wednesday the 31st of May using my TFG account. Recieved a call on Thursday asking if they can deliver so I asked if this is for both the beds. The person had no idea about the other bed so i gave her both order numbers she said she will call me back and never did. I decided to give them a call back on Friday since I didn't get any confirmation and then the person says that the order is pending on their side due to an issue with TFG. Then I get a call back telling me to cancel the order and reprocess so I said why should I do that if I can see on my side I was billed on my tfg account. So they say they will sort it out with tfg and again they say they will call me back and don't. I go on their website and use the live chat this morning to query my order. The person tells me to hold on for almost 15 mins and then says she sent me an email because my order is still pending. I told her I dont have any email from her she doesn't respond. I call TFG to see if there is a problem. They check and says there is absolutely no problem on their side it shows the purchase as approved and have definitely been billed and even asked why don't dial a bed just call them to confirm if they have an issue. This has been the worst experience ever. I wish I had never made the purchase through them and now I'm worried if I cancel it will still reflect on my account for me to pay for something I don't have. Never ever purchase online with them it's the worst.

0
Replies (2)
Dial-a-bed
Dial-a-bed's reply04 Jun 2023, 16:13
Official
Hi Tammy, your query has been escalated to our online manager for urgent attention and will be in contact with you soonest to assist. Thanks, NG. 
Dial-a-bed
Dial-a-bed's reply04 Jul 2023, 10:18
Official
Hi Tammy,  our team has provided an update and this response is to confirm that your query has been resolved. Thanks, NG.