Timezone in Reports and How It Affects Date Filters
Why the "Today" or "Yesterday" filters in Reports may not match your local calendar, and how to read them correctly.
The date filters in Reports (Today, Yesterday, Last 7 days, etc.) are calculated using the server clock, while the timestamps you see in the Inbox and the rest of Omnifox are shown in your personal timezone or your workspace's. This gap can make a "Today" count not quite match what you expect.
Where your timezone is set
- Profile → Timezone: your personal preference, used to display message times, notes, and activity in the Inbox.
- Settings → General → Timezone: the workspace's default, used as a fallback if you haven't set a personal timezone yet.
- If neither is set, Omnifox displays times in UTC.
How it works in Reports
Unlike the timestamps you see on your conversations, the "Today", "Yesterday", "This Month", etc. ranges in Reports are calculated against the server clock (UTC), without adjusting for your personal or workspace Timezone. This applies both to the charts and to the CSV export.
Example
You're a user in Ecuador (UTC-5). At 7:00 PM local time, it's already 12:00 AM UTC the next day. If an agent closes a conversation at that moment, Reports will count it under the UTC "day" that already rolled over, even though for you and your team in Ecuador it's still the same working day. That's why the "Today" filter can show fewer conversations than were actually closed by your local clock — the "missing" ones show up under "Yesterday" instead.
Tips
- If you need to match an exact calendar day in your own timezone, use the Custom filter and manually adjust the range for your offset from UTC.
- For same-day metrics, wait until the day actually ends in UTC (not your local time) before drawing final conclusions from "Today".
- This doesn't affect the times shown in the message Inbox — those are always converted to your timezone.
Troubleshooting
- "Today's numbers don't match what I see in the Inbox": that's the timezone gap described above, not a data error.
- "Last month's total looks cut off": check whether your comparison is crossing the UTC boundary versus your local timezone, especially near month-end.
Related articles
-
Customer support reports
Get to know Omnifox reports to measure volume, team productivity, and customer satisfaction.
-
Key metrics: CSAT, response time and resolution
Understand what CSAT, response time and resolution time measure, and how to improve them.
-
What the Reports module is and how to access it
An introduction to Omnifox's Reports module: what it measures, what it's for, and how to open it step by step.
-
Concepts: statuses, channels and metrics
The vocabulary you need to read your reports: what conversation statuses mean, what channels are, and how Omnifox calculates its key metrics.
-
The Overview Dashboard: KPIs and summary cards
A walkthrough of the main Reports screen: the KPI cards, the channel and status charts, the heatmap and the agent performance table.