When and How to Send Meeting Reminders (and What to Do Differently for Accepters vs. Non-Responders)
Sending meeting reminders sounds simple. Pick a time before the meeting, send a note, done.
But the right reminder strategy actually depends on who you're sending to. Reminding someone who already accepted is different from reminding someone who hasn't responded — different timing, different tone, different goal. Get this wrong and you either annoy the people who already showed up for you, or fail to convert the people who didn't.
Here's a practical framework for who to remind, when, and how — plus how CalNudge handles the automation if you don't want to do it manually.
Two completely different problems
Before tactics, the framing:
Reminders to non-responders are about getting a decision. Someone who hasn't responded is a question mark. Your reminder needs to convert them into an Accept or Decline so you can plan.
Reminders to confirmed attendees are about ensuring they show up. Someone who already accepted is mostly a known quantity — you just need to make sure the meeting hasn't fallen off their radar in the days since they accepted.
These goals are different. The reminders should be too.
Reminders for non-responders
This is where most of the pain is. People who haven't RSVP'd are the ones who break your meeting planning. They might attend, they might not — you have no idea.
### When to send
The optimal cadence for non-responders is staggered, not single:
- 7 days before: Initial reminder. Surfaces the invite again while the recipient still has flexibility to plan around it.
- 48 hours before: Mid-cycle nudge. By this point, most people are reviewing their week ahead and can act on it.
- 24 hours before: Final reminder. The meeting is now urgent enough that "I'll deal with it later" stops working.
For meetings scheduled with less than 24 hours notice (which happens often), a single reminder ~3-6 hours before the meeting is more appropriate than the staggered sequence.
The key principle: reminders should stop the moment they respond. If they respond after the 7-day reminder, don't send the 48-hour and 24-hour ones too. That's nagging.
### What to say
Non-responder reminders should be short, friendly, and direct. They shouldn't apologize for the reminder or over-explain. A good template:
> Hi Jamie,
>
> Just a friendly heads-up — you haven't responded to a meeting invitation from Mike Vanderslice:
>
> 📅 Q2 Planning Review
> 🕐 Friday, May 8, 2026 at 10:00 AM
>
> How to respond: Open your calendar app, find this event, and click Accept or Decline. You can also reply directly to this email.
>
> Thanks!
The whole message is under 10 lines. The action is one click. The tone is helpful, not accusatory.
### What NOT to say
- Don't guilt-trip ("I noticed you still haven't responded...")
- Don't escalate language ("URGENT: Please respond")
- Don't include long meeting descriptions or pre-reads in the reminder itself
- Don't send from a noreply system address — make it feel personal
Reminders for confirmed attendees
Different problem entirely. These people said yes. Your job isn't to convert them — it's just to keep the meeting on their radar.
### When to send
For most meetings, a confirmed attendee doesn't need any reminder beyond the one their calendar app gives them automatically (typically 10-15 minutes before).
The exceptions:
- Important meetings (interviews, demos, big decisions): A 24-hour reminder with the agenda or pre-reads attached is welcome. People preparing for important meetings appreciate the prompt.
- Meetings scheduled weeks in advance: A 24-48 hour reminder helps them re-orient. The meeting may have been on their calendar for 3 weeks — they need to remember it's tomorrow.
- External attendees (clients, candidates, vendors): They may not have your calendar in their primary view. A friendly day-before email keeps you top of mind.
### What to say
Reminders for confirmed attendees should add value, not just remind. The format:
- Brief context ("Looking forward to our chat tomorrow about X")
- Any pre-reads or links they need
- Logistics confirmation (Zoom link, address, dial-in)
- An out — *"if anything's changed, just let me know"*
The goal is to make their experience smoother, not to verify they're coming. If you're sending a reminder to a confirmed attendee that just says "are you still coming?" — you're undermining their commitment.
Reminders for tentative / maybe responses
Tentatives are interesting. The person engaged with the invite (good) but didn't fully commit (bad). They might attend, they might not.
### How to handle them
Treat tentatives more like non-responders than accepters:
- 48 hours before: Send a polite reminder asking if they can confirm. *"Hey Jamie, I noticed your RSVP is Tentative for Friday's meeting. Any chance you can confirm one way or the other so I can plan?"*
- 24 hours before: If still tentative, plan for them to be absent. Adjust agenda or attendee list as needed.
The mistake here is treating tentatives as "probably yes." They're not. The whole point of clicking Tentative is to communicate uncertainty. Take that signal seriously.
Reminders for declined invites
This sounds counterintuitive but: in some cases, you should remind people who declined.
### When to send
If a key person declined and the meeting can't function without them:
- Within an hour of decline: Acknowledge it kindly and ask if there's a better time. *"Hey Jamie, totally understood you can't make Friday — would Monday or Tuesday work instead?"*
- 24 hours before: If they declined a recurring meeting, periodically check whether their decline is still right. Their schedule may have changed.
For meetings where the declined person's absence isn't critical, no reminder is needed. They said no — respect it.
The manual approach
If you're doing this by hand, the basic process for each meeting:
1. Glance at the attendee list a week before the meeting
2. Manually email or Slack non-responders a polite reminder
3. Repeat at 48 hours and 24 hours before, but only for people still unresponded
4. For tentatives, send a confirm-please note 48 hours before
5. For confirmed attendees, send a separate, value-add reminder if the meeting is high-stakes
6. For declined-but-critical attendees, follow up about rescheduling
The problem: this is a lot. For 5+ meetings a week, manually managing this for each meeting takes 30-60 minutes weekly. Most people skip it after the first week.
The automated approach
This is exactly what CalNudge automates. Once you connect your Google Calendar or Outlook, CalNudge:
1. Watches every meeting you organize — automatically, no per-meeting setup
2. Sends reminders to non-responders at 7 days, 48 hours, and 24 hours before
3. Stops automatically when they respond — no continued nagging
4. Sends reminders from your name — recipients see it as coming from you, not from a system
5. Delivers a daily digest so you wake up knowing who's confirmed for your week ahead
6. Optionally sends post-meeting feedback surveys to attendees so you can learn what's working
The current CalNudge focus is on non-responders specifically, since that's where most of the pain is. We're evaluating whether to add reminders for confirmed attendees and tentatives as a future feature based on user requests — if that would help you, let us know.
A simple decision tree
For every meeting you organize, the reminder decision tree looks like this:
```
Did this person respond?
├── No → Send polite reminder at 7d, 48h, 24h. Stop the moment they respond.
├── Tentative → Ask for confirmation 48h before.
├── Accepted (low-stakes meeting) → Don't send anything. Calendar's auto-reminder is enough.
├── Accepted (high-stakes meeting) → Send 24h-before email with agenda/pre-reads.
└── Declined (critical attendee) → Ask about rescheduling within an hour of decline.
```
That's the whole framework. Most teams only do the first row consistently — and even doing just that one well (manually or via automation) typically improves attendance by 20-30%.
Frequently Asked Questions
Should I send reminders for every meeting?
For non-responders: yes, every meeting. For accepted attendees: only for high-stakes or external meetings. For most internal meetings, the calendar's automatic 10-minute-before reminder is enough.
What's the right reminder timing?
For non-responders, send at 7 days, 48 hours, and 24 hours before the meeting. This staggered cadence catches people at different planning horizons. Stop the moment they respond — don't send the next reminder if they've already RSVP'd.
Can I automate meeting reminders?
Yes. Tools like CalNudge connect to your Google Calendar or Microsoft Outlook and automatically send reminders to non-responders without per-meeting setup. The reminders come from your name, so recipients see them as personal nudges rather than system notifications. Free Forever with unlimited active events; Pro adds custom reminder timing.
Stop chasing RSVPs manually.
CalNudge automatically follows up with attendees who haven't responded — so you always know who's coming.
Get started free →