Skip to main content

​
Dashboard map — the top navigation and where each hub lands

The dashboard is one operator surface with a top-nav bar and a sidebar that changes with each hub. A new operator — or an agent migrating from another platform — taps a top-nav entry and expects to know which sidebar items belong to it and which page to open first. This page maps the top navigation, links each hub to its orientation guide or canonical entry page, and calls out the role gates so you know which hubs open for your seat. Every hub and console below is a tenant-owned control — you set it for your workspace, and nothing applies until you turn it on.

​
Section 1 — The dashboard’s navigation layout

The signed-in dashboard holds three regions:
  1. Top navigation bar — the horizontal bar at the top. It carries the app logo (links to Home), the sidebar hamburger, the command palette shortcut, and the user menu (Me).
  2. Sidebar — the vertical menu on the left. Its items change per hub — opening Messages swaps the sidebar to the messages-hub items (SMS, MMS, RCS, WhatsApp, and so on). The top nav names the hub; the sidebar lists the routes inside it.
  3. Main content area — the rest of the screen. The hub you pick in the top nav decides which page lands here.
The top-nav entries are: The Notifications bell and command palette (Cmd-K) sit in the top bar to the right of the hub entries; they are always reachable regardless of which hub is open.

​
Section 2 — Hubs with an orientation guide

Four hubs have orientation guides that walk every tile on the hub. Open these first: Each orientation guide answers the question every operator asks on a first visit: which tile do I start on? They link the in-depth guides and concept pages behind every console, so you do not need to open the per-feature docs to find the right page.

​
Section 3 — Hubs without an orientation guide

These hubs have a canonical entry page or a hub map instead of a full orientation guide. Open the listed page first.

​
Home

The Home page (/home) is the first surface after sign-in. Two guides cover it:
  • Navigate the dashboard Home page — a high-level orientation: what the greeting strip, bento metric tiles, channel-health track, banners, and Quick Actions each answer, and how white-label domains resolve after sign-in.
  • Read the dashboard Home page — a widget-by-widget walkthrough with the API endpoint each widget reads and the fetch-layer behavior.

​
Inbox

The Inbox hub (/inbox) holds every omnichannel conversation — SMS, WhatsApp, email, voice transcripts, and social messages — in one assignable, replyable list. Its settings surface has twelve operator consoles.
  • Start with the Inbox settings map — it names every console, what it controls, and which symptom-to-console path to follow when something is not working.
  • For the agent-facing Inbox itself (the reply surface), open Inbox setup.

​
Interactions

The Interactions hub (/interactions) is the cross-channel audit log — every voice call and messaging conversation in one recency-ordered list with asymmetric search-vs-export permission gates.

​
Campaigns

The Campaigns top-nav entry opens the same /outbound hub as the Outbound entry. The Outbound hub orientation covers both. For the first campaign, open Campaigns end-to-end.

​
Agents

The Agents hub (/agents) is the full AI-agent lifecycle surface — create, prompt, guardrail, evaluate, deploy, and monitor.

​
Quality

The Quality hub (/quality) holds scorecards, QA evaluations, coaching, and the performance leaderboard over your agents.
  • Start with the Quality hub overview — it maps the hub’s sections and the supervisor loop (review, calibrate, coach).

​
Insights

The Insights hub (/insights) is a grid of roughly thirty-five analytics tiles.
  • The Insights hub map is the fast index — one line per tile with the question it answers and when to open it.
  • The Insights hub overview walks the same grid top to bottom with worked examples.

​
Marketing

The Marketing hub (/marketing) groups wallet passes, loyalty programs, and referral programs.

​
Numbers

The Numbers hub (/numbers) covers purchase, port, configure, and release of phone numbers.

​
Developer

The Developer hub (/developer) holds API keys, webhooks, SDK docs, the API playground, and request logs.

​
Billing

The Billing hub (/billing) holds wallet balance, top-ups, usage records, invoices, and spend controls.

​
Settings

The Settings hub (/settings) holds organization profile, teams, security, compliance posture, data retention, and branding. It is the broadest hub and does not yet have a single entry page — open the console that matches your task:

​
Me

The Me flyout (user menu in the top bar) carries your profile, voice preferences, scorecard, and notification settings.

​
Section 4 — Scope and permissions

The top-nav bar shows every hub entry, but the role gate on each hub’s destination route decides whether a hub opens for your seat. Tapping a gated hub when your role is below the floor shows a forbidden page (403). The sidebar hides tiles that the destination route would reject, but the top-nav entries are always visible — this is a navigation aid, not a permission list. The role levels follow the Roles, teams, and permissions hierarchy: owner (100), admin (80), developer (60), billing (40), viewer (20), supervisor (15), marketer (13), analyst (12), agent (10), user (5). A route that gates on one role admits every role at or above that level — with the exception that billing is an orthogonal role that does not inherit and is not inherited by the hierarchy.

​
Section 5 — Cross-reference table

Hub to route prefix to the canonical page to open first.