PLAYBOOK

Supplier Not Responding to Emails? Here's What to Do

Sent the follow-up Tuesday. It's Friday. They acknowledged the PO last week, now nothing. Did they get the email or am I being ghosted?

Your supplier acknowledged the PO. You sent a follow-up asking for a ship-date confirmation, a status update, or an answer to a spec question, and the thread went quiet. Three business days have passed. No reply, no out-of-office, no acknowledgment that they read it. This is one of the most awkward situations in production buying, because you have to escalate without poisoning a relationship that may already be strained, and you have to do it before silence costs you a delivery.

What this looks like

It is Friday morning. You sent a follow-up to your contact at Henderson Machining on Tuesday afternoon at 2:14, asking for the ship-date confirmation on PO 7263 for the precision-machined housing that feeds the new pump line. Six-week lead time, acknowledged on time three weeks ago. You needed the confirmation to update production planning before the Monday meeting. It is now 9:00 Friday and the thread has been silent for three business days. No reply, no auto-response, no indication anyone read the email.

Silence is ambiguous and that is the problem. There are five plausible reasons your supplier has not responded and you cannot tell them apart from the outside. Your contact may be out of office without an auto-reply. The email may have been caught by their spam filter or never made it through their company gateway. They may not have the answer yet and are stalling instead of writing back. There may be bad news (a missed promise date, a quality issue, a capacity problem) that they are working up the nerve to send. Or your contact may have left the company and nobody has been assigned to your account. Each one calls for a different response, and assuming the worst before you have ruled out the simpler explanations is how you damage a relationship for no reason.

Before you escalate, run the diagnostic. Pull the original thread and confirm the email actually went out (not stuck in your drafts, which happens more than you would expect). Look for an out-of-office reply on a separate test message. Check LinkedIn for any signal that your contact changed roles. Open the PO in your ERP and check whether anything moved on it: a receipt against another line, an attached document, a comment from your team. If none of those explain it, look at your follow-up email itself. Was the ask specific? "Just checking in" invites silence. "Please confirm the ship date for PO 7263 by Friday" invites a response. Then decide which kind of escalation fits the answer you do not yet have.

Why it matters

The cost of silence compounds quickly when the part is on critical path. A missing ship-date confirmation on a six-week-lead-time component means production planning is working from your last best guess, and on a $10,000-per-hour idle line, two days of unplanned slack costs $80,000 before anyone makes a decision. If silence forces a reactive air-freight expedite later in the cycle, you are adding $3,000 to $40,000 of premium freight on top of the part cost, and that line item lands on your budget when finance asks why.

The longer silence runs, the fewer recovery options you have. A confirmed slip you learn about on day three gives you time to dual-source, expedite from another vendor, or rebalance the build schedule. The same slip discovered the morning after the missed promise date gives you nothing but bad options and a customer call. Silent threads also break the audit trail. When production planning asks "when did you know?" you want a paper trail showing you followed up on day two, escalated on day five, and got the answer on day six. Those timestamps matter in the post-mortem.

There is also a relationship cost most buyers underestimate. Escalate to the account manager too early and you label yourself as the difficult customer, which your day-to-day contact remembers on the next request. Escalate too late and you surprise your own production team with bad news that should have been managed five days ago. Get the escalation timing right and the supplier respects you, your contact gets the air cover they probably needed, and your production planner does not find out about a slip from the floor.

What to do, step by step

Step 1: Verify the message went out and was specific enough to demand a reply. Open your sent folder and confirm the email was actually delivered. Re-read the ask. If it was a vague "just checking in," that is on you, not the supplier. Specific asks ("please confirm the ship date for PO 7263 by Friday") get specific replies. Vague asks get nothing. If your original was vague, fix it on the next attempt.

Step 2: Send a second follow-up with a hard response deadline before you escalate. The second attempt is a one-paragraph email that names the date you originally asked, the specific information you need, why you need it, and a concrete deadline. Keep the tone steady. Do not lead with frustration. Your contact may have a real reason for the silence, and an angry email forecloses the relationship even if they were about to reply with the answer you wanted.

Second follow-up template: "Hi [SUPPLIER CONTACT], following up on my email from [ORIGINAL DATE] regarding PO [NUMBER] ([PART DESCRIPTION], originally promised [DATE]). I still need [SPECIFIC ASK] to update production planning. Please respond by [TIME, NEXT BUSINESS DAY]. If you are out of office, please advise who is covering the account so I can reach them directly. Thanks, [YOUR NAME]."

Step 3: If silence continues past your second deadline, escalate to the account manager or your contact's direct manager. Day five with two follow-ups sent is the trigger most teams use. The escalation should copy your original contact (do not bypass them silently, that breaks the relationship), state the facts plainly without editorializing, and ask for a clear, finite path to a response.

Day 5 escalation template (to account manager, original contact copied): "[ACCOUNT MANAGER NAME], I am following up on PO [NUMBER] for [PART DESCRIPTION], acknowledged on [ACK DATE] with a promise of [DATE]. I sent [SUPPLIER CONTACT] a follow-up on [DATE] requesting [SPECIFIC ASK] and a second follow-up on [DATE] with a response deadline. I have not received a reply. Production is impacted starting [DATE]. Please confirm by end of business today either the requested information or a path to it. Copying [SUPPLIER CONTACT] for visibility. Thanks, [YOUR NAME]."

"I will get back to you" is not an answer. If the supplier responds to the escalation with a stalling reply, push back the same day: "Understood, I need a specific date by [TIME] so I can update production planning. What can you confirm now?"

Step 4: Communicate internally before production has to ask. Two sentences to your planner. They need lead time to adjust the schedule, and they need to hear it from you, not from the floor.

Internal update template (to your production planner): "[PLANNER NAME], heads-up on PO [NUMBER] for [PART DESCRIPTION]. I have not received a response from [SUPPLIER NAME] in three business days on [SPECIFIC ASK]. I have escalated to their account manager with a response deadline of [TIME, DATE]. Best-case ETA still stands at [ORIGINAL DATE]. If I do not have a confirmed answer by [DATE], I will move PO [NUMBER] to at-risk and we should plan around a one-to-three-day slip. I will send a firm update by end of day [DATE]. Thanks, [YOUR NAME]."

If silence continues past the escalation, the next step is the phone, not another email. By day six or seven you have done your due diligence on email and the supplier has had every reasonable chance to reply. Pick up the phone, ask for your contact directly, and if they are not available, ask the receptionist to put you through to anyone in account management or production scheduling. A phone call breaks the email-silence pattern and forces a real conversation, which is harder to ignore than a fourth message in the same thread.

How PO-Relay handles this

When you send a follow-up from your own inbox, PO-Relay's Email Intelligence tags the thread against the right PO and starts watching for a real reply. The assistant does not count an out-of-office, an automated read receipt, or a stalling "I will get back to you" as a real response. The thread stays open until the supplier actually answers the question you asked, so the silence stays visible instead of being mistaken for progress.

If a configurable response window passes (most teams set it at two or three business days for active threads), the loop is flagged on your Parts Dashboard as "awaiting response" and sorted to the top by urgency. You see it the moment you open PO-Relay, no spreadsheet hunt, no inbox scroll, no report to run.

Auto Follow-Ups drafts the second-attempt email the moment the window expires. The draft is pre-loaded with the prior thread, the original ask, the PO number, the original promise date, and a concrete response deadline. Escalation language is layered in for the second attempt so the supplier sees the pattern. If silence continues past the second deadline, the assistant drafts the account-manager escalation with your original contact already copied. You review every draft and send it from your own inbox. PO-Relay never sends email on your behalf and never writes to your ERP.

The Morning Report resurfaces the silent thread in the next day's briefing if it has not resolved overnight, so a busy afternoon does not bury it. You decide every action, every send, and every status change. The assistant drafts and flags, you review and act.

See it in action

Common mistakes to avoid

  • Sending a vague second follow-up. "Just checking in" is not an ask, it is a prompt for the same silence you got from the first email. Every follow-up after the first should restate the specific question, the PO number, the original date, and a hard response deadline. If the supplier does not have the answer yet, they can at least tell you that. Silence on a vague ask tells you nothing.
  • Escalating to the account manager before exhausting the standard cycle. Day three with one follow-up sent is too early. You have not given your contact a fair chance and you have labeled yourself as the customer who skips the chain. Two follow-ups with clear deadlines, three to five business days, then escalate. Bypassing your contact silently (without copying them on the escalation) damages the relationship even more than escalating early.
  • Reading silence as confirmation that things are fine. They are not. A supplier who stops replying after the PO acknowledgment is more likely to be sitting on bad news than working quietly. The longer they go quiet, the higher the probability there is a problem they do not want to surface yet. Treat extended silence as a yellow flag, not a sign that the order is on track.
  • Waiting for a final answer before warning production. The planner needs lead time to adjust. A two-sentence heads-up on day four ("PO 7263 is silent, escalating, will confirm by Tuesday") gives them options. The same heads-up on day seven, after the missed promise date, leaves them none. Communicate the silence as soon as it becomes a pattern, not after it costs you a date.

Keep reading

GlossaryPO AcknowledgmentGlossaryLead TimeGlossaryExpediteFeatureEmail IntelligenceFeatureAuto Follow-UpsFeatureParts DashboardFeatureMorning Report

Frequently asked questions