Six email reply templates for acknowledgements, clarification, scheduling, missing attachments, next steps and closing a conversation. Copy and adapt.
These are plain-text examples. Replace bracketed labels yourself, or add real fields with PhraseShelf’s visual editor. They are not executable template syntax.
Confirm that you received a message without promising a deadline.
Hello [name], Thanks for your message about [topic]. I’ve received the details and will review them before replying further. Best, [your name]
Replace the topic with a short, specific description. Add a response date only if you can commit to it.
Resolve an ambiguity before starting work.
Hello [name], Before I continue with [topic], could you clarify [specific question]? That will help me work from the right information. Thank you, [your name]
Ask for the minimum information needed. Avoid stacking several unrelated requests into one sentence.
Offer a next step without implying a booked meeting.
Hello [name], Would a short conversation about [topic] be useful? I’m available [option one] or [option two], in [time zone]. Please let me know which suits you. [your name]
Replace every time and include the time zone. A reply is an invitation, not a calendar booking.
Record a completed exchange and leave a clear reference.
Hello [name], The update we discussed is now [verified status]. You can find the relevant details at [reference]. If anything needs clarification, please point me to the specific part. [your name]
Use only a status you have checked. Replace the reference with a working, appropriate link or document name.
Get the file mentioned in the message.
Hello [name], Your message refers to [file], but I cannot find the attachment. Could you resend it or share the current link? Thank you.
Check the thread first. Name the file so the sender can choose the right version.
Clarify what happens after your reply.
Hello [name], I have reviewed [material]. My next step is [action]. To proceed, I need [specific input] from you. Could you share that when available?
Include only the input that blocks the next action. For meeting decisions, use the meeting recap collection.
A reusable email should help the recipient understand what happens next. Start with the reason for replying, then ask one specific question or describe one next action. Remove anything that does not fit the thread.
Save these as plain text to begin. Replace bracketed labels before sending, or rebuild the changing details as real fields in the visual editor. Choose a tone appropriate to the relationship.
Keep acknowledgements separate from substantive answers so a quick reply does not imply a decision. Use a folder for email and tags for scheduling or follow-up. Check the recipient, any attachments, and the final wording yourself.
These examples do not assert compatibility with any named email service. Try the destination editor first; Copy and manual paste remain useful alternatives.
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.