Problem today: Filters let you slice data by day, week, or date range, but not by clock-hour windows within the same day — so a customer can't isolate "08:00–10:00 vs 10:00–12:00 today" without exporting raw data.
Proposed capability: Add a time-of-day filter/comparison layer on top of existing dashboard filters, letting users define two (or more) intraday windows and see side-by-side deltas in NPS/CSAT, volume, sentiment, or topic mix — on the same day or across days.
3 use cases:
Shift/staffing performance — A contact centre manager compares CSAT for the morning shift (08:00–10:00) against the shift after a team changeover (10:00–12:00) to see if service quality drops or improves post-handover.
Operational incident isolation — When a system outage or store closure happens at a known time, a CX lead filters feedback just before and after that window to quantify the immediate impact on sentiment, without it being diluted by the full day's data.
Campaign or price-change reaction — Marketing pushes a promotion or price change at 10:00; the team compares feedback sentiment and mention volume in the two hours before versus the two hours after to gauge real-time reaction speed.
Why it matters: Positions Netigate Insights as a real-time operational tool, not just a retrospective reporting layer — reinforces the "why, what to fix, act fast" narrative rather than "more dashboards."
@Guest do you want this to live within the calendar tool, or within a filter?
In theory customers can already submit "timeframe = 8:00" and just replace 8:00 with other time frame values. Then you could filter to those values. You should also be able to use Filter Buckets for this? And then in theory it should be added to a graph.
I guess I am asking if there is some benefit to adding this as a calendar field to "date" instead of as a background variable we already support