How to Set Customer Expectations About Response Times Across Time Zones

A customer in London contacts support at 4pm. They don’t hear back until 11am the next day — 19 hours later. If your team is in Manila, that’s actually fast. They responded within two hours of their working day starting. But the customer didn’t know that. The silence felt like neglect.

The fix isn’t faster responses. It’s telling customers when to expect a response, in terms they can understand.

What not to say

“We’ll get back to you shortly” means nothing when your team is 8 hours from starting their day. “Responses within 24 hours” is ambiguous about whether that clock runs on business hours or calendar time. “Our team is on it” tells the customer nothing useful.

What to say instead

In the auto-response to every inbound ticket, give a specific UTC time:

Thanks for reaching out. Our support team is based in Manila (UTC+8) and works Monday–Friday, 9am–6pm PHT.

Your ticket arrived at 16:42 UTC. Based on our current queue, you can expect a response by 03:00 UTC tomorrow (11am Manila / 4am London / 11pm New York).

This anchors the customer’s expectation to a real time, converts it to zones they recognise, and removes the anxiety of wondering whether anyone has seen their message.

If you know the customer’s location from their account, lead with their local time:

You can expect a reply by tomorrow at 11:00am your time (Sydney AEST).

That’s more actionable for most customers than a UTC time.

Be explicit about business hours vs. calendar hours

Your SLA probably runs on business hours, but customers assume calendar hours unless you say otherwise. Make it explicit:

• Calendar hours: “We respond within 8 hours of your message.” The clock runs continuously — a 4pm Friday message gets a response by midnight.
• Business hours: “We respond within 8 business hours.” A 4pm Friday message gets a response by 12pm Monday.

Whichever you use, express it in UTC-equivalent terms so international customers can verify when to expect a reply.

For holidays and planned downtime

Send notice 5–7 days in advance — not the morning of:

Our support team will be on reduced hours 24–26 December. For tickets received during this period, please expect a response by 27 December at 10:00 UTC. For urgent issues: [escalation path].

Customers who contact during the gap will see it in the auto-response. Customers who are planning ahead will see it earlier. Both groups are better served than by silence.

On your support page or contact form, show your team’s working hours in UTC alongside a current response time estimate. A customer who knows what to expect will wait patiently. One who gets “we’ll get back to you soon” will send three follow-ups.