Unmeet / Meeting excuses
Excuses to leave or miss a meeting, that hold up
The difference between an excuse that works and one that doesn't is rarely the reason. It's whether anyone can check it, and whether you said it early enough.
The short answer: the best excuses share three properties.
- Nobody can verify them. A conflicting call inside your own calendar can be checked. Connection trouble cannot.
- They need no follow-up. If it invites "how did it go?" a week later, you have to remember it.
- They're short. Detail is what makes an excuse sound invented.
For leaving a meeting early
Connection trouble
The most reliable one, because nobody can disprove it and everyone has lived it. It also explains why you left abruptly rather than gracefully.
Watch out: if you keep talking normally for ten minutes afterwards in another call, it falls apart. It works best when you actually go quiet.
Another call starting
Ordinary to the point of invisibility in most companies. The weakness is a shared calendar — if yours is public and empty, don't use it.
Something urgent came up
Deliberately vague, which is the point. It contains no checkable detail at all.
A client needs you
Strong in client-facing roles because internal meetings lose to client work by default. Weak if your colleagues know your accounts.
Something at home
Rarely questioned, and rarely followed up on. Use it sparingly; it's the one people remember.
For missing a meeting entirely
- A clash you flag in advance. Sent the day before, this stops being an excuse and becomes scheduling.
- Deep work on a named deliverable. "I need this morning on the launch copy" is respected in most teams because it's checkable in a good way.
- Asking whether you're needed. "Do you need me for this, or can I read the notes?" is often accepted outright — and it isn't an excuse at all.
The most underrated move: send it the day before. The same sentence that reads as an excuse ten minutes beforehand reads as courtesy twenty-four hours out.
The ones that get you caught
- Anything in a shared calendar. If colleagues can see your day, don't invent a meeting in it.
- Illness you can't sustain. It invites follow-up and you have to remember it tomorrow.
- Elaborate stories. Length is the tell. Two sentences maximum.
- The same excuse twice in a fortnight. Any single reason survives repetition badly.
- Blaming a named colleague. They will find out, and it costs more than the meeting was worth.
Say it in the chat, not out loud
Announcing an excuse by voice makes the whole room stop and listen to it, which is the opposite of what you want. Typed in the meeting chat, it is read by the people who care and skimmed past by everyone else — and it leaves written evidence that you said something, which is what protects you afterwards.
A different excuse every time, written for your job
Unmeet keeps over 100 wordings across 8 reasons, matched to your role and tone, and never repeats the last one. It posts the excuse and leaves the call for you.
See how Unmeet worksCommon questions
What is the most believable excuse to leave a meeting?
Connection trouble. Nobody can verify it, everyone has experienced it, and it also explains an abrupt exit. It works best if you then stay off other calls for a while.
What's a good excuse to leave a meeting last minute?
Something urgent and unnamed — 'I've just been pulled into something time-sensitive'. It contains no checkable detail, needs no follow-up, and nobody expects specifics about an emergency.
Should I give a reason at all?
A short one. 'I need to drop off' with no reason invites speculation; two sentences of explanation closes it. What backfires is a long, detailed story.
How often can I use the same excuse?
Rotate them. Any single reason used twice within a couple of weeks starts to be noticed, and connection trouble is the fastest to wear out because it is the most convenient.
Is it better to leave silently?
No. An unexplained disappearance is what people remember and ask about. A line in the chat costs you nothing and removes the question entirely.