Omniscio

Inbox Attention Analytics — how your inbox triage behaves

A built-in, entirely local report on how you work your Omniscio inbox — how long items wait before you clear them, how deep the backlog gets, how often you open an item and move on, and how long you look at each one. It is the inbox counterpart to UI Usage tracking, and nothing it measures ever leaves your machine.

On this page

What it is

Library page — describes what users see and how it works, self-contained so an outside AI with no repo access can answer "what is Inbox Attention Analytics and how does it work?"

Inbox Attention Analytics is a built-in, 100% local report on how you work your Omniscio inbox — not what's in it, but how it behaves: how long items wait before you clear them, how many pile up on average, how often you open an item and move on without acting, and how long you spend looking at each one. It answers "where does my triage time go?" and surfaces the answer in a new Inbox tab inside the Stats virtual project.

It is the inbox counterpart to UI Usage tracking: both quietly record lightweight signals on your own device and show you a picture of your own habits. Nothing here ever leaves the machine.

Where to find it

  1. Open Omniscio.
  2. In the project sidebar, open the Omniscio group and click Stats (chart icon).
  3. In the Stats sub-sidebar, pick the Inbox tab (second, right under Overview).

The Time Range selector (Today / Yesterday / 7d / 30d / 90d / All) filters every number on the tab, exactly like the rest of Stats.

How it behaves

What it shows

  • Four headline tiles — Avg time to clear (how long an item waited before you cleared it, with "N cleared by you · M resolved on their own" under it), Avg items waiting (the time-weighted average of the measured inbox size over the window, "—" until a first reading exists), Looked without acting (how many times you opened an item and moved on with no action, plus that as a % of views), and Avg view time (how long you spend on a single item per view).
  • Items waiting over time — a per-day bar strip of the measured number of items in the inbox at the end of each day, so you can see the backlog rise and fall.
  • By type — the same stats broken down by item type (session, SMS, daily digest, cron approval, alert, …).
  • By project — broken down by the owning project (resolved to the project's name, or the hub's name — System Alerts, Help Desk, … — for built-in inbox hubs).
  • Top sessions — the sessions you triaged most, with their clear/view stats.
  • Actions taken — how items left the inbox: dismiss / approve / reject / snooze counts.

An empty state ("No inbox activity tracked yet — triage some inbox items and check back") shows until there's data; a "Tracking since <date>" note shows how far back it goes.

How the metrics are defined

  • Cleared — an item you cleared yourself: you replied to, archived, snoozed, dismissed, approved or rejected it, on any device. An item that left the inbox without your action (an agent replied, an alert healed itself) is counted as resolved on its own and kept out of the clear stats.
  • Age / time to clear — the interval from when an item first appeared in the inbox to when you cleared it.
  • Average items waiting — measured: the desktop app records how many items are in the inbox (after a short warm-up at launch, when the number changes — at most every five minutes — once a day, and when the app closes). The report takes the time-weighted average of those readings; the chart shows each day's last reading.
  • Looked but didn't act — a completed view counts as this when you opened the item and took no action during it. A view pauses when you switch to another window and resumes when you come back, so an unattended window never piles up view time. Sub-second views (auto-select flashes) are ignored.
  • View time — how long a single item was the open item while you were looking, per view.

The setting, and privacy

  • On by default. A "Track inbox attention analytics" toggle in Settings → Diagnostics turns it off; when off, no new events are recorded at all.
  • On-device only. The report is built entirely from a local database and is never sent anywhere — it is deliberately kept out of the anonymous fleet-telemetry digest, and its table is classified so it is never merged into a portable backup that moves to another machine.
  • No content, ever. Only bounded dimensions leave the renderer — the item type, the project id, and (for session items) the session id — plus the computed durations. No message content, titles, phone numbers, or raw item ids are stored; the correlation key the tracker uses to pair an arrival with its clear stays in memory and is never persisted.
  • Retention. Events are pruned after 90 days (and above a row cap) by the same local background sweep that prunes the other local logs.

Limits

  • View time and looked-but-didn't-act only count while the app is open on the item.
  • Items-waiting history starts with the first measured reading (the October 2026 fix); earlier days have no bar, because the older running total was wrong and was retired.
  • Arrivals, clears and items waiting are recorded by the desktop app only, so a phone or browser looking at the same inbox never double-counts them; views count everywhere.
  • Stats — the parent virtual project (cost, tokens, time, spend, feature usage).
  • UI Usage tracking — the sibling local "how you use the app" report.
  • Inbox overview — the unified inbox these metrics measure.
  • Inbox Pilot — the AI that triages the inbox for you (a different system).

Last verified 2026-09-23