Most Support Delays Are Caused by the First Message
When an order goes sideways, the instinct is to write straight away and say something is wrong. That message then sits in a queue, gets read, and produces a reply asking for the order reference, which you send, which produces another reply asking what exactly is wrong. Two days have passed and nothing has been resolved.
The fix is not writing more, it is writing once, completely. A support channel handling a high volume of tickets can only act on what is in front of it, and a message containing everything needed for a decision gets a decision. This guide covers how to contact support about your order in a way that gets a real answer on the first pass.
Write Before You Are Annoyed, Not After
Timing changes what is possible. A correction to order data can only be made before the print job commits, which is a matter of minutes or hours, not days, as set out in changing your order details after you submit. A delivery problem is easier to trace while the courier's records are recent.
The exception is delivery timing itself, where writing too early wastes everyone's time. If your order is inside its stated window, tracking has not stalled, and nothing has actually gone wrong, there is nothing for support to act on. Read what a stalled tracking status means before reporting silence as a problem, because a quiet scan gap is normal.
What Every Message Needs
Include these five things and most tickets resolve in one reply.
- Your order reference, at the very top, exactly as it appears in your confirmation.
- The email address the order was placed with, if you are writing from a different one.
- One clear sentence saying what the problem is.
- The current status: what tracking says now, or what arrived and when.
- What you want to happen, stated plainly.
That last item is the one people leave out. Support cannot read intent from a description of a problem. Say whether you want a field corrected, a reship, a replacement, or simply confirmation that the delay is normal.
Attach Evidence When the Card Is in Your Hand
For anything physical, photographs replace paragraphs. A card that arrived damaged, printed wrong, or that will not scan is easiest to resolve when the evidence arrives with the first message.
Photograph the whole front and the whole back flat under even light, then take a close shot of the specific problem area. Avoid flash, which blows out the laminate and hides exactly the detail being disputed. If the issue is a failed scan rather than visible damage, say where it failed and how many times, and read what to do if your ID will not scan first, since some causes are environmental rather than defects. The wider arrival check is in inspecting your order on arrival.
One Thread, One Issue
Keep everything about one order in a single thread. Opening a second ticket because the first has not been answered yet is the most common self-inflicted delay in support, since it splits the history and often resets the queue position.
Equally, do not stack unrelated questions into one message. A correction request and a general question about delivery times will be answered at the speed of the slower one. Send the urgent thing on its own.
What Not to Put in a Message
Some habits actively slow a ticket down or create risk that did not need to exist.
- Payment credentials of any kind. No legitimate channel needs them to look up an order.
- Documents belonging to other people, which are irrelevant to your order.
- A long narrative of events with the actual question buried in the middle.
- Screenshots of a tracking page instead of the tracking number itself.
- Details of anyone else's order, even if you ordered together.
The privacy angle is worth a thought too, especially if you are writing from a device that is not exclusively yours. The practical steps are in keeping order details private on a shared computer.
What Happens After You Send It
A well-formed ticket typically follows a short arc: acknowledged, checked against the order record, decided, and actioned. Where a decision needs the courier, it takes longer, because the carrier's own inquiry process runs on its own schedule and support is waiting on it too.
Give a reasonable gap before following up, and when you do, reply in the existing thread rather than starting fresh. If the outcome is a reship or a replacement, the timeline effectively restarts, which is covered in what happens if an order is lost or damaged.
A Template You Can Reuse
Keep it this plain. Order reference on line one. Problem in one sentence. Current status in one sentence. Requested outcome in one sentence. Photos attached if the card is in hand.
Four lines and an attachment beat four paragraphs every time, because everything needed to make a decision is visible without anyone having to ask a follow-up question. Most of what makes this easy is set up before you order at all, in the record-keeping habits described in the order checklist.
Frequently Asked Questions
What should I include in my first support message?
Your order reference, the email the order was placed with, one sentence on the problem, the current status, and what outcome you want. A message with all five usually resolves in a single reply instead of a back-and-forth.
How long should I wait before contacting support about a delay?
Let the stated delivery window run its full length first. Tracking commonly goes quiet for a day or two between scans without anything being wrong, so writing inside the window rarely produces new information.
Should I open a new ticket if I get no reply?
Better not to. A second ticket splits the history across two threads and can push you back in the queue. Reply within the original thread instead, which keeps everything in one place.
What photos help most with a damaged card?
The full front and full back, laid flat under even light, plus a close shot of the problem area. Skip the flash, since it blows out the laminate and hides the detail you are trying to show.
Is there anything I should never send?
Payment credentials, other people's documents, and details of anyone else's order. No legitimate support channel needs payment details to look up an order, and a request for them is a warning sign in itself.
Can support fix a typo in my order?
Only before the print job commits, which is why speed matters more than wording. Send the order reference plus the old and new values immediately, and see the guidance on changing order details for what stays editable and for how long.