Someone Booked Me For Thursday Morning. It Landed Wednesday Night.

A confirmation email came through for a podcast interview. Wednesday, August 26, 7:00 PM PDT.

Two things were odd about that. I'm on Eastern time, so my own booking confirmation was quoting me a timezone I don't live in. And I don't record Wednesday evenings, my interview hours are Thursday, ten to five.

So how did anyone book a slot I never offered?

What was actually happening

When you set your available hours in PodGlue, you type something like "10:00 to 17:00." That gets saved exactly like that, as text. Ten o'clock. No note anywhere about ten o'clock where.

That's fine while you're the only one looking at it. It stops being fine the moment a guest opens your booking page, because their computer reads "10:00" and quite reasonably assumes ten o'clock their time.

There was a timezone dropdown on that page. It didn't do anything. You could switch it from Pacific to Tokyo and not a single time on the screen would move. It looked like a control and behaved like a label.

So the booking got assembled from two different places. The actual moment came from the guest's computer clock. The timezone written on the confirmation came from the dropdown. Nobody checked whether those two agreed.

The part that made it hard to spot

The booking wasn't made by the guest himself. He works with a team who handle his bookings, and they're on the other side of the world.

They opened my page. It showed them Thursday, 10:00 AM, which matched what the guest and I had agreed, so they clicked it. They set the dropdown to Pacific, because that's the guest's timezone, which is exactly the right instinct.

And it still went wrong. Their computer was on their local time, twelve hours ahead of mine, so "Thursday 10:00 AM" on their screen was Wednesday 10:00 PM on mine. The dropdown they'd carefully set didn't feed into the calculation at all.

Everyone did their job correctly and the booking still landed on the wrong day. That's the part worth sitting with. When a tool can absorb a right answer and produce a wrong one, the people using it have no way to catch it.

The thing that finally proved what happened was my own calendar. That slot only exists on Thursdays between ten and five. Read the stored booking on their clock and it lands squarely inside that window. Read it on Pacific, the timezone the email claimed, and it falls on a Wednesday evening, when I offer nothing at all. Their browser was the only clock that could have been shown that slot.

What changed

Your hours now belong to a timezone, and you can see which one. There's a picker at the top of your availability settings that says what your hours mean, and if it doesn't match the computer you're sitting at, it says so and offers to fix it in one click.

Guests see your times converted to their own clock. If the conversion moves the date, because they're far enough away that your Thursday morning is their Friday, the slot says so instead of quietly showing a time that belongs to a different day.

And your confirmation emails are on your clock now. Yours, not your guest's. The guest's local time is still in there, clearly labelled as theirs, so you can see both without doing the arithmetic yourself. Same for reschedule notices, cancellations, and reminder texts, those were all quoting you a stranger's timezone too.

What's next

I haven't moved any bookings that already exist. Changing what a confirmed booking means is not something software should do to you quietly, so if you've got one that looks off, it's still sitting there exactly as it was.

One thing I want to go further on: PodGlue currently assumes the person booking is the person showing up. For anyone with a team booking on their behalf, which, at a certain point, is most working podcasters, that's just not true, and it's why the confirmation went out labelled with a timezone belonging to neither person on the call.

That's the recurring lesson for me building this. The episode is a byproduct; the conversation is the product. And a conversation nobody can find because it's twelve hours from where they expected doesn't happen at all.