---
title: "Sales demo request and follow-up email templates"
url: https://meet.barq.dev/templates/sales-demo-follow-up-email
updated: 2026-11-17
author: "Hammad Ali"
---

# Sales demo request and follow-up email templates

> **Short answer:** A demo follow-up email should connect the next action to the prospect's stated goal, with a recap only of what you discussed. These five variants cover a sign-up, a webinar and later evaluation stages. Offer a meeting when it resolves an open question; send the promised answer directly when it doesn't.


## What should a demo follow-up email ask for?

Ask for the next decision the prospect can make, such as choosing a walkthrough time or confirming whether a requirement has been answered. After a demo, name the unresolved question and the material you're sending, so the recipient doesn't have to reconstruct the conversation.


Don't assume a purchase. "You asked whether [requirement] is supported" is more accurate than "You're ready to get started" when the buyer hasn't said that.


Separate facts from your recommendation. If someone mentioned a possible launch date, call it a possible date until they've committed to it; don't turn an exploratory conversation into a deadline you then use to chase them.


We recommend one requested action per message. A prospect shouldn't need to book a meeting, complete a questionnaire and introduce their manager before they can receive the answer you promised during the demo.


## Which demo request or follow-up template should I use?

Pick the email that matches the contact's actual stage, with no claim that a sign-up or webinar attendance means they requested a sales call. Each demo follow-up email sample leaves the product details and evidence in brackets for you to supply.


Match the context honestly. These demo follow-up email examples work as individual messages, and their timing should follow what the recipient agreed or the next step you've chosen for that relationship.


### After a sign-up: offer help with one task


```text
Subject: Help trying [task] in [product]?

Hi [Name],

Thanks for trying [product]. If you're looking at it for [known use case], I can walk through [task] in [duration].

Would [dated time and zone] or [dated time and zone] work? If you'd prefer to explore on your own, reply with a question and I'll answer by email.

[Your name]
```


Use this after a sign-up when you're authorised to contact the person and know the stated use case. If you don't know what they're trying to do, ask; don't insert a guess as though they told you.


### After a webinar: offer a focused demonstration


```text
Subject: A closer look at [webinar topic]

Hi [Name],

Following [webinar title], I wanted to offer a [duration] walkthrough of [feature or task]. We'd focus on [question the demonstration can answer].

If that would help, choose a time here: [demo booking link]. You can also reply with the question you'd like answered, and I'll tell you whether a call is needed.

[Your name]
```


Use this for a webinar contact you may follow up with. Only refer to their attendance or question if you know it happened; a registration alone doesn't establish either.


### After a completed demo: send the promised answer


```text
Subject: [Product] demo: answer on [open question]

Hi [Name],

Thanks for the conversation about [goal]. You asked about [requirement], and here's the answer we promised: [verified answer and supporting material].

We agreed that [next action], with [owner] handling it by [agreed date]. Does that still reflect your plan?

If another walkthrough would help resolve [remaining question], we can arrange one after you've reviewed this.

[Your name]
```


Send this once you have the promised material. Don't book another meeting merely to deliver a short answer, and don't invent an owner or due date that wasn't agreed during the call.


### Technical follow-up: define the next demonstration


```text
Subject: Next demo: testing [requirement]

Hi [Name],

To answer [open requirement], I suggest a [duration] session covering [test or demonstration]. Please include [required role] if they'll help assess the result.

Could your group do [date, time and zone] or [date, time and zone]? I'll confirm [specialist's role] before sending the invitation.

If another question matters more now, let me know and we'll adjust the agenda.

[Your name]
```


Use this when a second demo has a defined purpose. Coordinate the specialist yourself before confirming; the prospect's agreement alone can't reserve another employee's calendar.


### Re-engagement: ask whether the evaluation is still active


```text
Subject: Is [evaluation topic] still on your list?

Hi [Name],

When we last spoke, you were reviewing [stated requirement]. Is that still something you're working on?

If a short update would help, you can choose [duration] here: [booking link], or send your current question by reply. If the project has paused or you've chosen another direction, let me know and I'll stop following up on it.

[Your name]
```


Use this after a pause in an existing exchange, not as a way to invent a previous relationship. A request to stop needs to end the chase, including any messages you've scheduled elsewhere.


## When does a demo follow-up need a booking link?

Add a booking link when the next task requires a conversation and the recipient has enough context to decide whether to attend. Leave it out when you're delivering a document or answering a question that can be settled in the email itself.


Make the commitment visible. A 20-minute walkthrough and a 60-minute technical assessment ask for different amounts of time, so the linked event must match the duration you put in the message.


The [booking-link overview](https://meet.barq.dev/guides/what-is-a-booking-link) explains time selection. If the prospect hasn't explained their goal yet, use the [discovery call invitation emails](https://meet.barq.dev/templates/discovery-call-invitation-email) to agree the purpose before promising a product demonstration.


After a completed meeting, the [thank-you and recap wording](https://meet.barq.dev/templates/thank-you-after-meeting-email) can help distinguish agreed actions from suggestions you're making for the first time. The [meeting recap examples](https://meet.barq.dev/templates/meeting-recap-email) record decisions and named actions without requiring recipients to search an entire transcript. The [mentoring request examples](https://meet.barq.dev/templates/mentoring-session-request-email) ask for a bounded first conversation before proposing an ongoing commitment.


## What can I automate once a demo is booked?

In Barq Meet, use booking confirmations and reminders to carry joining instructions, then keep any timed follow-up broad enough to remain true without a salesperson's review. We provide editable booking emails; your account-specific demo recap still needs someone to verify the conversation.


Keep sales judgement human. Don't describe a generic scheduled follow-up as a message that knows which features the prospect used or what objections they raised.


1. Create a demo event with the duration and location your invitation promises.
2. Open "Notifications" and edit the confirmation with preparation the guest needs.
3. Review the reminder and follow-up text, then preview and send yourself a test.


We send these appointment emails through the platform with Reply-To pointing to the host. We also re-check the selected Google calendars at confirmation, so availability shown earlier can change before a guest completes a booking.


For a specialist demo, coordinate each required person's availability before sharing times; Barq Meet doesn't provide collective scheduling across a sales group. Its calendar connection is Google Calendar, so keep an Outlook-based sales calendar with a scheduler that connects to it.


Review [the booking-email settings](https://meet.barq.dev/features/emails-and-reminders) and [the included scheduling features](https://meet.barq.dev/pricing), then [create a demo event with an honest agenda](https://meet.barq.dev/app/sign-in).

## Frequently asked questions

### Should I attach a price proposal after every demo?

No. Send a proposal when you've agreed what it should cover and who needs it. If the buyer is still checking whether the product can do the job, a focused answer or a technical follow-up may be the better next step.

### Can I say the prospect loved the demo?

Only repeat feedback they gave you. A thank-you or a polite closing remark isn't agreement to buy; write down the questions they raised and the next action they accepted without inventing enthusiasm. Describe the questions, decisions and next steps they stated, keeping interpretation separate from a claim about their feelings or intent to purchase that the conversation doesn't establish and you cannot fairly attribute to them.

### What if another person needs to join the next demo?

Ask who needs to attend and what they need to decide before scheduling. Confirm the proposed time with required participants; a link to one salesperson's availability doesn't prove that everyone else is free. Agree that person's role and attendance before proposing a time, then tailor the next session's agenda instead of inviting a new stakeholder to repeat the same demonstration without explaining which decision their involvement should help make.

## Related pages

- [Booking emails with reminders before and after the call](https://meet.barq.dev/features/emails-and-reminders)
- [What is a booking link?](https://meet.barq.dev/guides/what-is-a-booking-link)
- [Discovery call invitation email templates](https://meet.barq.dev/templates/discovery-call-invitation-email)
- [Thank-you email after a meeting: templates](https://meet.barq.dev/templates/thank-you-after-meeting-email)
- [Meeting recap and follow-up email templates](https://meet.barq.dev/templates/meeting-recap-email)
- [Mentoring session request email templates](https://meet.barq.dev/templates/mentoring-session-request-email)

[Create your free booking link](https://meet.barq.dev/app/sign-in)
