Demo request email templates: 5 first replies that book the meeting

The first reply to a demo request should go out within minutes and ask for exactly one thing: a yes to a specific time. Speed matters because, in a Harvard Business Review study of 1.25 million leads, firms that tried to reach a lead within an hour were nearly seven times as likely to qualify it as firms that tried an hour later. Below are five reply templates across email, SMS and WhatsApp, with timings and the reason for every line.

• The rule: the One-Ask Rule. Every message in the sequence asks for one thing the buyer can answer in a word: “Tue” or “Wed”, “1” or “2”, “now” or “later”.
• The sequence: instant email with two proposed times (0–2 minutes), SMS bump (about 5 minutes, only with consent), WhatsApp where the buyer opened the chat, a one-question email at 24 hours, and a close-the-loop email on day 4.
• The sender: the named person who will run the demo, never a noreply address.
• The metric: booked-meeting rate per template = demo requests that book a held meeting within 7 days ÷ demo requests that received that template.
• The catch: at a 30% booking rate you need about 356 demo requests per template to see a 10-point difference with confidence. Test big changes, not wording.

How do I reply to a demo request so it turns into a booked meeting?

A demo request reply works when it converts intent the buyer already has into a calendar event, and nothing else. The buyer qualified themselves on the form. The reply’s only job is to make saying yes to a time take less effort than closing the tab.

That is the One-Ask Rule: every message makes one request, phrased so the answer is a single word. “Let me know a time that works for you” fails the rule, because it hands the buyer a scheduling task. “Tuesday 10:00 or Wednesday 14:30?” passes it. A calendar link sits underneath as the fallback, not the ask. The trade-off between a link and a call-back is covered in detail on our page about whether to send a calendar link or call leads back; this page is about the words.

A demo request reply that asks for one specific time gets a one-word answer; a reply that asks the buyer to find a time gets a task.

The five demo request reply templates, with timings

The five templates run as one sequence; each fires only if the previous one did not produce a booking.

Template 1: the instant email (0–2 minutes)

Subject: Your {Product} demo: Tuesday 10:00 or Wednesday 14:30?

Hi {first_name},

Thanks for asking for a demo. You mentioned {their words from the form}, so I’ll build the 30 minutes around that rather than the standard tour.

I can do Tuesday at 10:00 or Wednesday at 14:30 ({their time zone}). Reply “Tue” or “Wed” and I’ll send the invite. If neither suits, any open slot is here: {calendar link}.

{Name}, {role}, {Product}

Why each line: the subject line carries the ask, so a buyer can answer from the inbox preview. Quoting their form text proves a person read it. Two times, inside the next two working days, in the buyer’s own time zone, turn the decision into a one-word reply.

Template 2: the SMS bump (about 5 minutes)

Hi {first_name}, it’s {Name} from {Product}. Just emailed two demo times: Tue 10:00 or Wed 14:30. Reply 1 or 2 and I’ll lock it in. Reply STOP to opt out.

Why: it points back to the email instead of repeating it, keeps the same two times so the buyer is never choosing between offers, and carries an opt-out. Send it only where the form collected a phone number with consent to text; the consent and registration rules differ by country, and in the US the sending number needs registration, as our A2P 10DLC guide explains.

Template 3: the WhatsApp reply (where the buyer opened the chat)

Hi {first_name}, {Name} from {Product} here. Thanks for the demo request. Would Tuesday 10:00 or Wednesday 14:30 suit? If you’d rather see it straight away, I can do a 10-minute call now.

Why: WhatsApp suits buyers who reached you through a click-to-WhatsApp button or a regional site where it is the default channel. On the WhatsApp Business Platform, a buyer’s message opens a 24-hour customer service window for free-form replies; outside it, only pre-approved template messages can be sent. A reply sent within minutes stays inside that window.

Template 4: the one-question email (+24 hours)

Hi {first_name}, one question before I hold a slot: is {their problem} something you’re fixing this quarter, or are you mapping options for later? Either is fine. It changes what I’d show you.

Why: by day two, a second set of times reads as pressure. A question about timing is easier to answer than a calendar, and the answer sorts the buyer: “this quarter” gets two new times, “later” gets template 5 and a recorded walkthrough.

Template 5: close the loop (day 4)

Hi {first_name}, I haven’t found a time with you, so I’ll stop chasing. If a demo is still useful, reply “demo” whenever you’re ready and I’ll send two times. Meanwhile, here is a 4-minute recording of {the use case they named}: {link}.

Why: it ends the sequence with an exit the buyer controls, and the recording serves the buyer who wanted to look rather than talk. Leads who go quiet after this are a different problem; our guide to following up leads who ghosted picks up from here.

Which demo request reply fits which kind of request?

The form fields decide which variant of template 1 a demo request gets, and routing that decision automatically is what lets the reply go out in two minutes.

The out-of-hours row is the one teams get wrong most often, because the email can go at midnight but a text cannot.

What should a demo request reply never include?

Most demo request replies lose bookings through additions, not omissions. Five things to remove:

1. A qualification questionnaire. The form already asked. A second form between the buyer and the calendar is a second chance to leave.
2. “Let me know what time works.” It fails the One-Ask Rule and starts a scheduling thread that can run for days.
3. A deck or PDF attachment. It invites the buyer to self-evaluate instead of meeting.
4. A noreply or generic sales@ sender. The buyer cannot reply with “Tue”, which is the whole mechanism.
5. A calendar showing three weeks of availability. Offer the next two working days first.

How do I know which demo request template books more meetings?

Track booked-meeting rate per template as an experiment, because no credible public benchmark exists for it. We looked for a published booking rate for B2B demo requests on a stated denominator and did not find one we could verify, so this page does not print one. Measure your own: demo requests that book a meeting which is then held within 7 days, divided by demo requests that received the template.

The hard part is sample size. The table shows how many demo requests each template needs before a difference is real, at 95% confidence and 80% power (standard two-proportion test). The baseline rates are assumption bands; use your own.

Worked through: at 50 demo requests a week split between two templates, each template gets 25 a week. Reaching 356 each takes 712 requests, or 14.2 weeks. A 5-point gap would take over a year. That is why the practical rule is to test changes big enough to move the rate by 10 points or more: two proposed times against “pick a slot”, a 5-minute SMS against none, an instant reply against a 2-hour one.

What does running these demo request templates yourself cost?

Writing the five templates takes an afternoon, and loading them into a CRM sequence with the routing rules above takes a working day or two, depending on your stack (our estimates). The running cost is the part teams underestimate: the sequence only works if someone books the slot within minutes of a “Tue” or a “1” coming back and covers evening and weekend replies.

Assume 10 minutes of human time per demo request across replies, rescheduling and CRM notes (an assumption to replace with your own). At 20 requests a week that is about 3.3 hours, which a founder or account executive can absorb. At 100 a week it is about 16.7 hours, close to half a person, and the replies arrive at random times. Above that point the choice is a dedicated coordinator, automation that books from the reply, or a service that runs the conversation. LeadsNow’s AI appointment setting handles that conversation by AI calling, SMS and messaging, the method behind its 50,769+ AI-booked sales appointments since 2017; our speed-to-lead automation page shows how the instant first touch is set up.

Frequently asked questions

How quickly should I reply to a demo request?

Within minutes, and certainly within the hour. In the study reported by Harvard Business Review in 2011, covering 1.25 million leads at 42 US companies, firms that tried to contact a lead within an hour were nearly seven times as likely to qualify it as firms that tried an hour later. An automated first email at 0–2 minutes, sent from a named person, is the simplest way to hit that.

Should a demo request reply include a calendar link?

Yes, as a fallback under two proposed times, not as the main ask. Two named times let the buyer answer in one word from their inbox; the link serves buyers who prefer to choose their own slot.

What should the subject line of a demo request reply say?

Put the ask in the subject line: “Your {Product} demo: Tuesday 10:00 or Wednesday 14:30?”. A buyer can then reply from the inbox preview without opening the email, and the subject tells them it is about the request they just made.

Can I reply to a demo request on WhatsApp?

Yes, if the buyer opened the WhatsApp conversation or opted in to WhatsApp messages. On Meta’s WhatsApp Business Platform, a user’s message opens a 24-hour customer service window in which free-form replies are allowed; outside it, only pre-approved template messages can be sent.

What is a good booking rate for demo requests?

We have not found a credible public benchmark on a stated denominator, so measure your own: demo requests that book a held meeting within 7 days, divided by demo requests received. At a 30% rate, you need about 356 requests per template to detect a 10-point improvement.