Skip to main content

​
Overview

Every workspace has a time zone. RevyOps uses it to decide where one day ends and the next begins, so “today” in a filter, a score’s age and a daily workflow check all follow the workspace’s own calendar instead of UTC.

​
Setting the time zone

​
Agency default

Agency admins set the agency’s Default time zone under Settings → Agency → Agency details, next to the Agency name. Workspaces set to Agency default, including new ones, use this zone; changing it moves all of them and recalculates their scores.

​
Per workspace

Under Settings → General → Workspace details, the Time zone field shows the zone the workspace uses and a “Current time: …” line for it. Choose:
  • Agency default, to follow the agency’s default time zone. The link is live: when an Agency admin changes the default, every workspace that follows it changes too.
  • A specific zone, to give the workspace its own.
Agency admins and Workspace admins can change it. Members see it read-only.
When you change the zone, a warning explains what happens on save:
  • Filters, saved views and workflow triggers count days in the new time zone once you save.
  • Scores are recalculated for the new calendar days, so some of them may change.

​
What the time zone changes

​
Filters and saved views

Filters and saved views count calendar days in the workspace’s time zone:
  • “today”, “yesterday”, “this week”, “last N days” and the other relative ranges. Weeks start on Monday.
  • Absolute dates on timestamps: before, after or between a date means that date in the workspace’s time zone.
  • Activity windows in Find Records, such as “has been emailed by us today” or “Last reply received is yesterday”.
Timestamps stored on synced records, such as a HubSpot or Close deal close date that carries a time, or a meeting’s start time, are converted to the workspace’s day before they’re compared. Plain dates without a time, such as custom date fields and Close won dates, are compared as written.

​
Scores

Scores age on the workspace’s calendar days, for decay, windowed scores, frequency caps and score history alike. Daily decay runs at midnight in the workspace’s time zone. Changing a workspace’s time zone recalculates its scores.

​
Workflows and saved view syncs

Saved views with relative dates re-sync, and workflows re-check who is in their view, at midnight in each workspace’s time zone. Daily limits on view syncs count the agency’s day.

​
Lists, records and reports

Dates and times on lists, record pages, reports and workflow Run History show in the workspace’s time zone. Report date presets (with weeks starting on Monday), campaign reports and Reply Timing use it too.

​
MCP

list_clients returns each workspace’s time_zone. Day-based filters and activity windows your agent builds count the workspace’s calendar days.
The REST API still stores and returns timestamps in UTC. See Dates and Timezones.