The message lands at 8:40 for a 10:00 recording. Something came up.
You have a blocked-out morning, a mic already on the desk, and a Thursday publishing slot that assumed this episode would exist.
Almost everything written about guest cancellations is about preventing them. Good advice, wrong moment. Nobody at 8:41 needs to hear about confirmation cadence.
So this is the other half. What to do in the ninety minutes after the message arrives, how to choose between rescheduling and salvaging, and what to write back so the guest either turns up later or clears your calendar cleanly. Prevention is at the end, where it belongs.
Read the message before you answer it
Four different things get called a cancellation, and they need four different replies.
The reschedule. They name a reason and propose a new time, or ask for one. This is not really a cancellation. It's an administrative task wearing a scary costume.
The vague postpone. "Things are crazy right now, can we push to sometime next month?" No date. Usually a soft no, and treating it as a firm booking is how hosts end up with a calendar full of ghosts.
The withdrawal. They're out. Sometimes with a reason, sometimes not.
The no-show. No message at all. You're sitting in the room alone at 10:04.
The distinction matters. A reschedule needs a short logistical reply; a vague postpone has one job, which is forcing a date or a no. Don't send the same warm, accommodating note to both. That note is what keeps a dead booking alive for six weeks.
Your four options, and the thing that actually decides between them
Once you know what happened, you have four moves: reschedule, swap in a replacement, record solo, or leave the slot empty and publish from your backlog.
Most advice picks a favorite. That's the wrong shape of answer, because the right move barely depends on the cancellation at all. It depends on your buffer.
If you have two or more finished episodes banked, reschedule and go do something else. Seriously. Your publishing schedule is not in danger, and a rushed replacement episode is a permanent artifact of a temporary problem. The most common mistake here is treating a cleared morning as an emergency instead of as three free hours.
If you have one episode banked, swap in a replacement if your bench has someone reachable, and otherwise record solo. You have enough runway to be choosy about who, and not enough to skip a week.
If you have nothing banked, record something today. Replacement guest if you can get one in the next four hours, solo if you can't. Then, this week, fix the fact that you were running on zero. That's the real problem the cancellation exposed.
If the show publishes fortnightly or on no fixed schedule, reschedule. The gap costs you nothing.
Write your own version of those four lines and pin it somewhere. Deciding this under time pressure is how you end up recording a bad episode you'll still be embarrassed about in November.
What to write back
Three replies cover nearly everything. Keep them short. A long, gracious paragraph reads as an invitation to keep negotiating.
To a genuine reschedule, close it in the same message:
No problem at all. I've got Tuesday 14th at 10:00 or Thursday 16th at 15:00 — either work? Happy to hold the slot until end of day.
Gracious, and there's a clock on it. Two options beat "what works for you?", which hands the scheduling work back to the person who just created it.
To a vague postpone, force the fork:
Totally understand. Rather than leave it open-ended — do you want me to come back to you in September, or should we park it for now? Either is completely fine.
Explicit permission to say no is what gets you a real answer. Plenty of guests will pick "park it," and that's a good outcome. An honest no in August beats four more emails and a second cancellation in October.
To a no-show, wait fifteen minutes — there's a minute-by-minute protocol for that wait — then send one line:
Hi — had you down for 10:00 today, no worries if something came up. Want to find another time?
No edge to it. People miss things for boring reasons, and a guest who genuinely double-booked will be mortified. If there's no reply within 48 hours, that's your answer, and you don't need to send a second one. One follow-up is diligence. Two is chasing.
Recording with a guest you booked four hours ago
Say you go with the replacement. Somebody from your bench says yes at 11:00 for a 15:00 recording, and now you have the opposite problem: a confirmed guest you know almost nothing about.
Standard prep advice assumes a week. Compress it honestly instead of pretending you can do the full version at speed.
Thirty minutes buys you three things. Their bio and two most recent posts. Ten minutes of their last interview at 1.5x, listening for how they answer rather than what they say. Then five questions plus one thing you genuinely want to know. That last one carries more of the episode than the other five combined.
Skip the rest. Don't try to read a book, and don't build a full outline. An under-prepared host asking real questions beats a scrambling host performing preparation they don't have.
The gap that's left is the one you feel live: they mention a paper, a company, a number from their field, and you have nothing to push back with because you learned about all of it ninety minutes ago.
That's the part Liyam AI is built to carry. Its prep call agent listens to a prep call and drafts your outline, structures the segments, and writes your questions. So the fifteen-minute "can we jump on quickly first?" call becomes your prep document instead of just a chat.
During the recording, the on-screen script keeps your run-of-show in front of you organized by topic, and it generates follow-up questions in real time from what's actually being said. When they cite something you can't evaluate, live fact check catches inaccuracies as they happen and brings sources on screen. You can pull up relevant articles, images and clips mid-recording without losing the thread.
None of that manufactures expertise you don't have. What it does is remove the specific failure mode of a rushed booking, which is the host going quiet and nodding because they have nothing to ask next.
The solo episode you can actually record today
If nobody's available, record alone. The trap is trying to produce your normal show minus a guest, which needs the one thing you don't have: a script.
Three formats work from a standing start.
Listener questions. Pull four from your inbox, DMs, or comments. Answer them properly, eight to ten minutes each. Near-zero prep, and it's the format most hosts underrate.
The thing you changed your mind about. Pick an opinion you held two years ago and no longer hold, and walk through what moved you. You already know this material completely. It's usually more interesting than an interview.
The annotated recap. Replay two or three clips from a recent episode and add what you were thinking but didn't say on tape. Quick to produce, and it makes the back catalogue useful again.
Say the format out loud in the first thirty seconds so listeners know what they're getting. A solo episode that announces itself as a solo episode is a choice. One that doesn't sounds like an accident.
What to change so it happens less
Now the prevention part, and it's shorter than most articles make it.
Confirm twice, not once: a note when you book, and a note 24 hours before with the link, the expected length, and the topic in two lines. A guest who has to search their inbox for the link at 09:58 is a guest who might not join at 10:00. Zapier's walkthrough of automating guest scheduling is a reasonable starting point if you'd rather not send those manually.
Keep three people on a bench who've already said yes in principle and just need a date. Three, not a wishlist of thirty.
And try shortening your booking window. If you routinely book eight weeks out, run a month at three and compare how many hold. Long lead times let people say yes to a version of their future self who has more free time than they will.
If cancellations are frequent rather than occasional, the diagnosis is usually further upstream: the show's guest ghosting problem is a booking-process problem, not bad luck.
FAQ
Should you charge a fee when a podcast guest cancels?
No, for almost every independent show. Fees make sense when you're paying for a studio or crew by the hour, and even then they work better as a stated policy than as money you collect. Chasing a fee from an unpaid guest costs you the referral, and independent podcasting runs on referrals.
How many times should you let a guest reschedule?
Twice. After a second reschedule, move them from your calendar to your bench and let them come back to you. This isn't a punishment, it's accurate bookkeeping: someone who has moved twice is not currently a confirmed guest, and treating them as one distorts your whole schedule.
Is it rude to fill the slot with someone else?
Not at all, and you don't need to mention it. Guests are not booked to a specific episode number in any way they can perceive. If they ask, the honest answer is fine: the recording day was blocked out, so it got used.
How far in advance should you confirm a podcast guest?
Twenty-four hours, with the link in the message. Earlier than that and it gets buried; later and there's no time to salvage the slot if they can't make it. If the booking was made more than a month ago, add a check-in a week out too.
Bottom line
A cancellation is a scheduling problem that hosts keep treating as a crisis.
Work out which of the four things actually happened. Look at your buffer, not your feelings, and pick a move. Send a short reply that either sets a date or ends the booking. Then record something you can do from a standing start, or take the morning back.
The one thing worth being strict about: an empty slot is only an emergency if you were running on zero episodes banked. That's the thing to fix this week.
And if the answer today is a replacement guest you booked four hours ago, Liyam AI is built for exactly that recording — the one you walk into under-prepared and still have to make good.
Further reading: Guest ghosting and why interview subjects disappear, handling last-minute cancellations from speakers, and taking the busywork out of scheduling podcast guests.