## TL;DR
A stuck vendor escalation moves when you make silence expensive in writing. Nudge once with new information right after the promised response time passes, then climb the contact ladder with a written deadline, and keep your own customers updated on your own cadence the whole time. The vendor's silence is their problem; your customers' silence about it is yours.

## The query

```text
how to chase a vendor on a stuck escalation
```

## Use this when

- A vendor support ticket has gone quiet past its promised response time
- Promised callbacks or fixes never arrived
- The escalation is blocking your own customers
- You keep getting "we're looking into it" with no substance

## Not for

- Choosing or evaluating vendors
- Negotiating contracts or SLAs
- Escalating inside your own company
- Writing the initial vendor support request

## Steps

### 1. Assemble the paper trail before you write a word

Gather the ticket number, the date opened, every promised response time and callback, and what was actually delivered. You are about to quote their own promises back to them; have them exact.

Expected output: a timeline with dates, promises, and gaps, attached to the internal ticket.

### 2. Send the nudge with new information, not just "bump"

Reply on the existing thread right after the promised response time passes, plus one business day. Add something new: another affected customer, a fresh log excerpt, an increased count. New information resets their queue position; "any update" does not.

Expected output: a reply sent on the thread, logged in your tracker.

### 3. Climb the ladder in writing

If the nudge gets nothing in 48 hours, loop in the next level: the named escalation contact, the escalation inbox, then your account manager or customer success rep. Each step references the unanswered thread. Never skip levels by phone without a written follow-up.

Expected output: each escalation step documented with who, when, and what was asked.

### 4. Set a deadline that has a consequence

"We need a fix plan by Thursday" beats "as soon as possible." Tie the deadline to something real: customer impact numbers, your own status page update, a renewal conversation. Vague deadlines get vague responses.

Expected output: a written deadline in the vendor thread, with the consequence stated.

### 5. Run your own customer comms in parallel

Dont let the vendor's silence become your silence. Update affected customers on your own cadence with what you know, what you are doing, and when you will update next, even if the news is "still waiting on the vendor."

Expected output: customer updates going out on schedule regardless of vendor replies.

### 6. Log it for the renewal file

When it resolves, write two sentences: how long it took, how many chases it needed. This is the evidence your team needs at renewal or when evaluating alternatives.

Expected output: a vendor reliability note filed where procurement can find it.

## The chase sequence, copy-paste

```text
Day 0: Vendor promises a response by [date]. Log the promise verbatim.
Day [promise+1]: Reply on the thread with new info:
  "Following up: this is now affecting [N] customers, including [segment].
   Latest example attached. Can you confirm a fix plan by [date]?"
Day [promise+3]: Escalate to [escalation contact], CC account manager:
  "Escalating [ticket]: opened [date], promised response by [date],
   no substantive update since. Customer impact: [numbers].
   We need a fix plan by [date]."
Day [deadline]: Final notice plus internal decision:
  "We have not received the fix plan requested for [date].
   We are proceeding with [workaround or alternative] and will
   revisit this at renewal."
Every step gets logged on the internal ticket with timestamps.
```

## Variant phrasings

### vendor not responding to support ticket

Steps 1 through 3. The mistake is opening a second ticket; stay on one thread so the silence is visible in one place.

### how to escalate with a vendor

Step 3 is the escalation. Note it only works if steps 1 and 2 built the trail first.

### stuck third-party escalation playbook

The whole sequence. "Third party" or "vendor," the mechanics are identical.

## Why it happens

Vendor queues reward the squeaky ticket and bury the polite one. Support portals sort by recent activity, so a thread with no replies sinks. Meanwhile the agent who filed it moves on to the next fire and the thread dies quietly. The chase sequence works because it treats the vendor ticket like a ticket of your own: owned, dated, and escalated on a schedule instead of on frustration.

## Edge cases

- Vendor has no escalation path published: ask your account manager for one in writing at onboarding, not during an incident. Failing that, reply-all to every address on the thread.
- The vendor is also your competitor's vendor: assume nothing about priority. The paper trail matters more, not less.
- Timezone gaps: state deadlines in the vendor's timezone and yours. "By Thursday" means nothing across twelve time zones.
- Vendor asks you to "try again" with no changes: comply once, document the attempt, and say so. Repeated blind retries are stalling; name it.
- Legal or security vendors: some truly cant share details. Ask for what they CAN share: a timeline, a fix plan date, a workaround. Silence on everything is still a chaseable offense.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_S65Ba6Sp6Bri7jGsW6a3-A