Timezone confusion is almost always a display question rather than a booking that's genuinely at the wrong moment. Working out whose timezone you're looking at usually resolves it.
How SalesCal picks a timezone
Your availability is set in your timezone, taken from your profile.
The booking page shows times in the prospect's timezone, detected automatically from their device. There's a timezone selector on the booking page so they can change it if the detection is wrong or they're booking on behalf of someone else.
Emails are sent in the timezone of whoever is receiving them. You see your time, the prospect sees theirs, and both refer to the same moment.
So a 2pm slot on your calendar legitimately appears as 9am to a prospect five hours behind. Nothing is wrong.
Check your own timezone first
Go to Settings and confirm your timezone is correct. This is the anchor for your entire weekly schedule.
If it's wrong, every slot you offer is shifted, and the symptom looks like "my availability is at the wrong hours" rather than a timezone problem. This is worth checking after any house move or any account originally set up by someone else.
The prospect saw the wrong time
Check the timezone shown in the picker on the booking page. Detection uses the device's own setting, so it goes wrong when:
The prospect's computer clock or timezone is set incorrectly
They're travelling and their device hasn't updated
They're using a VPN that shifts the apparent location
They can correct it with the timezone selector before choosing a slot. If a booking has already been made at the wrong time, reschedule it rather than trying to correct the record.
Daylight saving changes
Clock changes are the other common cause, and they bite when your region and the prospect's region change on different dates. For a couple of weeks each spring and autumn the usual offset between two countries is an hour different from normal.
SalesCal handles the arithmetic, but a meeting booked before a clock change and held after it can look an hour out if you're mentally applying the old offset.
Multi-host events
On events with several hosts in different regions, availability is normalized to the event owner's timezone before the hosts' calendars are combined. Each host's own calendar is still checked in their own timezone, so nobody gets booked outside their working hours.
If a host in another region is being offered at hours that look wrong to you, check that host's profile timezone.
A lead's stored timezone looks stale
The timezone recorded against a lead is captured when they book. If they later travel or fix their device setting, the stored value on the older record stays as it was. That's a record of what was true at booking time, not a live value, and it doesn't affect the meeting itself.
Still looks wrong?
Get in touch with the meeting, the time you expected, and the time you actually saw, plus the timezone you're in. Two clocks and two zones is exactly the kind of thing that's faster for us to check against the stored record than to reason about in the abstract.