# AI prompts for supplier chasing emails that get a date

> source: https://promptoogle.com/ai-prompts-supplier-chasing-emails/
> published: 2026-08-19T04:44:04+00:00
> updated: 2026-08-19T04:44:04+00:00
> topic: Logistics

Asking a supplier for an update gets you an update. These five prompts get you a date, an owner and a reason.

Most supplier emails ask for an update, which is the most common mistake in procurement correspondence, because an update is exactly what you get: a paragraph explaining that the order is progressing and someone is looking into it. Nothing in that reply is actionable and nothing in it is a commitment.

Supplier emails that work ask a different question. They state what was agreed, state what has happened, and ask for one specific thing — a date, from a named person, with the reason if it has moved. These five prompts do that: a core chaser, an escalation, a version for a supplier you cannot afford to antagonise, a review prompt that checks for accidental concessions, and a batch prompt for a whole open-order book.

## Why do supplier emails not get answers?

Because they ask an open question. "Could you provide an update on order 4471?" can be answered truthfully with almost anything, and the easiest truthful answer is the one that commits to nothing.

The second reason is that they are addressed to a mailbox rather than a person. An email to sales@ is nobody's job. An email to a named individual, copied to one other named individual, is somebody's job and visibly so.

Third, most chasers do not state a consequence, so there is no cost to answering next week. That does not mean threatening — it means saying what you will have to do if a date does not arrive, which is usually something mundane like informing a customer or re-planning a fitting slot.

Fourth, supplier emails bury the ask. A paragraph of context followed by a question at the end gets skimmed, and the question is the only part that matters.

## What should supplier emails actually contain?

The ask in the first line, phrased so that only a date answers it. Then the facts: order reference, what was agreed, when it was agreed, and what has happened since — each as a dated line, because a chronology is far harder to argue with than a complaint.

Then the consequence, stated neutrally and factually. Then a deadline for the reply itself, which is separate from the delivery date and is the thing most chasers omit.

And nothing else. No pleasantries that soften the ask, no apology for chasing, no speculation about what might have gone wrong at their end.

## The core prompt for supplier chasing emails

```
You are writing a chasing email to a supplier. The purpose is to
obtain a committed date from a named person. An update is a
failure.

Supplier and contact: {{company, person's name and role}}
Who else should be copied: {{name and role, or none}}
Order: {{reference, description, value}}
What was agreed: {{the date, and where it was agreed — PO,
  email, call, with the date of that agreement}}
Chronology: {{each relevant event with its date, including
  every previous chase and any reply}}
Current position: {{what they last said, and when}}
What we need: {{the specific commitment}}
Why it matters: {{the downstream consequence — a customer, a
  fitting date, a production slot}}
Our leverage or lack of it: {{sole supplier? long relationship?
  outstanding payment?}}
Deadline for their reply: {{date and time}}

Write under 150 words.
```

### The writing rules

```
Structure:

1. THE ASK — first line. Ask for a specific delivery date and
   the name of the person confirming it. Phrase it so that
   "we're looking into it" does not answer it.
2. THE CHRONOLOGY — dated lines, factual, no adjectives.
   Include every previous chase.
3. THE CONSEQUENCE — what we have to do if no date arrives.
   Factual, not a threat.
4. THE REPLY DEADLINE — a date and time for the answer itself.

Rules:
- No pleasantries before the ask. No "hope you're well", no
  "sorry to chase".
- No adjectives about the delay. The dates carry the argument.
- Never apologise for chasing.
- Do not offer them an excuse. Asking "I appreciate there may
  be supply issues" invites a supply issue as the answer.
- Do not accept or propose a new date on our behalf.
- Do not threaten anything we would not do.
- Never concede a contractual position: no "no rush", no
  "whenever you can", no "we can probably work around it".
- Ask who owns this internally if they have not said.
- If this is the third chase or later, say so with the dates.
```

## A worked example

### The brief

```
Supplier: Halden Components, contact Dave Ellis (account mgr)
Copy: Sarah Nunn (their ops director)
Order: PO-4471, 400 brackets, £6,200
Agreed: delivery 4 August, confirmed by email 12 June
Chronology: 4 Aug missed, no notice. Chased 6 Aug — "with
  production". Chased 13 Aug — "should be this week". No
  delivery, no further contact.
Need: a confirmed dispatch date
Why: they are for a fit-out with a client handover on 2 Sept
Leverage: sole supplier for this part, but £6,200 unpaid
Reply deadline: Thursday 21 August, 12pm
```

### The result

>

Dave — I need a confirmed dispatch date for PO-4471, and the name of the person confirming it, by 12pm on Thursday 21 August.

The position so far:
12 June — delivery confirmed for 4 August by email.
4 August — no delivery, no notice.
6 August — chased; told the order was with production.
13 August — chased; told it should be that week.
19 August — no delivery and no contact since.

This is the third time of asking. The brackets are for a fit-out with a client handover on 2 September. Without a dispatch date by Thursday I have to tell that client their handover is at risk and start sourcing an alternative part.

Sarah, copying you as the position has not moved in three weeks.

No adjectives, no anger, and no room to reply with an update. The chronology does all the work, and copying the ops director is stated as a fact rather than as a threat.

## The escalation prompt

```
You are escalating above a supplier contact who has not
delivered a date.

Previous emails: {{paste the full thread}}
Who we are escalating to: {{name, role}}
Relationship with them: {{do they know us?}}
Total value at risk: {{this order, and annual spend with them}}
Contractual position: {{delivery terms, any liquidated damages,
  right to cancel or source elsewhere}}
What we want from the escalation: {{a date, a replacement
  contact, a credit, or an exit}}
What we will do if this fails: {{decided in advance}}

Write under 180 words.

Rules:
- Do not criticise the original contact personally. State what
  did not happen, not who failed.
- Lead with the value at risk and the annual spend. This is
  what makes an escalation register.
- Attach the chronology rather than retelling it.
- State the contractual position once, factually, without
  legal posturing.
- Make one clear ask with a deadline.
- State what happens if the deadline passes, and only state
  something we have already decided to do.
- No emotional language. Escalations that read as frustrated
  are handled as complaints; escalations that read as
  commercial are handled as decisions.
```

## The prompt for a supplier you cannot antagonise

Sole suppliers, allocated stock and long-standing relationships change the tactics but not the objective. You still need a date; you just cannot spend relationship capital getting it.

```
You are chasing a supplier where the relationship matters more
than this order, or where we have no realistic alternative.

Supplier and relationship: {{history, why they matter}}
Order and position: {{detail}}
Chronology: {{dated}}
What we actually need: {{the minimum that solves our problem —
  it may be partial delivery, or just certainty}}
What we can offer: {{flexibility that costs us little —
  splitting delivery, extending on a different order,
  collecting ourselves}}
Our real deadline vs our stated deadline: {{be honest}}

Write under 140 words.

Rules:
- Still ask for a date in the first line. Warmth does not
  require vagueness.
- Offer a genuine flexibility that reduces their problem, and
  ask for certainty in exchange. This is the trade.
- Ask what would help them give us a date — sometimes the
  honest answer is that they are waiting on someone else, and
  knowing that is worth more than pressure.
- Do not reveal that our real deadline is later than stated.
- Do not concede the delivery position while being pleasant.
  No "no rush at all".
- No escalation language, no contractual references.
```

## The review prompt: catching accidental concessions

```
Audit the supplier email below before it is sent.

Output, quoting the exact text:

1. CONCESSIONS — any phrase that weakens our position on
   delivery, price, quality or contractual rights. Include
   softeners: "no rush", "whenever suits", "I know you're
   busy", "we can probably manage".
2. OPEN QUESTIONS — anything answerable without giving a date.
   Quote it and rewrite it so only a date answers.
3. OFFERED EXCUSES — anywhere we have supplied a reason they
   can adopt.
4. UNSUPPORTED CLAIMS — any assertion about what was agreed
   that is not in the chronology.
5. THREATS WE WOULD NOT CARRY OUT — anything stated as a
   consequence that we have not actually decided to do.
6. MISSING ELEMENTS — is there a reply deadline, a named
   person, and a stated consequence.
7. TONE RISK — anything that would read as personal rather
   than commercial if forwarded internally by the supplier.

Assume this email will be forwarded to their management and
possibly read in a dispute.

EMAIL: {{paste}}
CHRONOLOGY OF RECORD: {{paste}}
```

Point seven is the useful discipline. Every supplier email is a document that may be read later by people you did not write it for, and the ones that read as measured are the ones that survive that.

## Chasing a whole open-order book

```
You are producing this week's chasers across all open overdue
orders.

Our position: {{payment terms, typical leverage, escalation
  contacts by supplier}}
Open orders: {{table — supplier, contact, PO, value, agreed
  date, days overdue, last contact, last response, downstream
  impact, sole supplier yes/no}}

For each overdue order, write the appropriate email, choosing
the right register: standard chase, escalation, or
relationship-sensitive.

Rules for the batch:
- Choose the register from the data, and say why for each.
  Third chase or later goes to escalation automatically.
- Never send two separate emails to the same person on the
  same day. Consolidate into one email covering all their
  overdue orders, with a line per order.
- Sort output by downstream impact, not by value.
- Flag any supplier with more than {{n}} overdue orders as a
  supplier-level problem rather than an order-level one, and
  draft a separate note to the buyer.
- Flag any order where the agreed date is not evidenced in the
  chronology. We cannot chase a date we cannot show was
  agreed.
- Output a table: supplier | orders | register | reply
  deadline | escalation date if no reply.
```

Late payment cuts both ways here: if you are chasing while holding their money, expect it raised, and the [statutory late payment rules](https://www.gov.uk/late-commercial-payments-interest-debt-recovery) apply to both sides. The consolidation rule matters more than it sounds. Three separate chasers to the same account manager on one morning reads as disorganisation and gets all three deprioritised.

## Common mistakes with supplier emails

Writing supplier emails that ask for an update. It is the default phrasing and it guarantees a non-answer. Ask for a date and the name of the person confirming it.

Supplying the excuse. "I imagine there are supply chain issues" is polite and it hands them a reason that cannot be argued with. Ask the question and let them account for it.

Softening the ask with an apology for chasing. You are asking about something that was agreed and has not happened. There is nothing to apologise for, and the apology signals that the deadline was optional.

Chasing without a chronology. Without dated lines it is your recollection against theirs, and the whole force of a good chaser is that the dates are not in dispute.

## What to check before supplier emails go out

Supplier emails live or die on their dates. Check every date in the chronology against the actual record — the PO, the confirmation email, the delivery note. One wrong date and the reply is about your error rather than their delay.

Confirm the agreed delivery date is evidenced somewhere you could produce. A date agreed on a phone call and never confirmed in writing is not a date you can chase, and the fix is a follow-up email at the time, not a firmer chaser later.

Check that any stated consequence is one you have actually decided to carry out. A threat you do not follow through on costs you the next three chasers.

Finally, read it as though the supplier has forwarded it to their director. If any sentence would embarrass you in that context, it is the sentence to remove — and the position is usually stronger without it.

## Related prompt guides

- [AI prompts for summarising insurance claim notes](https://promptoogle.com/ai-prompts-insurance-claim-summaries/)

- [AI prompts for drafting standard operating procedures](https://promptoogle.com/ai-prompts-standard-operating-procedures/)

- [AI prompts for restaurant menu descriptions that raise spend](https://promptoogle.com/ai-prompts-restaurant-menu-descriptions/)

---
Published by Promptoogle. Canonical version: https://promptoogle.com/ai-prompts-supplier-chasing-emails/