Templates

Communication

Follow up with customers the right way

Use Template

By Nalvin

Use Template

Description

Nalvin helps you close the loop after shipping a fix or feature by identifying who requested it, drafting an update in the right tone, and optionally sending it once you confirm recipients and content. It can also suggest what to ask next, so the outreach becomes a discovery opportunity instead of a generic “FYI” email.

Supported Integrations

Templates are flexible by default. Nalvin automatically picks the right integrations based on what you’ve connected.

How to best use this template

Below are a few tips & tricks from the Nalvin team to get the most out of this template.

Be explicit about the audience

Closing the loop differs for customers vs internal stakeholders. Tell Nalvin who the message is for and what tone to use, then reuse that as a default.

Include context without overpromising

You can level this up by stating what changed, what’s now possible, and what’s still not supported. Clear boundaries prevent confusion and follow-up escalations.

Use a confirmation gate before sending

Nalvin should always present the recipient list and final text before sending. This prevents misfires and helps you catch sensitive details.

Offer a call-to-action

Ask Nalvin to include one question or next step (try the feature, confirm the fix, share remaining gaps). This turns outreach into learning.

Track the follow-up in CRM when useful

If your team uses CRM notes, Nalvin can draft a short note to log the outreach after you approve. This keeps CS and product aligned.

Be explicit about the audience

Closing the loop differs for customers vs internal stakeholders. Tell Nalvin who the message is for and what tone to use, then reuse that as a default.

Include context without overpromising

You can level this up by stating what changed, what’s now possible, and what’s still not supported. Clear boundaries prevent confusion and follow-up escalations.

Use a confirmation gate before sending

Nalvin should always present the recipient list and final text before sending. This prevents misfires and helps you catch sensitive details.

Offer a call-to-action

Ask Nalvin to include one question or next step (try the feature, confirm the fix, share remaining gaps). This turns outreach into learning.

Track the follow-up in CRM when useful

If your team uses CRM notes, Nalvin can draft a short note to log the outreach after you approve. This keeps CS and product aligned.