AI phone interviews: avoid timezone booking mistakes
Prevent interview timezone mix-ups. Use a London–Singapore example and booking checklist to confirm the right date, local time and joining method.
Adan Vielma · · 7 min read
Avoid AI phone interview timezone mistakes by confirming the date, local time, timezone and joining method together in the booking and confirmation.
Before recording a no-show, compare what the candidate saw with the scheduled call. The London–Singapore example shows how a clock change can make a calendar entry look correct to the recruiter while the candidate receives the call at a different local time.
One appointment can have two correct clock times
Suppose a candidate is in London and the recruiter is in Singapore. The candidate chooses 9 am London time. These are two possible bookings in October 2026:
| Interview date | Candidate’s London time | Recruiter’s Singapore time |
|---|---|---|
| Monday 19 October 2026 | 9:00 am BST, UTC+1 | 4:00 pm, UTC+8 |
| Monday 26 October 2026 | 9:00 am GMT, UTC+0 | 5:00 pm, UTC+8 |
The UK clocks go back on 25 October 2026. Singapore uses UTC+8, as the National Metrology Centre explains. The one-hour change in the table comes from that UK clock change.
“Singapore is eight hours ahead of the UK” would be wrong for the first booking. “9 am your time” is also fragile when it is copied into an email thread read by people in different locations.
Use the date of the appointment when checking the conversion, not today’s difference between the cities. An interview booked before a clock change may happen after it.
Find out which timezone the booking page is using
A scheduling page can detect a browser’s timezone, use an account setting or be fixed to a particular event location. Those choices have different effects.
For example, Calendly’s timezone guidance describes detecting invitees’ local time, allowing a different timezone to be selected and locking some events to a location. It also distinguishes account display settings from the settings used on the booking page.
That is a reason to inspect your actual tool, not to assume Screened behaves exactly like Calendly. Ask the person testing the booking to read the timezone label before choosing a slot. Can they understand it? Can they change it where the workflow allows? What does the confirmation then show?
A candidate might book while travelling, use a device still set to another location or deliberately select the timezone where they will be on the interview date. Do not infer their intended appointment solely from their current location or the address on their CV.
The useful question is: “Which timezone was selected for this booking?”
Test the selection, confirmation and scheduled event together
Use a made-up candidate with contact details controlled by your team. Do not create an appointment in a real applicant’s name or change a live calendar merely to test a conversion.
Record the expected time in both locations before starting. The intended appointment is 9 am in London and 5 pm in Singapore on 26 October 2026.
Then trace it through the system:
| Step | What to inspect | What would be a problem? |
|---|---|---|
| Candidate chooses a slot. | The date, clock time and visible timezone. | The page shows only “9:00” or uses a different timezone without making that clear. |
| Booking is confirmed. | The latest confirmation’s date, time, timezone and interview method. | The email changes the clock time without explaining the timezone, or describes the wrong joining route. |
| Calendar event is opened. | The event’s timezone and how it displays in each test calendar. | A copied calendar item refers to a different moment or an earlier booking. |
| Recruiter opens the appointment. | The scheduled event and the timezone used in the recruiter’s view. | The recruiter mistakes a correct local conversion for an incorrect booking. |
| Candidate reschedules. | The new confirmation, current event and treatment of the original appointment. | Both appointments remain active or the candidate is still reminded about the old one. |
A correct 5 pm Singapore display is not a fault when the candidate booked 9 am London time on that date. You are checking that both displays refer to the same appointment, not demanding identical clock numbers everywhere.
If the information differs, preserve the test record and identify the first point where it changed. That gives support something more useful than “timezones are broken”.
Changing the display is not the same as rescheduling
Opening an existing event in another timezone should be distinguished from choosing another appointment. Ask the vendor to demonstrate both actions in the test workflow.
Suppose the candidate booked while in Singapore but will be in London on the day. They need to know the local time of the existing appointment. They may then decide to reschedule, but a display conversion alone should not be described as a new booking.
Keep the conversation explicit: “Your current appointment is at 9 am London time on Monday 26 October. Would you like to keep it or choose another available time?” Do not silently move it because a recruiter assumes that 9 am in one place must mean 9 am everywhere.
For recurring or repeated appointments, check the dates individually around daylight-saving changes. A template with a fixed difference between countries can become wrong even when the event’s local start time stays the same.
London–Singapore interview confirmation
For the London example, an employer’s confirmation could read:
Your phone interview for the Customer Support role is booked for Monday 26 October 2026 at 9:00 am London time (GMT, UTC+0). That is 5:00 pm in Singapore. Ryan, Screened’s AI interviewer, will call the phone number you provided. Use the reschedule or cancel link in your latest booking confirmation if you need to change it.
The second location is useful for this cross-border example; it is not necessary to put five timezones into every candidate email. Prioritise the timezone the candidate selected and avoid abbreviations on their own.
Confirm that the joining instruction matches the actual interview. Screened’s interview guide distinguishes a call to the supplied phone number from a browser interview started through a link. Using a mobile device does not turn the browser route into a scheduled phone call.
Screened’s existing-booking guide explains how candidates find their confirmation and its reschedule or cancel links. It also explains that the original scheduling link may no longer open a new booking page once an interview is scheduled.
Do not send a second application link to solve that expected behaviour.
What to check when the interview call does not arrive
Start with three checks: the latest booking, the joining method and the number supplied for a phone interview. Do not begin with browser microphone instructions when the person is waiting for an ordinary telephone call.
Ask the candidate to check the date, time and timezone in the latest confirmation, including any reschedule message. Have them verify any phone details displayed in the booking through the approved route. Do not tell them to call an unfamiliar number back or post their private invitation link in a public support channel.
If the scheduled time has passed and the call has not arrived, investigate the interview state. Do not invent a five-minute retry rule, promise a particular caller ID or tell them to keep making new bookings. Use a callback or reschedule action only where the current page or message actually offers it.
A support request can be short:
My phone interview for the Customer Support role was booked for Monday 26 October 2026 at 9:00 am London time, but I have not received the call. I have checked my latest confirmation. Please help me check the booking.
The candidate should provide their booking identity through the support channel as needed, not identity documents or a complete CV. The employer handles application decisions and alternative arrangements; technical support checks the interview process.
Resolve the scheduling issue before recording a missed interview
Where a booking or confirmation was wrong, explain the error and agree the next step. Check the ATS record and any outstanding reminder before declaring it resolved.
Do not leave “unreliable, missed interview” in a hiring note when the evidence shows that the person followed an ambiguous or incorrect confirmation. Record the scheduling issue accurately and keep any later assessment separate.
Finish with one clear, current appointment. The candidate should know when it happens, which timezone that time belongs to, how to join and what to do if the call does not arrive. That is more useful than asking them to understand how your calendars work.
