Opening a customer hub

From Customers, click any row. Or use Cmd+K / Ctrl+K to open the command palette and type a customer name — you’ll jump straight to the hub.

The URL is stable per customer (/customers/[id]) — bookmark it, share it with a teammate, drop it in a ticket comment.

What's on the page

Each section below the header is fed by one or more integrations. A section only renders when at least one integration in that category is connected and has data for this customer.

Header — name, primary contact, locations, primary site, status badges (overdue invoices, open critical alerts, expired warranty count).
Tickets — open + recently-closed PSA tickets. Click any ticket to expand inline.
Devices / Assets — agents from each connected RMM. Inline lifecycle indicators when warranty, OS-EOL, or past-standard-age detections fire.
Alerts — RMM critical alerts, backup failures, security-posture issues. Deduped across providers.
Backups — Datto BCDR + Keepit + Veeam jobs with last-success / last-failure timestamps.
Licensing — distributor-side seat counts + cost (Pax8 today; Sherweb / Ingram / SYNNEX coming as Phases 141–143 land their rewrites).
Contracts & invoices — from your PSA and your billing system, side-by-side.
Documentation — Hudu / IT Glue / Egnyte shortcuts to this customer’s runbooks, passwords, files.
Timeline — chronological merge of every connected system’s events (ticket created, alert fired, payment received, backup failed) so you can reconstruct what happened across tools.

Inline actions — the verbs

The hub is the product’s center of gravity because every panel exposes the actions you’d normally context-switch for. From the same page you can:

Reply to a ticket and have it write back to your PSA.
Acknowledge or resolve an RMM alert; Vectis writes back to the originating RMM and stamps the audit log.
Create a new ticket against a specific alert or device — the ticket captures the linkage so it’s one click to come back.
Open a runbook from your documentation system.
Trigger a manual sync of the customer’s data from any connected integration.

Every write-back action is captured in the audit log with the full request payload. See Audit log.

Customizing the layout

Each user can hide and reorder sections under Admin → Customer hub. Workspace defaults are set there too. The dispatcher pinning Tickets + Alerts at the top and the account manager pinning Contracts + Invoices at the top can both be right.

Multi-customer search

Need to act on something across all customers — “all tickets opened in the last 24 hours”, “every device with a failed last backup”? That’s the Query Builder. The customer hub is for one-customer-at-a-time work; Query Builder is for cross-customer slicing.

If a section you expect doesn’t render, the most common cause is the customer not being matched to the underlying integration’s record. Open Admin → Customer matching to inspect and fix.