4 ready-to-use ChatGPT prompts for ticket response and macros. Fill in the bracketed fields, paste into ChatGPT, and go.
Customer Support · 4 prompts
01
Write a Ticket Response That Actually Solves the Customer's Problem
Write a support ticket response grounded in the specific issue and account context, avoiding generic reassurance that doesn't actually resolve anything.
You’ll needcustomer's messageaccount or product contextknown solution or workaroundtonepolicy constraints
Prompt
You are a support agent writing a ticket response.
Write the response using the context below.
Context:
- Customer's message: [message]
- Account or product context: [account context]
- Known solution or workaround: [solution]
- Tone: [tone]
- Policy constraints: [policy]
Instructions:
1. Address the specific issue the customer described, not a generic version of it — restate their actual problem in your own words to show you understood it before giving the fix.
2. Give the concrete solution or workaround directly rather than a vague "try restarting and let us know" that just defers the real answer.
3. If the fix requires steps, number them clearly so the customer can follow along without guessing.
4. Note any limitation or caveat about the fix honestly (partial fix, known bug, workaround only) rather than implying it's fully resolved when it isn't.
5. End with a specific next step or confirmation ask, not a generic "let us know if you need anything else."
Output format:
- Response opening (shows understanding of the issue)
- Solution or steps
- Honest caveat if applicable
- Specific next step or confirmation ask
Missing information policy:
Ask up to 2 concise questions only if the issue or account context is unclear.
Quality bar:
- Addresses the specific issue, not a generic version.
- Gives a concrete fix, not a deferred non-answer.
- Honest about limitations of the fix.
02
Tell a Customer Their Issue Won't Be Fixed as Fast as They Hoped
Write a response telling a customer their issue will take longer to resolve than expected, being direct about the timeline without sounding evasive or excessively apologetic.
You’ll needissue descriptionreal reason for the delayrealistic new timelinewhat's being done in the meantimecustomer's stated urgency
Prompt
You are a support agent delivering a timeline delay.
Write the response using the context below.
Context:
- Issue description: [issue]
- Real reason for the delay: [delay reason]
- Realistic new timeline: [timeline]
- What's being done in the meantime: [interim actions]
- Customer's stated urgency: [urgency]
Instructions:
1. State the delay and the reason directly in the first two sentences — burying bad news under a long preamble reads as evasive and wastes the customer's time.
2. Give a specific new timeline, not a vague "as soon as possible," since a specific timeline (even if it's not what they wanted) is more trustworthy than an open-ended promise.
3. Note what's actively being done in the meantime so the customer knows the issue isn't sitting untouched.
4. Match the apology level to the actual severity — over-apologizing for a minor delay reads as insincere, while under-acknowledging a major one reads as dismissive.
5. Offer a concrete alternative or workaround if one exists, rather than leaving the customer with nothing to do but wait.
Output format:
- Direct delay statement with reason
- Specific new timeline
- What's being done meanwhile
- Alternative or workaround if available
Missing information policy:
Ask up to 2 concise questions only if the delay reason or new timeline is unclear.
Quality bar:
- States the delay directly, not buried in preamble.
- Specific timeline, not vague reassurance.
- Apology level matches actual severity.
03
Build a Macro Library for a Recurring Support Issue
Build a macro library for a recurring support issue with variant openings and modular pieces, designed to be adapted per ticket rather than sent verbatim.
You’ll needrecurring issuecommon variations of the issueresolution stepstoneknown edge cases
Prompt
You are a support operations strategist building a macro library.
Build the macro set using the context below.
Context:
- Recurring issue: [issue]
- Common variations of the issue: [variations]
- Resolution steps: [steps]
- Tone: [tone]
- Known edge cases: [edge cases]
Instructions:
1. Build the macro as modular pieces (opening, diagnosis, fix, close) rather than one rigid block, so agents can swap the opening or add a sentence without rewriting the whole thing.
2. Write 2-3 opening variants so customers don't receive an identically-worded reply to what they might see reported by other customers online, which erodes trust in the support experience.
3. Flag the specific edge cases where this macro doesn't apply cleanly and shouldn't be used without modification.
4. Note which parts of the macro must stay accurate as-is (policy language, technical steps) versus which parts agents should personalize freely.
5. Include guidance for the agent on how to quickly adapt the macro to the specific ticket details.
Output format:
- Modular macro pieces (opening variants, diagnosis, fix, close)
- Do-not-use edge cases
- Fixed vs personalize-freely sections
- Agent adaptation guidance
Missing information policy:
Ask up to 2 concise questions only if the issue or resolution steps are unclear.
Quality bar:
- Modular, not one rigid block.
- Multiple opening variants included.
- Edge cases where it doesn't apply are flagged.
04
Respond to a Feature Request Raised in a Support Ticket
Respond to a customer's feature request raised through support, acknowledging it genuinely and routing it internally without overpromising on roadmap timing.
You’ll needfeature request as describedknown roadmap status if anyworkaround if one existshow it will be tracked internally
Prompt
You are a support agent responding to a feature request.
Write the response using the context below.
Context:
- Feature request as described: [request]
- Known roadmap status if any: [roadmap status]
- Workaround if one exists: [workaround]
- How it will be tracked internally: [tracking]
Instructions:
1. Acknowledge the specific request and why it matters to the customer's use case, not a generic "thanks for the feedback" that doesn't show you understood the request.
2. Be honest about roadmap status — don't imply a timeline the team hasn't committed to just to make the customer feel better in the moment.
3. Offer a workaround if one exists, so the customer isn't left with nothing until (or if) the feature ships.
4. Explain how the request will be tracked internally so the customer knows it's not disappearing into a void, without promising it will be built.
5. Keep the tone genuinely appreciative without sounding like a scripted deflection.
Output format:
- Acknowledgment of the specific request
- Honest roadmap status
- Workaround if available
- Internal tracking explanation
Missing information policy:
Ask up to 2 concise questions only if the request or roadmap status is unclear.
Quality bar:
- Specific acknowledgment, not generic thanks.
- Honest about roadmap, no false promises.
- Explains tracking without sounding like a deflection.