Every team running cold calendar invite outreach tracks two outcomes. Accepted goes in the win column. Declined goes in the loss column. Everything else is noise.
Except one of the “everything else” answers is not noise at all. It is the prospect telling you something specific, and most teams either ignore it or treat it as a yes.
A tentative response, the Maybe button in most calendar clients, is a prospect who opened your invite, read it, thought about it, and chose not to say no. That is more engagement than most cold emails ever get. It is also not a meeting. The gap between those two facts is where a surprising number of booked-looking meetings quietly die.
This post covers what a tentative actually is at the protocol level, what it usually means in practice, and the follow-up that converts it.
What Tentative Is, Technically
A calendar invite is an iCalendar event, and every invitee on it carries a participation status. The main values are needs action, accepted, declined, tentative and delegated. When a prospect does nothing, their status stays at needs action. When they click Maybe, the client sends a reply back to the organizer setting their status to tentative.
Three details matter for outreach.
The event stays on their calendar. Unlike a decline, a tentative keeps the meeting in place. In most clients it renders differently, often hatched or faded, but it is there. The prospect will see it on the day.
The time is usually not blocked as busy. Many calendar clients treat a tentative event as tentative availability rather than a firm booking. That means a colleague can book over it, and the prospect’s own scheduling tools may treat the slot as open. Your meeting is on the calendar but not defended.
A tentative can carry a note or a counter-proposal. Google Calendar and Outlook both let an invitee respond Maybe and propose a new time, or add a comment. Those replies are the most valuable messages in the whole channel, and they sometimes land in a shared inbox nobody watches.
It also helps to know what a tentative is not. A prospect who never responds is not tentative. Some clients let a user accept or decline without sending a response to the organizer, so silence on your side does not always mean silence on theirs. Tentative is an active answer they chose to send you.
What a Tentative Usually Means
You cannot read minds from a status field, but the patterns are consistent enough to plan around. A tentative usually falls into one of four cases.
1. Interested, time is the problem. They want the conversation but the slot is awkward: a recurring meeting nearby, travel, an end-of-quarter crunch. This is the best case and the most common one when the invite was relevant.
2. Interested, not the right person. They think the topic is worth a meeting but someone else on their team should probably be there. They are holding the slot while they decide whether to forward it.
3. Curious, not committed. They are not sure the meeting is worth their time. Maybe is a polite way of keeping the option open without making a promise. These prospects need one more reason.
4. Defaulting. Some people click Maybe on everything they did not create themselves, as a way of acknowledging an invite without committing. You will learn to recognise these accounts by role and seniority. Busy executives and their assistants do it often.
Notice that only one of the four is close to a held meeting, and even that one needs a new time. Treating every tentative as a soft yes is how pipeline reports end up full of meetings that never happen.
Why Tentatives Leak
If tentatives are so engaged, why do so many of them turn into no-shows?
Because a tentative meeting has every structural weakness at once. The slot is not defended, so it gets booked over. The prospect has not committed, so there is no social cost to skipping it. The rep often does not notice it, because the CRM sync maps tentative to “pending” or to “accepted”, and either way nothing triggers a follow-up. And if the prospect proposed a new time, that proposal may sit unanswered while the original slot comes and goes.
The meeting fails silently. On the day, the rep joins, waits, marks a no-show, and concludes the prospect was never serious. In reality the prospect told you days earlier that the time did not work, and nobody answered.
The Follow-Up That Converts a Tentative
The rule is simple: a tentative deserves a human reply within one business day, and the reply should make it easy to firm up or move the meeting.
Step 1: Check for a note or a proposed time first
Before writing anything, look at the response itself. If they proposed a new time, take it. Update the event to their time rather than sending a second invite, so there is still only one event on their calendar. If they left a note, answer the note.
Our guide to rescheduling or cancelling a cold calendar invite without losing the meeting covers what each kind of edit does on the prospect’s side.
Step 2: If there is no note, ask one question
Keep it short and give them an easy way to say what is going on. Something like:
Saw you marked Thursday as a maybe, thanks for keeping it on the calendar. Is the time the problem, or would someone else on your team be better placed for this? Happy to move it either way.
That single message covers cases one and two directly. The prospect who has a time problem tells you, and the prospect who wants to forward it now has permission to.
Step 3: Offer two specific alternatives
If they say the time is the issue, offer two concrete slots rather than an open “when works for you”. Concrete options get answered. Open questions get postponed.
Step 4: For the curious, add one reason
If there is no reply after a couple of days, send one more short note with a single specific reason the meeting is worth their time, tied to whatever signal led you to invite them. Do not resend the invite. It is already on their calendar.
Step 5: Confirm the day before
Tentative meetings need a reminder more than accepted ones do. A short confirmation the day before, ideally one that asks them to reply or update their response, turns a maybe into a yes or frees the slot. Either outcome is better than an empty room. The approach in our post on reducing no-shows for meetings booked with cold calendar invites applies here with extra weight.
Reporting Tentatives Properly
Most teams lose tentatives in reporting before they lose them in real life. Three fixes help.
Give tentative its own status. If your CRM sync collapses tentative into accepted, your acceptance rate is inflated and your show rate looks worse than it is. If it collapses tentative into pending, nobody follows up. Map it to a separate stage that triggers a task.
Track tentative-to-held as its own number. Over a few campaigns you will see how your tentatives behave, and whether changes to your invite copy move more of them into accepted.
Separate defaulters. If certain roles or accounts respond tentative to everything, flag them so their tentatives are not counted as real interest.
Our guide to syncing cold calendar invite outreach with HubSpot and Salesforce covers the field mapping.
What Tentatives Tell You About the Invite
A steady stream of tentatives is useful feedback about the invite itself.
- Lots of tentatives with proposed times usually means the topic is landing but your default times are not. Look at time zones and the day of the week.
- Lots of tentatives with no note often means the description did not give a strong enough reason. The prospect is interested enough not to decline, not enough to commit.
- Tentatives that get forwarded suggest your targeting is close but one level off. The invite is reaching someone adjacent to the real owner.
Each of these points at a specific fix in your targeting, timing or copy, which is more than an acceptance rate alone will ever tell you.
The Short Version
A tentative is not a yes and it is not noise. It is a prospect who engaged, did not commit, and is often telling you exactly why. Answer every one within a business day, take any proposed time, ask one clear question when there is no note, confirm the day before, and give tentative its own place in your reporting.
Handling those replies at volume is part of running calendar outreach properly. KALI manages invites, follow-ups and reply handling as a managed service, so maybes get answered instead of expiring. See how it works.