PhraseShelf

Thoughtful sales follow-ups

Six sales follow-up templates for existing conversations, useful resources, questions and respectful pauses. Personalize the reason for every reply.

Saved shortcut;recap

Space

Your reusable reply

Hello [name], Thank you for discussing [topic]. You mentioned [specific need]. The information we discussed is [reference]. Would [proposed next step] be useful? [your name]

Replace the example details before use.
Illustrated workflow. Create real fields in the visual editor for the details that change.

These are plain-text examples. Replace bracketed labels yourself, or add real fields with PhraseShelf’s visual editor. They are not executable template syntax.

01;recap

After a conversation

Recap an actual discussion and offer the relevant next step.

Hello [name],
Thank you for discussing [topic]. You mentioned [specific need]. The information we discussed is [reference]. Would [proposed next step] be useful?
[your name]

Use only needs the person actually shared. Replace the reference with verified material.

02;follow

Check whether information helped

Ask a focused question after sharing material.

Hello [name],
I’m following up on the information about [topic]. Did it answer your question about [specific point], or is there something you would like me to clarify?
[your name]

Keep it to one useful question. Do not imply that reading the message creates any obligation.

03;update

Share a relevant update

Offer newly available information tied to a stated need.

Hello [name],
Following our conversation about [need], I wanted to share [verified update]. Here is the relevant information: [reference]. If it is useful, I’m happy to discuss the details.
[your name]

Verify that the update is both new and relevant. Avoid invented scarcity or unsupported benefits.

04;pause

Leave the door open

Close a quiet exchange respectfully.

Hello [name],
I’ll leave the conversation here for now. If [topic] becomes relevant later, you’re welcome to get back in touch.
Thank you for your time,
[your name]

Use when further follow-up would add little value. Honor any request not to contact the person again.

05;sales-answer

Answer a specific question

Return with the detail actually requested.

Hello [name],
You asked about [question]. The confirmed answer is [answer], with this limitation: [relevant limit].
The supporting information is [reference]. Does that address the point you were evaluating?

Check the current product facts. Remove any claim you cannot support.

06;reconnect

Ask permission to reconnect

Offer a later conversation without scheduling it.

Hello [name],
You mentioned that [topic] might be relevant later. Would you prefer that I check back in [proposed period], or leave the next step with you?
Either is fine.

Use only a period grounded in the conversation. This does not schedule an automatic message.

Make the follow-up worth reading

Refer to something actually discussed. Offer relevant information rather than pretending to have a relationship or manufacturing urgency. A reusable structure should make the message easier to personalize.

These examples are for individual writing after a legitimate exchange. PhraseShelf does not find prospects, run campaigns, schedule follow-ups, or send messages automatically.

Keep claims and consent current

Check product details, prices, availability, and any promises against your own approved information. Respect a request to stop contact. Review the complete message before manually sending it.

Use a small set of purpose-based aliases. Keep dated offers out of permanent defaults so they do not quietly become stale.

Save an example as your own reply

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.