Account timezone

Overview

The account timezone is the single time reference for your workspace. It decides two things at once:

• How a time is saved. When someone picks "21/07/2026 15:59" as a task due date, that time is interpreted in the account timezone.
• How a time is displayed. The same commitment shows the same time on the dashboard, on the board card, in the notification email, in the generated PDF and in the CSV export.

In practice, the team sees one clock. An agent in São Paulo, another in Lisbon and an automated email all show 15:59 for the same commitment — because the authority is the account, not the computer of whoever is looking.

What stays on the reader's own clock: conversation and message timestamps and activity trails ("5 minutes ago", "yesterday at 14:20"). Time there is relative to the reader by design, and that does not change.

Prerequisites

• Administrator profile, to edit account settings.
• Knowing which timezone represents your operation — usually where the team sits, or where most of your customers are.

Step by step

1. Open Settings → Account.
2. Find the Timezone field.
3. Pick your timezone from the list (for example, (GMT-03:00) Brasilia).
4. Save. From then on, every business date and time created or edited uses that timezone.

Platform operators can also view and adjust an account's timezone from the Super Admin console, under Accounts → edit account. The value is the same in both places.

Settings & options

If the field has never been filled in, Conversa Labs uses the timezone provided during initial signup. If there is none, it falls back to UTC — and in that case it is worth setting the correct value.

Use cases

• Distributed team. Agents in different cities and countries agree on deadlines without doing mental conversions.
• Campaign delivery. A campaign scheduled for 09:00 goes out at 09:00 in the account timezone, no matter who scheduled it.
• Contracts and documents. The date printed on the PDF matches the one on screen.
• Exported reports. The date column in the CSV matches the dashboard.

Tips, limits & best practices

• Existing records are not converted. Dates saved before the timezone was set stay as they were, so older and newer records may carry different interpretations. When reviewing an important older commitment, check the time and reschedule it if needed.
• Changing the timezone moves nothing. Changing it changes how everything is displayed, not the instant that was stored. A commitment still happens at the same moment; only the number on screen changes.
• Daylight saving time is handled for you. In timezones that observe it, a time that simply does not exist (the hour the clock skips) is adjusted to just after the jump, and a repeated hour resolves to the first occurrence. The field tells you when it makes that adjustment.
• Dates without a time have no timezone. A date-only field (just the day) is never converted — and should not shift a day when the timezone changes.

Troubleshooting

The time shown is a few hours off from what I typed. Check the timezone under Settings → Account. If the record was created before the timezone was set, it predates the correction: reopen the item and save the intended time again.

Each teammate sees a different time. That points to a screen still tied to the browser clock. Note where it happened (which page and which field) and send it to support, with an example of the expected and the displayed time.

The email shows one time and the dashboard shows another. Confirm both refer to the same record and the same field. If the difference persists, send support the email you received along with a link to the record.

I cannot find my timezone in the list. The list covers the world's standard timezones. If yours is missing, pick one with the same offset and the same daylight saving rule, and let support know.

See also

• Account, agents and teams
• Business hours, labels and attributes