For businesses booking across countries and time zones, it should be easy to see, set, and use each client’s local time. Adding a client time zone throughout the platform would make scheduling far less confusing, help handle daylight saving changes correctly, and make sure clients always receive the right appointment information.

What this would make possible:

• Show a client’s time zone in their details at a glance so teams can quickly confirm where the client is based.

• Store the time zone alongside other client info such as email and phone number when onboarding a new client.

• Edit or set the client’s time zone from the backend — especially useful when staff create or update bookings on a client’s behalf.

• Use the client’s own time zone for reminders and notifications so appointment messages reflect their local time, not the staff member’s time zone.

• Handle daylight saving time more reliably for clients in different regions, reducing the yearly confusion that comes with seasonal clock changes.

• Include the client time zone in the interface, API responses, and webhooks so it’s visible both inside the product and in connected systems.

• Add the meeting start date and time based on the customer’s time zone to API fields so external email tools, CRMs, automations, and reporting systems can send accurate confirmations and stay in sync.

Why this matters:

• Reduces mistakes and missed appointments caused by time zone mix-ups.

• Removes the guesswork for teams working with clients from places like San Francisco, Amsterdam, and Sydney.

• Helps businesses keep communications consistent across their own tools, including custom email flows.

• Makes global scheduling smoother and more reliable for both staff and clients.

This would be a must-have improvement for any business serving clients across multiple regions.