The Servicehub is where your support team works. It replaces the separate Tickets, Knowledge Base, and Surveys pages with a single, deep-linkable workspace that has four sections. Every section runs on the same customer records your sales team already uses, so a support agent sees the open deal value, account tier, renewal date, owning rep, and recent sentiment for the person they are helping — with zero integration.

A horizontal section nav at the top of the hub lets you switch between the four sections. The nav carries live counts — for example the number of open tickets waiting in the Inbox — so you always know where work is piling up. On mobile, the section nav collapses to a dropdown.

The Team performancelens of the Overview breaks the numbers down per agent. Each row shows an agent's current open load alongside their median first-response time, median resolution time, and median CSATover the selected window. Medians (rather than averages) keep one unusual ticket from skewing the picture, so a lead can spot who is overloaded, who is fast, and where satisfaction is dipping — and coach from real numbers. An agent with no tickets in the window simply shows a dash for the medians, never a misleading zero.

A gear affordance in the section nav opens Service Settings, where users with the right permissions configure SLA targets, ticket queues, reply macros, and the AI autonomy policy. The gear only appears if you have access to at least one settings area, so agents without admin rights never land on an empty page.

The Service hub appears in the sidebar for anyone who can view tickets, the knowledge base, or feedback. Within the hub, each section and action is gated by its own permission — for example, replying to a ticket needs ticket edit rights, and editing the autonomy policy needs the autonomy admin permission. The built-in Servicerole grants the day-to-day support agent everything they need; admins can fine-tune any role under Roles & Permissions.