The problem, stated plainly
Whichever campaign issue has brought you here, at some point the only way forward is a message to Tide support. This page covers the route, the timing, and — most importantly — exactly what to include so the first message you send is the only one you need. A vague message saying cashback has not arrived gets a vague, slow answer; a specific message with dates and evidence gets a specific one.
The route
Tide's member support runs through the app's in-app chat, available around the clock, with priority handling on higher membership plans. Use the app rather than social media: support cannot discuss your account on a public channel, and you will simply be redirected.
When to contact support
- Before completing an application, if a referral code has been rejected and you still have the chance to fix it.
- The same day you notice you forgot to enter a code.
- After a relevant deadline has passed and a reasonable validation-and-payment window has also passed, if a reward has still not appeared.
- As soon as you spot a discrepancy in your qualifying card spend or Instant Saver balance, ideally with time left in the window to correct it.
- Never immediately after a deadline passes — allow validation time first, or you will get a holding answer rather than a useful one.
What to include in an offer query
- Your account opening date, clearly labelled as the opening date rather than the application date.
- The campaign code you used, and where you entered it.
- The specific reward step you are asking about, and its deadline.
- Screenshots of the relevant settled transactions or savings balance history.
- One clear question, not a narrative.
A model of what to say
State the facts in order: account opening date, campaign code, the step you are asking about, the evidence attached, and a single direct question — for example, whether the £75 step has been validated, or whether a specific transaction has been counted. Avoid framing it as a complaint in the first message; ask the factual question first, and only escalate if the answer does not address it.
Evidence checklist to attach
- Screenshot of account opening date.
- Screenshot of the full card transaction list for the relevant window, with statuses visible.
- Screenshot or export of Instant Saver statement, if the query relates to the savings step.
- The campaign code and the page you applied through.
- Reference number of any previous chat, if this is a follow-up.
What support can do
Confirm whether a campaign is attached to your account, explain how a condition is measured, tell you whether validation has run, and escalate a genuine error. That is a lot, and it is worth asking.
What support cannot do
Override the campaign terms, guarantee a payment, or promise a discretionary exception in advance. Support will not confirm in advance that a code will be added to your account or that a reward will be approved before the relevant condition has actually been checked. If a condition was not met, no amount of persistence changes the mechanics — and the same is true for us, since we are an independent site with no access to your account.
If you are still not satisfied
Ask support to confirm in writing, within the chat, exactly why a step was not validated. If you believe there has been a genuine processing error rather than a condition that was not met, ask specifically for the query to be escalated. Keep your tone factual — the strength of your case comes from the evidence, not from repetition.
Two more message scripts, ready to adapt
For a code that appears rejected during signup: 'I applied through [campaign page URL] on [date] and entered REFER200 at the promo code step, but [describe exactly what happened — rejected, blank, no confirmation]. Screenshot attached. Can you confirm whether the code has been attached to my application?' Send this before you submit the final step if you still can — it is far easier for Tide to fix an in-progress application than a completed one.
For a card-spend total that looks short of the threshold: 'My account opened on [date]. My 30-day window ends on [date]. My running total of settled card transactions is [amount], shown in the attached screenshot. Can you confirm whether this matches your records, and whether any of these transactions have been excluded and why?' This version works because it asks a specific, checkable question rather than simply stating that a total 'feels wrong'.
Setting realistic expectations before you message
Support can look at your account and explain what it shows; it generally cannot see behind Tide's own validation logic to explain why a specific automated decision was made beyond what the data shows. Response times vary and are not something we can quote, since they depend on your plan tier and current volumes at Tide's end — do not assume a same-day answer, and do not assume a slow first reply means the query has been ignored.
It also helps to expect a factual answer rather than a sympathetic one. Support agents work from the same campaign terms and account data you can see yourself; they are not able to make a discretionary exception on the spot for most queries, even where you feel the outcome is harsh. A calm, evidence-led message gets you the fastest route to a correct answer, whatever that answer turns out to be.