Time Zones
Two separate problems#
Translating. Every participant needs to see options in their own local time, not yours. Sending "2pm PT" to a candidate in London is asking them to do arithmetic on your behalf before they can answer.
Timing. Even correctly translated, a message sent during your working day may land in the middle of their night, and their reply lands in the middle of yours. Every exchange costs a day.
What Vela does#
Vela proposes options in each recipient's local time automatically, and it coordinates around the clock. When a candidate in Singapore replies at what is 2am your time, the confirmation goes out immediately and the invite is on every calendar before your day starts.
One customer put it plainly: "Vela is killing it. Working across time zones and continents." — AI Leader at Clarity Group.
Where this matters most#
| Situation | Without Vela | With Vela |
|---|---|---|
| Candidate abroad, recruiter in SF | One exchange per day, a week to book | Booked overnight |
| Panel spanning three continents | Manual matrix of overlapping hours | Options that clear every calendar |
| Client in a different zone reschedules | Cascade waits for your morning | Re-coordinated when it happens |
| Daylight-saving shift mid-process | A meeting quietly lands an hour off | Correct on every calendar |
Related: Channels, Rescheduling.