Skip to main content
[email protected] 24/7 Support
Menu

PremiumFakes message response delay

posted by rc1279 20 hours ago 129 views 0 comments

Reporting back on the PremiumFakes support delay that's been mentioned a few times recently, since I've been in direct contact with their team about an order issue for the past week and a half.

My original message was sent eleven days ago about a proof I needed corrected before production. The first response came after four days — not fast, but within what I'd consider the outer edge of acceptable for this kind of request. The response acknowledged my correction and said it would be applied to the proof before it went to production.

Four more days passed without a revised proof. I sent a follow-up. That took three more days to get a response. The second response confirmed the correction had been made and that the card was now in production. At this point I'd already waited eight days from first contact to production start on a simple correction that should have taken a day to process.

I've seen a few posts attributing the delays to a high-volume period. That may be accurate. What I can say is that the responses I did receive were substantive — they actually addressed my specific correction rather than sending generic replies — but the pace at which those responses arrived is genuinely slow by any reasonable standard.

If you need to send a correction to PremiumFakes, do it the same day you receive the proof, not the next day. And include everything they need in the first message rather than waiting for them to ask follow-up questions. Each additional exchange adds several days to the timeline, and those days add up. My order is now on day nineteen, when it would probably be shipping by day twelve if the correction communication had moved faster on their side.

The quality reputation for PremiumFakes is what keeps me coming back despite this, but I'm actively planning to place my next order with more buffer time built into the schedule.

6

No comments yet. Be the first to comment!

Please login to comment on this thread.