Six support replies for useful details, troubleshooting, progress, unresolved issues, workarounds and resolution checks. Adapt each to the actual case.
These are plain-text examples. Replace bracketed labels yourself, or add real fields with PhraseShelf’s visual editor. They are not executable template syntax.
Ask for enough context to understand a problem.
Hello [name], Thanks for describing [issue]. Could you share the steps you followed, what you expected, and what happened instead? Please remove passwords and other sensitive information from anything you share. [your name]
Request a screenshot only when it helps, and explain what should be hidden before it is shared.
Offer a specific, reversible check.
Hello [name], To narrow down [issue], could you try [specific check]? Before you begin, save any work that could be affected. Please tell me what you see afterward. [your name]
Replace the check with a verified step appropriate to the product. Do not suggest deleting data without a safe procedure.
Keep the person informed without an invented deadline.
Hello [name], A brief update on [issue]: [verified current status]. The next step is [confirmed next step]. I’ll share further information when it is available. [your name]
Separate what is known from what is still being investigated. Add a time only when confirmed.
Ask whether the proposed fix addressed the original problem.
Hello [name], Were you able to try [step]? Please let me know whether [expected behavior] now works, or describe what still happens. Thank you, [your name]
Name the exact behavior you want to verify. Do not claim the issue is resolved before the person confirms.
Avoid repeating a step that did not help.
Hello [name], Thanks for trying [step]. Since [issue] still occurs, could you tell me what changed, if anything, and which message now appears? I’ll use that to identify the next useful check.
Read previous results before asking again. Do not make the customer repeat a risky action.
Describe a verified alternative and its limit.
Hello [name], While we investigate [issue], you can use [verified alternative] for [specific task]. It does not support [known limitation]. Please tell me if that limitation prevents the work you need to do.
Use only an alternative you have checked; a workaround is not proof that the issue is fixed.
A saved support reply is a starting point. Read the question first, acknowledge the specific issue, then remove irrelevant instructions. Ask for information you can use rather than collecting everything by default.
Keep policy-sensitive passages separate and review them against your actual approved policy. None of these examples promises refunds, eligibility, response times, or a resolution.
Organize replies by purpose: diagnose, explain, update, and check. Add fields for the issue or next step. PhraseShelf keeps an individual local library; it does not assign tickets, synchronize teams, or send replies.
Test your actual editor with harmless content. Named support platforms remain unverified. Use prepared text and manual paste where direct insertion is not available.
Copy an example, choose New snippet, give it a title and enter its suggested alias in Shortcuts and aliases. Paste into Plain text, edit the details, then choose Save snippet. Test it in Help & practice with the alias followed by Space.
For changing details, replace each bracketed label with a real field in the visual editor. Keep punctuation in the adjacent text segments. Preview a short and a long answer, then review the final message before using it. Choose a different alias if the suggestion already exists in your library.