Customers in multiple time zones: how to state your hours, book appointments in their local time, set expectations for human replies, and let an AI agent cover the hours you sleep

The moment a business serves customers abroad, every time becomes ambiguous. "We reply within business hours" means nothing to someone eight hours away, and "your session is at 3 pm" has started arguments on three continents. The fix is naming the zone, converting for the customer, and covering the overnight with something that never sleeps.

By Ritchie, ReplyKit · Published 5 October 2026 · 6 min read

Quick answer

Always write times with a named zone ("9 am to 6 pm GMT+8" or "Singapore time"), ask the customer's location early so the agent can convert, state when a person replies ("a human answers between 9 and 6 GMT+8; the assistant answers now"), book appointments in the customer's local time with the zone shown, and schedule reminders in the customer's daytime. An AI agent answers questions and books at any hour, which removes most of the pain; ReplyKit converts booking times when you set your business time zone and the customer tells it theirs.

State the zone, every time Booking in the customer's time Covering the hours you sleep The three classic mistakes FAQ

State the zone, every time

Hours: "Mon to Fri, 9 am to 6 pm, GMT+8 (Singapore)". Never bare "9 to 6".
Deadlines: "Order by 2 pm GMT+8 for same-day dispatch".
Appointments: "Tuesday 3 pm your time (Tuesday 10 pm GMT+8)". Both, with yours second.
Support expectations: "The assistant replies now; a person replies within business hours, GMT+8".
Put your zone in the knowledge base once and the agent uses it in every answer.

Booking in the customer's time

Set your business time zone in the dashboard.
The agent asks the customer's country or city early (it is also a qualifying question).
It offers slots converted to the customer's local time, showing both zones, and books in yours.
The confirmation and the day-before reminder state the customer's local time first.
Daylight-saving changes are handled by the conversion, which is where humans get it wrong twice a year. The booking mechanics are in booking without double-booking.

Covering the hours you sleep

A customer in another zone messages during your night, and research on lead response, including the HBR study, finds the first hour decides most of the outcome. The agent answers in seconds from your knowledge, books the call, and hands over anything that needs you with a note that a person replies at 9 am your time. Stating that honestly is better than silence; the wording is in setting expectations for AI replies. For a business with customers mostly in one distant zone, consider a human shift that overlaps their afternoon.

The three classic mistakes

Ambiguous times. Fixed by naming the zone everywhere.
Deadline confusion. "By Friday" is two different days on either side of the date line. Add the zone and the time.
Reminders at 3 am. Reminders scheduled in your zone land at night for the customer. Set reminders relative to the appointment in the customer's local time, and keep any manual follow-ups inside their daytime; the sequence is in following up leads who stop replying.

Frequently asked questions

How should I write my business hours for international customers?

With a named zone every time: "9 am to 6 pm GMT+8 (Singapore)".

Can an AI agent convert appointment times?

Yes, when you set your business zone and the customer tells it their location. It shows both times and books in yours.

What do I tell customers who message overnight?

That the assistant answers now and a person replies within stated hours in a named zone. Honest expectations beat silence.

How do I avoid sending reminders at night?

Schedule reminders relative to the appointment in the customer's local time, and keep manual follow-ups inside their daytime.

Does daylight saving break the conversion?

Not when software does it. It breaks when people convert by hand twice a year.

Answered in their daytime, booked in their time

The agent covers your night and converts every appointment. 7-day free trial, no card.

Start free

Written by Ritchie, ReplyKitPart of the small team in Malaysia that builds and runs ReplyKit. Writes about WhatsApp automation, AI customer service and small business lead response.

How we know this. ReplyKit serves customers across many time zones and its booking states times in the customer's zone when the business sets its own; the practices here are what international customers use. Product figures in this article (limits, prices, per-reply costs) are taken from ReplyKit as it runs today and are re-checked when we update the page. Where we cite outside research, the source is linked below. We sell ReplyKit, so read our product claims with that in mind; we say where a different tool or no tool is the better choice. About ReplyKit.

Sources and further reading

Harvard Business Review, The Short Life of Online Sales Leads (Oldroyd, McElheran, Elkington, 2011) · firms that responded within an hour were about seven times more likely to qualify the lead
Lead Response Management Study (2007) · the five-minute window for contacting a new lead

ReplyKit is an independent product and is not affiliated with or endorsed by Meta or WhatsApp. This article is general guidance for running a small business, not legal, financial or regulatory advice.