Demo requested,nothing booked.

It is rarely the offer and rarely the team. It is timing. The people who work inbound leads also do other work, so at the moment a request lands they are on a call, in a demo or in another queue. The common patterns:

• The form has no calendar. The lead asked for a demo and is waiting for someone to suggest a time.
• The calendar was shown and they left. They meant to pick a slot later and did not.
• The reply went to a shared inbox. Everyone assumed someone else had it.
• Follow-up depends on someone remembering. The first touch happens. The second is late, the third never happens, and a few weeks later nobody has heard from them.

Instant scheduling tools fix the first two for leads who are ready to choose a time there and then. This guide is about everyone else: the people who asked and then did not book.

Before buying or building anything, take your last 50 demo requests and fill in five columns for each one:

It takes an afternoon and usually settles the argument. If replies are fast but most leads got one or two touches, your problem is follow-up, not speed. If they book but do not turn up, start with reminders.

1. 01At once: reply by email, and by WhatsApp or SMS if they gave a number for it. From a named person, about what they actually asked for, with a booking link. Invite them to reply with what they are trying to fix. If you plan to call, say so in one line, so the call is expected rather than a surprise.
2. 02Check the request against your own rules, in parallel. Spam out, then fit against criteria you have written down. Never let this delay the reply, and never count "we could not find them online" against a lead.
3. 03Wait about 2 minutes. Some of them are already picking a slot. A call that lands while someone is booking interrupts the exact thing you wanted them to do.
4. 04If they have not booked, make one personal contact. A call from a rep, or from an AI assistant that says what it is in its first sentence, only to people who asked to be contacted. Its one job is to answer simple questions and find a time.
5. 05No answer: a short text about 10 minutes later. Skipped if the call connected, with the booking link.

For a “call me now” button the wait in step 3 can be zero. For a contact form, a couple of minutes works well.

Most of the leak is here. Most teams send one or two messages and stop. These are the defaults we run, timed from the request:

The rules matter more than the exact timings:

• One channel per step. Never an email, a text and a call in the same minute.
• Stop the moment they book, reply or say stop, on every channel at once. A reply goes to a person, so nobody who has just answered gets an automated message an hour later.
• Respect their hours. We send between 8am and 8pm in the lead's own time. A message that falls due at 3am moves to the morning; it is never quietly dropped.
• Cap it. No more than two follow-ups a day to one person.
• A different track for poor fits. People who do not meet your criteria still get a helpful reply and a couple of useful emails, not calls.

Use the channel they gave you and agreed to, and vary it. Email alone is the easiest to ignore, a call reaches people who meant to book and forgot, and WhatsApp or SMS gets read on the move. We do not yet have measured reply rates by channel across enough companies to rank them, and we would rather say so than quote a number we cannot show. We will publish them when we can.

A booked demo is not a held demo. After a booking we send:

• a confirmation straight away, by email and WhatsApp
• a short note an hour later on what the call will cover
• a reminder the day before, and another an hour before
• a message to rebook if they cancel, instead of silence

And give the rep a short brief on the lead before the call, so nobody starts cold.

You can do part of it with what you already have:

• Your CRM (HubSpot, Salesforce and others) can send the first email, create tasks and run an email sequence. Where they usually stop short: several channels in one sequence, stopping every channel when the lead replies on any one of them, calls, and timing to the lead's own hours.
• A scheduling tool on the form catches the leads who are ready to book there and then.
• A rota where one person owns new requests each day closes the shared-inbox gap at no cost.
• Building it yourself in a workflow tool such as n8n is realistic if someone technical will own it. Budget more time for what goes wrong than for the build: the stop list, messages that fail silently, and phone numbers in the wrong format.
• Having it installed makes sense when nobody internally has the time to run it and keep it working.

Deciding between another hire and automation? Read Hire another SDR or automate inbound?

Record every step for every lead (replied, qualified, called, booked, showed) as it happens, rather than overwriting a status field. Then you can see exactly where each lead stopped. Two rules keep the numbers honest:

• Anything not yet measured shows as “not measured”, never as 0.
• When a message is not sent, record why, and whether the failure was on the lead's side (no number, opted out) or yours (a channel not set up). Otherwise your own setup problems look like bad leads.

Plain summary, not legal advice. Check your own setup with a legal adviser; the ICO publishes guidance on electronic marketing and calls.

• Contact only people who asked to be contacted, about what they asked for.
• Record what they agreed to, for each channel, when they agreed.
• If an AI makes the call, it says so in its first sentence.
• Honour “stop” on every channel at once, including for messages already scheduled.
• Keep call recordings and transcripts only as long as you need them, and say that you keep them.

• Fewer than about 50 demo requests a month. One person with a checklist and the sequence above can usually keep up by hand.
• The leads are cold. More follow-up does not create intent in people who never asked.
• Booked demos are not being held, or nobody follows up after the demo. Fix that first, because it is where you have already won the lead.