By Junaid Ahmed
Someone booked a recording on my calendar this week. The episode created itself. The confirmation went out. The prep reminder went out ahead of the call, right on schedule.
Every part of that worked. The one part that actually helps the guest was missing.
PodGlue is supposed to send a guest their questions before we record. Not a script. Just the shape of the conversation, so they can think about it in the shower instead of hearing it cold on the call. That email arrived on time with no questions in it.
Here is what I found when I went looking.
There are two ways an episode gets created from a booking. I open the app and click a button. Or the system notices a confirmed booking with no episode attached and builds one on its own.
The first way generated the questions. The second way didn't.
Now think about when the second way runs. It runs when somebody books me at 11pm through my public link. It runs for calendar bookings. It runs, specifically and by design, when there is no host sitting in the app.
The automatic path exists for the moments nobody is around. It was also the only path missing the questions step. So the bookings that needed the software to carry the most were the ones it carried the least.
The reason it hid for so long is the part I keep thinking about.
When the questions are missing, the prep email doesn't break. It doesn't error. It doesn't send a half-finished section with an empty heading. We built it that way on purpose, because a guest should never receive something that looks like a bug.
So it just sends the email without them. Politely. On time. Every time.
A missing feature that renders as a perfectly good email is not something you catch by reading the email. I read those emails. They looked fine. They were fine, minus the only part I added them for.
What it does now: when a booking creates an episode on its own, the questions get written right then, on the server, without waiting for me to open anything.
It reads what the guest already told me. Their intake answers are sitting right there on the booking, in their own words, which is a better brief than anything I'd write about them from the outside.
I tested it on a real booking before trusting it. Episode created, questions written three minutes later, every one of them built from what that person had actually typed into the form. One of them was pulled from the book they said they liked.
That is the whole point. A question that could have been asked of anybody is not worth sending ahead of time.
What's next is the boring half: the same treatment for the discovery calls, which deliberately get nothing today, because a run of show for a fifteen-minute chat is the wrong artifact and I'd rather send nothing than send that.
And I want to look harder at the class of bug this belongs to. Not the missing questions. The fact that a feature can be absent for weeks while every screen and every email reports success.
Those are the ones that cost you a guest's preparation and never show up in a log.
If you're building a show where the conversation is the product, the prep is not overhead. It's the work. PodGlue is where I keep mine.
Run your next episode through PodGlue
Upload one transcript. Get show notes, social posts and an SEO page, plus a guest record that remembers the conversation after you publish.
Start free trial14 days free · Cancel before day 14, pay nothing
Don’t just read the build. Shape it.
PodGlue is built from conversations with hosts, guests, producers, and agencies doing the work. What does Nobody Was There to Press the Button look like in your workflow?
Related reading
The Episode Is Already There
A guest books. Their episode now exists before you've opened the app. Small change, and it removed a step I'd been doing hundreds of times without noticing.
My Calendar Invite Finally Tells Me Who I'm Talking To
Ten minutes before a recording, the calendar event said a name and an email. Everything the guest had actually told me was somewhere else.
I Kept Opening the Calendar and Learning Nothing
Ten minutes before a recording I'd click the event and get a name, an email, and a link. Everything the guest had actually told me was somewhere else.