# When the prospect reschedules for the third time: a moved meeting is a signal

https://salesbond.app/blog/prospect-keeps-rescheduling-pipedrive/
Published: 2026-10-06 · Updated: 2026-10-06

When a prospect keeps rescheduling, one reschedule is normal. The second asks you to change the meeting: shorter, with a written agenda, with a second person from the buyer’s side in the room. The third means you park the deal with a date you will come back on. And count the moves the buyer asks for inside the deal itself, because otherwise the calendar looks busy while the pipeline underneath it is hollow.

## The meeting that always happens next week

Vesna’s demo with Caius was set for the 9th. On the 8th he asks for the following week; a vendor audit landed on his desk, fair enough. Then it moves again: “end of quarter chaos, can we do the 24th?” Today is the 23rd and a one-liner arrives. “Can we push to early next month? Things are hectic here.” Every message is friendly. Caius has never failed to show up, because the meeting has never taken place.

In Pipedrive the deal looks fine: an activity due next month, a touch this week. The stage hasn’t changed in five weeks. The only thing that has moved is the date of the next meeting, three times, always at the buyer’s request. Nobody wrote that down. In Friday’s review, “we have a demo booked” ends the conversation.

## A reschedule is not a no-show

A no-show is a buyer who agreed to a time and did not come. A reschedule is a buyer who agreed to a time and moved it before it arrived. The first breaks a commitment; the second keeps one that is shrinking. No-shows get their own rule, written up in [what to do about demo no-shows in Pipedrive](https://salesbond.app/blog/demo-no-shows-pipedrive/), and we keep the two apart.

The no-show playbook is too harsh for a first reschedule and too soft for a third. Someone who moves the meeting is still talking to you; what they are saying changes with each move.

## First, second, third: change the ask each time

![Three steps for a rescheduled meeting: say yes and ask what changed, shorten it with an agenda and a second person, park it with a return date](https://salesbond.app/wp-content/uploads/2026/10/prospect-keeps-rescheduling-pipedrive-2.png)

1. **The first move.** Say yes, and ask one question in the same message: “What changed on your side?” You want the reason in his words, to compare with the next one. Then move the due date on the same activity (why, below). A first reschedule is a dentist, a sick child, a board meeting. Treat it as a red flag and you lose real buyers over nothing.
2. **The second move.** Say yes to a different meeting. Cut it from sixty minutes to twenty-five. Send a three-line agenda that ends with the decision Caius will be able to make when the call is over. And ask for the person he keeps mentioning: “Should Anouk join, since she signs off on this?” A buyer who takes a shorter call with Anouk in the room is busy. A buyer who wants the same hour pushed another two weeks, alone, is cooling. You won’t know which until you ask.
3. **The third move.** Do not offer a fourth slot. Park the deal, with a date.

Our rule: a meeting moves at the buyer’s request twice at most. Write it down before you need it, because in the moment every rep books the fourth slot and calls it persistence.

## Keep count in the deal, not in your head

A Pipedrive activity keeps its due date (the scheduled slot) and its marked-as-done time apart ( [Pipedrive: activity marked-as-done logic](https://support.pipedrive.com/en/article/activity-marked-as-done-logic)). When Caius asks for the 24th Vesna moves the due date. The help article doesn’t describe a counter of reschedules or a history of earlier due dates, so after the edit the activity reads as if it had always been set for the 24th.

Why not create a new activity for each new date, as our no-show article does when a prospect rebooks? There the old activity becomes a No-show, an event that happened and gets counted. A meeting moved before the day never happened. Mark the old Demo done and it enters the no-show rate as a demo that took place. So for buyer reschedules: one activity, moved, with the count written on it.

The counter goes into the activity subject, visible in the list view without opening anything. The reasons go into a note on the deal, in the buyer’s words:

```
Subject: Demo · Caius · moved x2 (buyer)
Note: Sep 9 → Sep 16: vendor audit.
          Sep 16 → Sep 24: "end of quarter chaos".
```

The reasons matter more than the count. “Legal, then procurement” is a deal moving through a company. “Hectic” twice in a row is a deal moving nowhere. If you record an [Outcome on every activity](https://salesbond.app/blog/pipedrive-activity-outcome-field/), leave it alone here: a moved meeting has no outcome yet.

Then one look a week. On Monday, type “moved x2” into the Pipedrive search bar and read what comes back. Search covers activity names, notes and descriptions, but regular users only find their own activities, while admins find everyone’s ( [Pipedrive: search](https://support.pipedrive.com/en/article/search-finding-what-you-need)), so the team-wide look is an admin’s job. Every hit needs a different ask than the the last one. If [the close date got pushed](https://salesbond.app/blog/pushed-close-dates-pipedrive/) on top of the moved meeting, that’s a second signal; count it separately.

## Park it with a date, not a goodbye

On the third request, Vesna doesn’t send a calendar link. She writes: “Caius, I’ll take the demo off the calendar rather than move it a third time; this clearly isn’t the month. I’ll come back to you the week of October 13. If the audit wraps up earlier, the link below books twenty-five minutes with me.”

No fourth slot. A date Vesna chose. An open door, with the effort now on his side. It isn’t a breakup email; the buyer has done nothing wrong except run out of time.

In the deal, the same activity moves to the return date with the subject “Parked until Oct 13 (moved x3, buyer)”. It stays open, not marked done. The deal doesn’t go to lost; that’s the no-show rule. Whether it stays in it’s stage or steps back one is your team’s call, but it leaves this month’s forecast either way. [Stalled is not the same as dead](https://salesbond.app/blog/stalled-deals-vs-dead-deals/), and the parking date tells you which one you have without guessing.

A disclosure: we build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. Deal Health checks every deal against the rules a team has switched on and explains each violation in plain words. The reschedule counter above is our convention, not a product feature. [Check your CRM with SalesBond](https://salesbond.app/).

## One sentence for Friday’s review

Replace “we have a demo booked” with this: “The buyer has moved it twice; the next one is twenty-five minutes with Anouk in the room, or we park it until mid-October.” Same four seconds. It just happens to be true.