## TL;DR
Never book from a bare time. The agent must resolve the lead's timezone from the CRM record, convert the proposed time explicitly, and state the time in both timezones in the invite and the confirmation message. Ambiguity at booking time becomes a missed meeting later.

```
agent booked a meeting for 'tomorrow at 2' without a timezone  -  the rep and the lead showed up 3 hours apart
```

## Steps

1. Require a timezone on every booking: the agent looks up the lead's timezone from the CRM (falling back to asking the lead) before any invite is created.
   Expected: no invite is created without a resolved timezone for both sides, and the run log shows the lookup.

2. When the lead says "tomorrow at 2", the agent confirms back with the time in both timezones: "tomorrow at 2pm Pacific - that is 5pm Eastern for you, right?"
   Expected: the confirmation message names both zones, and the booking waits for the lead's yes.

3. Write the invite with the timezone baked into the calendar event itself, not just the email body, so every calendar renders it correctly.
   Expected: the calendar event carries an explicit timezone, and opening it in a different zone shows the right local time.

4. Add a pre-send check on the invite: start time, end time, timezone present, and the converted time matches what the lead confirmed.
   Expected: the check fails loudly if any piece is missing, blocking the invite until fixed.

5. For the missed meeting that already happened, have the rep rebook personally with an explicit apology and a timezone-confirmed time.
   Expected: the rebook message states the time in the lead's zone and confirms it back.

## Use this when
- meetings get booked from vague times with no timezone
- the rep and the lead show up hours apart
- the agent assumes its own timezone is everyone's timezone

## Not for this skill when
- the calendar API throws errors - that is an integration bug
- the meeting is double-booked - that is an availability-check bug
- the lead no-shows for other reasons - see the no-show follow-up skills

## Variant phrasings
- booked "tomorrow at 2" with no timezone
- meeting time assumed in the agent's timezone
- rep and lead 3 hours apart
- timezone never confirmed at booking

## Why it happens
"Tomorrow at 2" feels complete in conversation, and the agent treats it as complete data. But a time without a zone is not a time at all - it is a wish. The booking step then renders it in whatever zone the server or the rep happens to sit in, and the lead reads it in theirs.

## Edge cases
- Daylight saving transitions move the offset - resolve the zone by date, not by a fixed hour difference.
- Leads who travel: confirm the zone for the meeting date, not the zone on their CRM record from last year.
- "2" could mean 2am - the confirmation-back step catches absurd times before they become invites.
- Group meetings across three zones - name all of them in the confirmation, and let the calendar event do the math.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_hOxY2N5Zgy0GamLtr7E_NQ