Sense Home is the AI home surface in the xMatix web app: a short written brief on your day, the key numbers, a ranked queue of things worth acting on, and outside context from your industry. It is not a hardcoded dashboard — it is an ordinary app page your organization composes from Sense widgets, so a sales workspace's home and a service workspace's home can legitimately look different. Everything on it is drawn through your own permissions.
The four blocks
| Block | What it shows |
|---|---|
| Morning brief | Two to four written sentences over a deterministic fact pack, cached for the UTC day unless you explicitly regenerate it |
| KPI strip | Summary figures from the entities your workspace tracks, read through the same permission-enforced path as the list screens |
| Attention queue | A ranked, capped feed of your live nudges from across the workspace |
| Industry pulse | Headlines and developments from outside your organization, for context next to your own numbers |
The morning brief
The brief is a writing task, not an analysis task. Before any model is involved, the server assembles a deterministic fact pack — summary figures from your workspace's entities, read with your permissions, plus your top-ranked nudges — and the model's only job is to turn those supplied facts into a few readable sentences. It is instructed to use only the facts provided: no arithmetic of its own, no inferred numbers.
The normal load is cached per user, UTC day and configured entity set. The regenerate control deliberately bypasses that cache, rebuilds the fact pack and replaces today's cached result; it is a metered model call when AI phrasing succeeds. On a quiet day the service reports that there are no KPI signals or attention items. If the model call fails or a quota check blocks it, a deterministic template is returned instead; template results use a shorter retry cache so the page can recover when data or capacity becomes available.
The attention queue
The queue gathers active nudges across entities rather than only the record currently open. The default widget requests up to eight items and at most three from one category. The service ranks them deterministically; the widget refreshes after live nudge invalidation, when the window regains focus, on an optional interval and when the user presses Refresh. Designers can change both caps, so regard eight and three as widget defaults rather than a tenant-wide rule.
Each row is a full nudge card: dismiss, snooze for a day or a week, Why? to open evidence, mutating actions that use the signed-in user's entity services after confirmation, and Ask Sense AI to open chat with the nudge context. Only a successful mutating action marks the nudge Applied. Navigation, Why? and chat do not resolve it. Dismiss and snooze remove the card optimistically, so a request failure can make it reappear after a later refresh.
KPI strip and industry pulse
The KPI strip is the numbers block: summary figures for the entities your workspace is configured to track, identical to what the corresponding list screens would show you. Industry pulse is the one block that looks outward — a feed of industry headlines and developments — and it depends on web retrieval being available in your deployment; where that is switched off, the block simply hides.
When blocks are missing
Sense Home fails open. A block whose feature is off, whose license is missing, or whose data is unavailable renders nothing — not an error — so a partially licensed organization sees a smaller page, never a broken one. Two other absences are worth knowing about: Sense Home is web-only today (the mobile app shows nudges on records and lists, which suits work in the field, but has no composed home surface), and because the page is composed per organization, it exists only once someone has authored it for your workspace.
Common questions
Why does my Sense Home look different from a colleague's?
Two reasons compound. The page itself is composed per workspace, so different roles can be given genuinely different layouts — a different KPI strip, a differently filtered queue. And within any layout, every block is permission-scoped: the brief, numbers and nudges are built from what each viewer is allowed to see, so even the same layout reads differently for different people.
Why doesn't the brief change during the day?
Ordinary loads reuse the per-user daily cache. Press Regenerate brief when you intentionally want a fresh fact pack and new phrasing; that bypasses and replaces today's cache. The attention queue refreshes independently, so its contents can change even while the brief remains cached.
Why don't I see the industry pulse block?
Either your organization's Sense Home layout doesn't include it, or your deployment has web retrieval disabled — the block needs outside access and hides itself when that is unavailable. Blocks on this page never render an error state; absent means off or unavailable.