PlaybookPrompts

Draft a follow-up when a customer goes silent

Customer Support follow-upticket-managementcustomer-communication

A ticket stalls when the customer stops responding mid-resolution. This prompt writes a follow-up that prompts a reply without sounding passive-aggressive or automated.

Prompt
You are a support writer helping a rep follow up on a stalled ticket. The customer has not responded in {{DAYS_SILENT}} business days. Here is the last message sent to the customer:

{{LAST_MESSAGE_SENT}}

The unresolved issue is: {{ISSUE_SUMMARY}}

Write a follow-up message using these steps:
1. Open with a low-pressure check-in that references the specific issue — not a generic 'just following up'.
2. Briefly restate what was asked of the customer and why it matters for resolution.
3. Offer an alternative path if the original ask was too complicated (e.g., a call, a screen share, a simpler workaround).
4. Set a clear but polite deadline: if no response by {{AUTO_CLOSE_DATE}}, the ticket will be closed with an open invitation to reopen.
5. Close warmly without sycophancy.

Tone: conversational, patient, not chasing. Keep it under 120 words.

Edge cases: If the original message was asking for something sensitive (billing, account access), soften the deadline language. If the ticket is older than 30 days, acknowledge the gap.
Variables to fill in
  • {{DAYS_SILENT}}
  • {{LAST_MESSAGE_SENT}}
  • {{ISSUE_SUMMARY}}
  • {{AUTO_CLOSE_DATE}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{DAYS_SILENT}}{{LAST_MESSAGE_SENT}}{{ISSUE_SUMMARY}}{{AUTO_CLOSE_DATE}}.
  3. Paste it into one of the recommended tools below.
  4. Iterate: tighten constraints in the prompt if the output is generic.

Why this prompt is structured this way

The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

The PlaybookPrompts weekly

One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.

Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.