# Demo no-shows in Pipedrive: how to measure them and what to change first

https://salesbond.app/blog/demo-no-shows-pipedrive/
Published: 2026-10-02 · Updated: 2026-10-26

A demo no-show is a metric, not bad luck. Record it on the Pipedrive activity itself, read the no-show rate by lead source and by how far ahead the demo was booked, fix the booking window and the confirmation step first, and after the second no-show close the attempt under a rule the team agreed in advance.

## The meeting that “happened” in the calendar and never in the call

Thursday, 2 pm. The rep opens the video link, waits twelve minutes, sends the “looks like we missed each other” email, and goes back to work. The Pipedrive activity sits there with its green checkmark, because the rep marked it done to clear the list. The deal moves on. Nobody records that the demo did not take place.

Three weeks later the manager runs the pipeline review and finds a deal in Demo scheduled whose last activity is the meeting that never happened. They ask the rep. The rep says the prospect went quiet. That’s a different problem with a different playbook, and we wrote it up in [what to do when the prospect goes silent after the demo](https://salesbond.app/blog/prospect-went-silent-after-demo/). What the manager is looking at is a no-show that was never written down as one. And what was never written down can’t be counted.

And [a prospect who keeps moving the meeting](https://salesbond.app/blog/prospect-keeps-rescheduling-pipedrive/), without ever missing it, is a third case with its own rules.

## Why it is a pipeline problem, not an SDR problem

Almost everything published on demo no-shows is written for SDR teams: reminder cadences, rebooking templates, a script for the “sorry I missed it” call. Useful if you have an SDR. If you run sales on a six-person team, though your problem sits before and after the rep in the empty call. Before: a demo set eleven days out with nobody confirming it is a different event from one set for tomorrow afternoon, and a demo booked off a cold outbound reply differs from one a buyer requested through the pricing page. Lump them together and you can’t see which process is leaking. If an outside [appointment setter books your demos](https://salesbond.app/blog/outsourced-appointment-setters-pipedrive/), read the no-show rate by setter as well as by lead source. (How fast the lead was touched in the first place is its own measurement, covered in [speed to lead in Pipedrive](https://salesbond.app/blog/speed-to-lead-pipedrive/).)

After: every uncounted no-show is a deal that looks alive and isn’t. It carries its value into the forecast, sits in the Demo stage with a recent activity date, and survives the weekly review because “we have a demo booked” is the most reassuring sentence in sales. Like [tire-kickers](https://salesbond.app/blog/tire-kickers-in-your-sales-pipeline/), it inflates the pipeline with buyers who have committed nothing. That is why we treat the no-show as a pipeline hygiene event the manager owns, with the rep’s follow-up as one part of the response.

## Count it: one activity outcome, one rate, two cuts

An activity in Pipedrive carries a type, a due time and a marked-as-done time. A Demo activity marked done looks the same whether the call was held or not, so the type field is where the team records it. In short, [booked is not held](https://salesbond.app/blog/hubspot-meetings-booked-call-deal-activity-check/). The convention below uses only those documented fields.

![Flow: a Demo activity is either held and marked done, or becomes a No-show and is rebooked as a new Demo activity](https://salesbond.app/wp-content/uploads/2026/10/demo-no-shows-pipedrive-2.png)

1. Create two custom activity types, “Demo” and “No-show”. In Pipedrive that’s Settings > Company settings > Activities, then “+ Activity type” ( [Pipedrive: creating custom activity types](https://support.pipedrive.com/en/article/creating-custom-activity-types) ). Only a global admin can do it, which on a small team is usually the manager. Fine: it’s a management convention.
2. Book every demo as a Demo activity linked to the deal. A deal-linked activity is automatically linked to that deal’s person and organization ( [Pipedrive: activities](https://support.pipedrive.com/en/article/activities) ), so the link is made once. When the prospect books through a Pipedrive Scheduler link, booking creates the activity for you ( [Pipedrive: Scheduler](https://support.pipedrive.com/en/article/scheduler) ); the rep just makes sure its type is Demo. When the time was agreed on a call, the rep creates it before hanging up.
3. Demo happened? Mark it done. Nothing else.
4. Nobody showed? Don’t delete the activity, and don’t just mark it done. Open it, change the type from Demo to No-show (type is one of the editable activity fields, [Pipedrive: bulk editing and filtering](https://support.pipedrive.com/article/bulk-editing-and-filtering) ), then mark it done. The due date keeps the original slot unless someone edits it, and the marked-as-done time records when the rep closed it out ( [Pipedrive: activity marked-as-done logic](https://support.pipedrive.com/en/article/activity-marked-as-done-logic) ). You lose nothing and gain a countable event.
5. If the prospect rebooks, create a new Demo activity rather than moving the old one. The new one gets its own add time, so the booking window of the second attempt is measured honestly, and the first attempt stays on record as a No-show.

Now the rate. **Demo no-show rate = No-show activities done in the period ÷ (No-show + Demo activities done in the period).** Both counts come from the Activities list view with the filter Activity > Done > is > Done plus a date range ( [Pipedrive: how can I see done activities?](https://support.pipedrive.com/en/article/how-can-i-see-done-activities)), or from an Insights activities performance report, which filters and segments by activity type, deal, due time and marked-as-done time and exports to a spreadsheet ( [Pipedrive: Insights reports, activities performance](https://support.pipedrive.com/en/article/insights-reports-activities-performance)).

One number on its own is a mood. Two cuts turn it into a decision.

The first cut is lead source. The activity doesn’t carry the source, the deal does. Export the report table with the Deal column, export the deals with whatever field holds your lead source, and match them in a spreadsheet. At five to fifteen demos a week that’s a ten-minute job once a month. You’re looking for the source that is clearly out of line with the others, not for decimal places.

The second cut, booking window, is the one that most often changes behavior, because the team controls it directly. For each Demo and No-show activity, subtract add time from due time; both fields are in the the activities report and its export ( [same Insights article](https://support.pipedrive.com/en/article/insights-reports-activities-performance)). Group into same or next day, two to seven days, and more than a week.

A worked example with invented numbers, just to show the shape:

| Booking window | Demos held (Demo, done) | No-shows | No-show share |
| --- | --- | --- | --- |
| Same or next day | 21 | 3 | 12.5% |
| 2 to 7 days out | 26 | 5 | 16.1% |
| More than a week out | 10 | 6 | 37.5% |

These aren’t benchmarks or customer figures, just the kind of table the export produces. If you already track activity counts, this slots into the same read; see [which sales activity metrics a small team should keep](https://salesbond.app/blog/sales-activity-metrics-small-team/) for how we keep that list short.

What about published benchmarks? SnapSDR, for one, puts the average demo no-show rate at 20 to 35 percent and demos booked eight or more days out at 23 to 47 percent ( [SnapSDR, March 2026](https://www.snapsdr.com/blog/how-to-deal-with-demo-no-shows)), with no source or method given, and other pages quote ranges that disagree. The direction is plausible. But a number with no method can’t tell you whether your rate is good or bad. Compare internally instead: this month against last, inbound against outbound, booked within two days against booked two weeks out.

## Reduce no-shows by changing one thing first

Resist fixing everything. Pick the cut that is most out of line, change the one input that feeds it, and read the number again a month later. Change two things at once and you won’t know which one worked. Here are three candidates, in the order we’d try them.

**Booking window.** If “more than a week out” is the ugly row, shorten the offer. If the team books through Pipedrive’s Scheduler, narrow the dates and time frames the link offers ( [Pipedrive: Scheduler](https://support.pipedrive.com/en/article/scheduler)); that’s a settings change, nothing more. For demos agreed on a call, our rule for reps is simple: offer two slots inside the next three working days before offering anything further out. Buyers who want next month can have it, but they ask for it. Demos [booked through a scheduler link](https://salesbond.app/blog/pipedrive-meeting-scheduler-booked-meetings/) create the activity without a rep touching it, so check how those bookings are recorded before you read the no-show rate.

**Confirmation.** If no-shows are spread evenly across windows, the likelier problem is that nobody touches the meeting between booking and start. Send one confirmation the working day before, from the rep rather than the calendar tool, with one question that needs an answer (“will Dana be joining, or should I send her the recording?”). A buyer who answers is going to show. A buyer who doesn’t has told you something a day early, and the rep can offer to move the slot. Getting that reminder onto the rep’s list is covered in [our piece on Pipedrive activity reminders](https://salesbond.app/blog/pipedrive-activity-reminders/).

**Qualification.** If one source produces most of the no-shows and the other two fixes haven’t moved it that source is sending people who were never going to buy. Add one qualifying question before a demo is offered from it, or route it to a [short discovery call](https://salesbond.app/blog/discovery-call-small-team-pipedrive/) instead of a full demo. It’s the slowest fix to show up in the numbers and the most argued-over, which is why it comes third.

## After the second no-show: a rule, a stage and a lost reason

The first no-show gets a rebook. The second one needs a rule, written before it happens, because in the moment every rep will argue for a third try and will usually be wrong.

Ours reads like this: *after two No-show activities on the same deal, the rep sends one closing message offering a slot within the next five working days and saying the deal will be closed if there is no reply. No reply inside five working days: mark the deal lost with the reason “No-show x2”.* No third demo is booked unless the buyer books it themselves. That’s shorter than the follow-up we suggest when a prospect [goes silent after a demo that did happen](https://salesbond.app/blog/prospect-went-silent-after-demo/), and on purpose: here the buyer has already skipped the meeting twice.

The lost reason needs its own entry. “Went silent” and “No response” are already on most teams’ lists and they hide the pattern; a separate “No-show x2” lets you count, a quarter later, how many deals died this way and from which source. Setting up the list without bloating it is in [our guide to lost reasons in Pipedrive](https://salesbond.app/blog/pipedrive-lost-reasons/), and [when a deal should be closed lost](https://salesbond.app/blog/when-to-close-a-deal-lost/) covers the argument you’ll have with the rep.

While the rule plays out, move the deal back to the stage before the demo was booked. The pipeline report stays honest for those five days, and if the buyer replies, moving it forward takes two seconds.

The rep gets something too. Closing a deal under a pre-agreed rule is no mark against them, its the convention doing its job. If the buyer comes back, you pick it up again, and some do. What the deal can’t do is sit in the forecast for six weeks pretending to be a meeting.

A disclosure, since this is where tooling comes in: we build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. One of the things it flags for the manager is a deal with no next activity scheduled, with the reason written out. It can’t know a demo was a no-show unless the rep recorded it, which is why the convention comes first. If you want to see your pipeline through that lens, [check your CRM with SalesBond](https://salesbond.app/).

Start with the two activity types this week; the first monthly read will tell you more about your booking process than any benchmark post.