Skip to main content

​
Read the dashboard Home page

The Home page (/[locale]/home) is the first surface every signed-in user lands on after login, and the answer to “is my account healthy right now?” before you open anything else. One glance gives you today’s message volume and delivery rate, each channel’s status, and the most recent platform activity — with deep links to the console that explains any number that moved. Everything below walks the page top to bottom in the order you see it.

​
1. Greeting header

The page opens with a time-aware greeting plus today’s date, then a one-line context summary underneath: “N messages sent in the last 24 hours — X% delivered.” When you have no traffic in the window the summary falls back to a no-messages line instead of inventing a zero-percent rate, and when delivery receipts haven’t come back yet (a fresh send, a DLR backlog) the ”% delivered” clause drops rather than claiming an unknown rate. Next to the summary sit quick stat pills — compact chips that echo the rolling-24-hour trend (up/down) for messages and the count of open inbox conversations, each linking to the surface behind it. The greeting is the page’s headline element, so it renders first while everything below streams in.

​
2. Hero metrics (the bento grid)

The Overview section below the greeting is a bento-style grid of KPI tiles: messages sent, delivery rate, spend, balance-related tiles, plus a channel-mix breakdown. Each tile pairs its headline number with a trend sparkline, so you can tell whether the value is moving before you drill in. Above the grid sits a timeframe picker (24h / 7d / 30d / 90d / Custom). The 24h preset is the default and matches every other 24-hour surface in the dashboard; picking a longer window re-reads the delivery-rate and spend tiles over that range (and accepting a custom calendar range pins the window to exact dates). Switching ranges keeps showing the previous values while the new window loads — the tiles never blink to zero mid-switch. The grid’s last row is the Activity feed (section 5).

​
3. Channel health row

The Channels section renders one card per active channel — SMS, WhatsApp, email, voice, and any other channel your workspace has enabled. Each card shows the rolling-24-hour picture for that channel: operational / degraded / down status, measured latency where the channel reports it, volume and delivery rate in the window, and an uptime percentage. When a channel degrades, its card surfaces an Investigate link that lands you on that channel’s message hub (/messages/<channel>) with the failure context pre-filtered — this is the fastest path from “a card went red” to the delivery receipt that explains why. Cards degrade as a group through an impact banner at the top of the row, so one bad channel reads as one banner instead of five red tiles. The channel-health values are tenant-owned measurements of your own traffic — the same feed the Messages hub cards read — not a platform-wide status page. For the sub-signals behind each tile, how a red tile lags a live gateway view, and the time-boxed recovery sequence to run when one does, see Read the channel health widget.

​
4. Quick Actions

Quick Actions is a row of tiles linking straight into the operations you run most: send a message, create a campaign, import contacts, build a flow, open the inbox, add credits, view reports, and more. The exact tile set adapts to your workspace — a billing-seated user sees balance and invoice tiles, a developer-seated user sees API keys — and each tile is a deep link, so the destination opens with no extra navigation.

​
5. Activity feed

The Activity feed is the recent-events list: message sends and their terminal status, campaign completions, webhook deliveries, contact imports, agent runs, API events, and configuration changes such as webhook-endpoint updates. Events group per day (“Today”, “Yesterday”, or the date), so a busy feed stays scannable, and each event carries its type icon, a timestamp, and a status label. This feed is the top slice of the same activity stream the full Insights → Logs viewer reads — Home shows the most recent handful and links out when you need the wider window, filtering, or event detail (see Insights → Logs viewer).

​
6. Intelligence and insights grid

The bottom grid assembles the “what’s happening with my account” cluster:
  • Smart insights — generated observation cards (delivery-rate moves, unusual volume, billing anomalies), each with a link to the surface that backs the observation. A workspace with nothing to report collapses the tile entirely instead of showing placeholders.
  • Customer health — the predictive segment distribution over your contact list; clicking a segment filters the contacts list to it.
  • Spend forecast — daily spend over the last 30 days, a 7-day projection, and anomaly highlights. This tile is billing-seat gated: roles without billing visibility don’t see it.
Each card in this grid is a compact read of a deeper surface — Smart insights resolves to Ask your data insights class analysis, Spend forecast to the billing consoles — so treat the grid as triage and the linked page as the explanation.

​
7. Where each widget’s data comes from

Every tile on Home is a client render of a documented stats endpoint, so anything you see on the page you can also read from a script or wire into your own monitoring: Two fetch-layer facts explain the page’s behavior:
  • Request consolidation. Widgets that read the same endpoint share one in-flight request — the greeting, the error classifier, and the hero tiles all resolve against the same /stats/summary fetch rather than polling independently. The channel-health and activity polls refresh on a 30-second cadence and stop when a session expires, so an idle logged-out tab doesn’t spin.
  • Query dedupe across surfaces. The Messages hub cards read the same channel-health query key, so opening a Messages page from Home shows already-fetched data instead of a second request.
The full endpoint catalog, common-window semantics, and guidance on reading summary vs. analytics windows lives in the stats API guide. For role-filtered Quick Actions tiles, white-label domain resolution after sign-in, and what to check when the page stalls on skeletons, see Navigate the dashboard Home page.

​
8. Pending, empty, and pre-first-data states

Home is a fully client-rendered route, and it is deliberately built to never show you a broken intermediate state:
  • Skeletons reserve the settled footprint. Every widget paints a placeholder shaped like its final content — the greeting reserves its summary line and pill row, channel health reserves its banner plus five-card grid, the feed reserves two short rows. Values grow into the reserved space rather than shoving the page around, so the first paint doesn’t jump when data arrives.
  • The provisioning window. Right after signup, while your workspace is still being created, Home shows a “Setting up your workspace” panel that walks each setup step and polls until it’s ready. Data widgets stay hidden during this window instead of erroring against a not-yet-ready account. If setup crosses five minutes, the page offers a retry and support path instead of spinning forever.
  • Partial failures surface once at the top. Each widget loads independently and contains its own errors; if any of them fails, a single page-level warning banner aggregates the failed sections so you’re never reading an incomplete KPI set unaware. A widget that fails to load offers its own retry without tearing down the rest of the page.
  • Empty states self-hide. Tiles with nothing to report — no smart insights, no trial promotion needed, no open fraud alert — remove themselves entirely rather than rendering placeholder content. The greeting handles the zero-traffic case with its explicit no-messages line.
  • Range switching is non-destructive. Changing the hero-metric timeframe keeps the previous values on screen until the new window arrives; tiles never flash empty.

​
9. How Home differs from the full Insights dashboards

Home is a triage surface: it compresses the rolling 24 hours (or your picked window) into glanceable tiles and routes you onward via Investigate links, Quick Actions, and insight cards. The Insights dashboards are the analysis surface: cohort retention, journey paths, funnels, deliverability scoring, topic intelligence, containment, LLM spend, and the full log viewer — arbitrary ranges, per-channel breakdowns, and drill-through. Rule of thumb: Home answers “do I need to look closer right now?”; Insights answers “why, and what do I do about it?“

​
10. Getting help without leaving the dashboard

Every signed-in page carries a small chat bubble at the screen edge. Open it and you are talking to Devotel support from inside the dashboard, with no ticket form and no page change. The section below covers what the bubble is, when it appears, how it differs from the other help surfaces, and what to include so your first message gets a fast answer. What it is. The bubble is Orbit’s live-chat channel to the platform’s support team. It appears only after you sign in, on every dashboard page, and stays available while you work. A conversation goes straight to the Devotel support queue; the team sees your name and the email address you are signed in with, which is usually enough to identify your workspace. Responses come through the same chat window while you are signed in. The bubble makes no response-time promise and is not a 24/7 commitment. For platform-wide incidents, the status page remains the source of truth. When it appears. The bubble loads only inside the authenticated dashboard. Public pages, the marketing site, and the sign-in and signup screens never show it, and signing out removes it. Workspaces reached through a reseller’s white-label login get the same bubble, and conversations still land with Devotel support; if your provider runs your help desk, keep using their channel for account questions with them. What it is not.
  • It is not the chat widget you embed on your own site. Web support end to end documents the widget your visitors talk to; that one routes into your inbox for your team to answer. The dashboard bubble runs in the opposite direction: it is your line to Devotel support.
  • It is not the status page, which reports platform health and incidents.
  • It is not the help center, the hosted guide and FAQ portal you can brand for your own customers.
Getting a fast answer. Lead with identifiers, not narrative. Your organization ID lives under Settings → General; for a failing API call, the request ID is on the row in Developer → Request logs, and the status page guide shows where incident identifiers live. A one-line description of what you expected versus what happened, plus the channel and number or campaign involved when relevant, turns the first reply into a lookup instead of a back-and-forth. What the bubble carries. A message you send, together with your signed-in name and email address, goes to the Devotel support backend that hosts the chat. Nothing else from your workspace is attached: message content, contact records, and call data stay in your workspace unless you paste them into the conversation yourself. The chat is separate from the visitor session recording your workspace may run, which Session replay covers; recordings of your own dashboard sessions follow the retention posture described there.

​
See also