A useful customer-support reply names the customer’s problem, explains what happens next and asks for only the information needed to continue. The six original examples below cover common situations. Adapt them to the actual case and your company’s process before sending.

You can copy these examples into any email draft. To reuse them with SlashFlow, save the body as a template and give it a distinct shortcut. Text in square brackets is a manual editing note, not a SlashFlow variable. Replace every bracketed note before you send.

Choose the reply that matches the case

A template is a starting point for a reply. It does not establish that a task was completed, approve a refund or change the status of a ticket.

Six replies to save and personalize

1. Acknowledge a new request

Suggested shortcut: /sfack

Hello [customer name],

I’ve read your message about [specific problem]. I’m going to check [next action] so we can work out [what that check should establish].

I’ll update you by [date, time and time zone], even if the investigation is still in progress.

[Your sign-off]

Before sending: name the problem in the customer’s terms. Include an update time only if you can meet it; otherwise replace that sentence with a confirmed next step. An acknowledgment is not a resolution estimate.

2. Ask for the missing details

Suggested shortcut: /sfrepro

Hello [customer name],

To check [specific problem], could you tell me:
• What you expected to happen?
• What happened instead, including any visible error wording?
• Which steps led to it, and which app or browser version you used?

Please leave passwords, payment details and private customer information out of your reply or screenshots. If you already sent these details, point me to that message and I’ll use it.

[Your sign-off]

Before sending: remove questions the customer has already answered. Ask for a screenshot only when it would help, and explain what needs to be visible. For a nontechnical case, replace the diagnostic questions with the one detail you actually need.

3. Give an update when there is no confirmed fix

Suggested shortcut: /sfprogress

Hello [customer name],

An update on [problem]: we have checked [completed check and its result]. We have not yet confirmed [what remains unknown].

The next step is [specific action]. I’ll share the next update by [date, time and time zone].

[Your sign-off]

Before sending: include only checks that actually happened. If you have a workaround, describe its limits and any effect on the customer’s work. Avoid “almost fixed” when you cannot support that claim.

4. Follow up when you still need a response

Suggested shortcut: /sfcheckin

Hello [customer name],

I’m checking whether you still need help with [problem]. The next thing we need is [specific detail or confirmation] so we can [next action].

If the situation has changed, let me know what is happening now. You can reply in this thread so the earlier details stay together.

[Your sign-off]

Before sending: check for a reply in another channel or an update from a colleague. Do not say the issue is resolved just because the customer has not replied. Mention a closure deadline only when it matches an established process that applies to this case.

5. Explain an accepted handoff

Suggested shortcut: /sfhandoff

Hello [customer name],

[Receiving person or team] has accepted the next step for [problem]: [specific action]. I’ve included [relevant case summary] so they have the details already shared.

[Who will update the customer] will update you by [agreed date, time and time zone]. For now, [any action the customer needs to take, or “there is nothing else you need to send”].

[Your sign-off]

Before sending: confirm the handoff, owner and timing. Do not use this wording while the receiving team is still being contacted. Share only the case information that team needs and your process permits.

6. Check a proposed resolution

Suggested shortcut: /sfverify

Hello [customer name],

We have [specific change or completed action] for [problem]. Could you try [precise verification step] and tell me whether [expected result] now happens?

If it still fails, please share what you see at that step so we can continue from there.

[Your sign-off]

Before sending: verify that the stated action is complete. Give a short check the customer can perform without risking their data or interrupting work unnecessarily. Do not turn “we made a change” into “your problem is solved” before there is evidence.

Personalize the reply without rewriting everything

Keep the structure, then change the parts that belong to this conversation: the customer’s name, the exact symptom, the work already completed and the next responsible person or action. Read the previous messages before asking another question.

For example, replace “Could you send more details?” with “Does the error appear when you save the template, or when you type its shortcut?” The second question separates two different failures without asking the customer to repeat the whole story.

Before sending, search the draft for [ to catch unfilled notes. Check names, links, attachments and any commitment to a date. If the case involves a refund, complaint or access decision, use your approved process rather than inventing a policy inside a reusable reply.

Use a saved reply in Gmail with SlashFlow

  1. Save one useful reply

    In the SlashFlow workspace, open Templates → + New template. Enter a shortcut such as /sfrepro, a descriptive title and the reusable message in Body. Select Save template. Keep subject lines out of the body unless you intentionally want them in the message.

  2. Try the shortcut in a draft

    In desktop Gmail using Chrome, open a new message or reply and click in the editable message body. Type the shortcut exactly as saved; a matching shortcut expands as you finish typing it. Try it in a draft first, away from text you need to preserve. The text-shortcuts guide covers setup and troubleshooting.

  3. Review before sending

    Replace the bracketed notes, remove irrelevant questions and read the complete message with any existing draft text. SlashFlow inserts text; it does not send the email or confirm a ticket action for you. Send from Gmail only when you are ready.

Use the same letter case as the saved shortcut, and avoid making one shortcut a prefix of another. These six suggestions use distinct endings. Some browser fields and custom editors are unsupported; browser address bars, Chrome settings and password fields are not places to expand these replies. If an existing Gmail tab loses its page connection after an extension update, preserve your draft and reload the page.

Gmail also has its own message templates on computers. If you only need saved email replies there, Google’s Gmail template instructions explain that built-in option. SlashFlow’s templates can also be reused in other supported browser fields; it is not a shared help-desk inbox or ticketing system.

The real SlashFlow Templates workspace with its saved reply library and editor
The actual SlashFlow template workbench. The six examples in this article are text to save yourself, not a preinstalled template pack.

Watch a saved shortcut expand in the real ChatGPT composer →

Keep a small library you can trust

Start with the two replies you use most. Give each a title that describes the situation, then update the wording when your process changes. Remove outdated links, product names and promises. Keep case-specific information in the current conversation rather than in a template you might reuse for someone else.

For a new SlashFlow account, follow the Quick start guide. Text expansion needs an active trial or subscription. First-time eligible accounts can start a 14-day trial with a card; then $3.49 USD/month including applicable tax, automatically renewed unless canceled. Cancel in Account before the trial ends to avoid a charge. Existing subscriptions keep their current plans.

Save the reply you need next

Choose one example, make it sound like you and try its shortcut in a draft.

Set up SlashFlow →