🟣 HubSpot Service Practical Textbook — 2026 Edition
Chapter 2

Help Desk Workspace
The center of omnichannel supportdesign

Help Desk Workspace is the support team's ``headquarters'' that manages inquiries from multiple channels such as email, chat, phone, SNS, and WhatsApp on one screen. This workspace, officially released in spring 2025,AI support・SLA tracking・Collaboration・Switch between board view and list viewThis creates an environment where agents can move without hesitation about what to do next. This chapter explains screen configuration, view design, channel integration, collaboration functions, and how to properly use views.

📖 Estimated reading time: 30 minutes
🎯 Target: Support managers, agents, RevOps
📅 March 2026 version — Spring 2025 Workspace official release compatible

📋 Contents of this chapter

  1. 2-1Help Desk Workspace overview and screen layout
  2. 2-2View design: by team, priority, and channel
  3. 2-3Inbox and omnichannel integration (email, chat, SNS, WhatsApp)
  4. 2-4Collaboration features (internal memos, @mentions, shared views)
  5. 2-5How to use board view and list view
Section 2-1

Help Desk Workspace overview and screen layout

Help Desk Workspace (“Workspace”) is an integrated support team work environment available in Service Hub Professional and above. Resolved the previous problem where the "Inbox" and "Ticket List" were separated into separate screens,Reply to incoming messages, ticket management, SLA tracking, and cross-team collaboration all on one screen. We recommend an approach that starts with three custom properties: ticket category, scope of influence, and reason for closure, and then adds whatever is necessary during operation.

A ticket pipeline is a "mechanism that visualizes the process by which a ticket is resolved." It has the same structure as the opportunity pipeline in Sales Hub, but

HubSpot — Help Desk Workspace(Service Hub Professional)
The design perspective is completely the opposite: business negotiations are based on the actions of the salesperson, but ticket pipelines are designed based on the state of the resolution process.
📥 All tickets 24
🔴 SLA Danger 3
👤 my responsibility 8
🚨 Urgent / High 5
Waiting for customer response 7
🏢 VIP companies 4
📧 email 14
💬 low 6
📱 WhatsApp 4
All tickets (24) SLA deadline order ↑
#4821 10 minutes ago
API linkage error (payment processing)
Urgent SLA 1h remaining
Field
#4820 32 minutes ago
Unable to log in (two-factor authentication)
High Open
mountain
#4818 1 hour ago
Request a change of billing address
Medium waiting for customer
bell
#4815 2 hours ago
About garbled characters in CSV export
Medium Open
Field
#4812 3 hours ago
I would like to know how to share the report.
Low Open
tree
#4821 · API error · Urgent · SLA remaining 1h 12m
An error occurs when linking with API (payment processing)
⚡ SLA status
First response (1h 12m remaining)
Generate 1 article
👤 Customer information
contact
Taro Yamada (CTO)
Company / Health Score
Tech Force / 42⚠️
48 items this month
4 cases (+3 compared to last month)
🤖 AI suggestion (Breeze Copilot)
Draft reply
Mr. Yamada, thank you for your report. We will check the HTTP 422 error. Current API version and…
▸ Use this suggested reply
Compose reply (email)
none
internal memo
Send →

Workspace isLeft pane (view navigation), center pane (ticket list), right pane (details & replies)It has a 3-pane configuration. Switch ``which group of tickets to view'' in the left pane, determine priorities in the center, and reply while checking customer information in the right pane - this process is completed on a single screen.

Section 2-2

View design: by team, priority, and channel

Workspace's view is a filter setting for ``which tickets to view and in what order.''By designing an appropriate view, agents can instantly understand which tickets they should be handling today.. From Public Beta in November 2025, not only ticket propertiesYou can also narrow your view by contact/company properties.Now, advanced views such as ``VIP Contact Tickets'' and ``Enterprise Company Backlogs'' have been realized.

🚨
SLA risk view
A view that automatically extracts tickets whose initial response deadline is within 1 hour or whose resolution deadline has passed. Managers monitor and use it as a starting point for calling out to agents in real time.
Filter example: SLA status = Danger OR Overdue → Display in ascending order of SLA deadline
👤
My view
Displays tickets where Owner = yourself and Status ≠ Closed. Set this as the first view that agents open in the morning. By arranging tasks in descending order of priority, you can see at a glance the most important tasks of the day.
Filter example: Owner = Login user / Status ≠ Closed / Descending priority
🏢
VIP Corporate View (from November 2025)
This is made possible by filtering by contact/company properties. You can narrow down tickets based on conditions such as ``company plan is Enterprise'' and ``contact tag is VIP.'' Prevent failure to respond to top customers.
Filter example: Affiliate company plan = Enterprise / Status = Open → Ascending creation date
📧
View by channel
By creating a dedicated view for each reception channel, it is effective for teams with clear division of roles, such as ``WhatsApp person'' and ``email person''. Easier to manage response times for each channel individually.
Filter example: Reception channel = WhatsApp / Status = New OR Contact person is currently responding
🔧
Technical team view
Team-specific views filtered by team properties and categories. Function as a work queue for each team, such as "Category = Technical Defects and Team = Technical Support."
Example filter: Category = Technical Defect / Team = Technical Support / Descending Priority
Long outstanding view
Extract tickets that have not been resolved even after 3 days have passed since they were created. A view to take inventory of tickets that are in a pinch with weekly reviews. Operations that are checked by managers every Monday are effective.
Filter example: Creation date ≤ 3 days ago / Status ≠ Closed → Creation date ascending order
Pro+ (credit consumption)

There are two types of Workspace views: ``Just Me'' and ``Shared with Everyone.''Personal: My responsibility/my tasks for today. Team sharing: SLA risk/VIP company/long-term unresolvedThis is the basic usage. Team-shared views are created and managed by managers, and individual views can be freely customized by each agent, making it easier to establish an operation.

Section 2-3

Inbox and omnichannel integration (email, chat, SNS, WhatsApp)

Workspace's strength is that it "gathers inquiries from all channels on one screen." Agents no longer have to keep multiple tabs open for email, chat, and WhatsApp.Same view, same experience, same SLA management regardless of channelBeing able to respond in a timely manner reduces the agent's cognitive load.

📡 Omnichannel integration flow — all inquiries into one workspace
📧email
💬live chat
📱WhatsApp
📋form
📞phone
🗂️ HubSpot unified inbox
Messages from all channels are consolidated into one inbox. Ticketing, routing, and SLA measurement will start automatically.
🎫
Automatic ticket generation
Upon receipt, a ticket is created and enters the "New Arrival" stage of the pipeline. Created with no person in charge set
⏱️
Start SLA count
First response SLA countdown starts from ticket creation time. Deadlines are automatically set according to priority
🔀
automatic routing
Automatic assignment to agents and teams according to set rules (round robin, skill base, etc.)

Notes on settings for each channel

channelConnection methodNotes on settings
Email (Gmail/Outlook) Settings → Inbox → Add email → OAuth authentication If you set "All replies from HubSpot", be careful about mixing with existing email clients. Connect to team shared address and personal address separately
live chat Settings → Inbox → Add chat → Embed code on your website Be sure to configure the bot for non-business hours (switch to Breeze Customer Agent). Setting the time zone is important
WhatsApp Within 4 hours WhatsApp only requires a response within 24 hours when a customer contacts you for the first time. Template messages must be approved by Meta in advance
Facebook Messenger Settings → Inbox → Add Messenger → Connect with Facebook Page Requires Facebook page administrator privileges. Messages received via Messenger can be treated as tickets, but comments on public posts are managed separately.
Section 2-4

Collaboration features (internal memos, @mentions, shared views)

Ticket handling is often not completed by one person. Escalation to the technical team, consultation with the manager, handover to other agents—theseCommunicating within the team “within the ticket record” is the key to preventing information dispersion and ensuring uniform response quality.is.

📝
Internal Note
You can record internal comments on the ticket timeline that are invisible to the customer. Used to hand over the response status, such as "Checking with the technical team" or "Escalated/see ticket #4781." In the reply box, select the "Internal Memo" tab and enter.
@
@mention
If you enter @username in an internal memo or comment, that user will receive a notification. You can ask other agents or your manager to take action without leaving the ticket by saying something like, "@Tanaka, please check the cause of this error."
🔔
Ticket subscription (Watch)
Even if you are not the person in charge, if you set the ``Watch this ticket'' setting, you will receive a notification every time a reply, stage change, or memo is added. By monitoring important tickets, managers can grasp the situation before it escalates.
🔗
Linking between tickets
Related tickets can be linked together. The ``parent-child ticket'' configuration, which consolidates multiple tickets caused by the same bug into a parent ticket and manages them all at once, is especially effective for technical support teams.
📋
shared view
Mon-Fri 09:00–17:30
🤖
Breeze Copilot Reply Suggestion
Breeze Copilot auto-suggests suggested replies in the ticket details pane. Since it is generated by referring to the contents of the knowledge base, past similar tickets, and customer information in the CRM, agents only need to review, edit, and send the proposal.
💡 Internal memos affect the “quality of handover”

When an agent leaves the office, goes on vacation, or is suddenly absent, the internal memo is the first thing the colleague who takes over the ticket sees.The habit of writing internal notes about how far you have investigated, what you should do next, and what you communicated to the customer.By ensuring that all agents are aware of this, SLA violations due to handover losses can be significantly reduced. We recommend that you make ``No handover without notes'' a team rule.

Section 2-5

How to use board view and list view

Help Desk Workspace allows you to display tickets in"List view" and "Board view"You can switch with . Board view was officially added in the March 2025 update, allowing tickets to be displayed in columns by pipeline stage. The two views have different uses,It is important to use them properly depending on the role and purpose.is.

📋 List view
Ideal for agents' daily work and SLA management
#4821 API linkage error (payment) Urgent
#4820 Can't log in High
#4818 Change billing address Medium
#4815 CSV garbled characters Medium
✓ Situations where list view is suitable
I want to quickly check tickets in order of SLA and priority.
Scan a list of large number of tickets and determine their priority
Managers check the amount of work handled by each agent
Make frequent use of precise narrowing down using filters
🗂️ Board View (from March 2025)
Ideal for understanding the entire process status and moving stages
New arrival
Unable to log in
Invoice correction
Currently being supported
API error 🔴
waiting for customer
Checking settings
completion
PW reset
KB confirmation
✓ Scenes where board view is suitable
Visually spot blockages in your team's ticket processing flow
Quickly update ticket stages with drag and drop
Share your overall progress with daily stand-ups
Manage highly project-oriented responses such as onboarding tickets
comparison axislist viewboard view
Main users agent for daily work Manager/Team Lead
Amount of information that can be displayed at once Many (displays information in multiple columns as a list) Few (mainly card titles)
Stage change operation Select from dropdown Intuitive drag and drop
Discovering bottlenecks Difficult (hard to see the number of cases) You can see at a glance which stage you are stuck in based on the height of the row.
Check SLA time remaining Can always be displayed as a column Badge displayed on card (limited amount of information)

Merely setting and implementing SLAs is not enough.

Workspace completes agent work with a "3-pane structure"

With a left pane (view), center pane (ticket list), and right pane (details & replies), agents no longer need to go back and forth between multiple tabs. Breeze Copilot's reply suggestions are also integrated into the right pane.

The view is designed first with "SLA Risk/My Responsibility/VIP Company"

By making it possible to filter by contact/company properties (from November 2025), advanced views such as "VIP Contact Open Tickets" have been realized. Manage personal and shared use separately.

① 1 article 1 topic

Turn on the "Always create tickets" setting for all emails, chats, WhatsApp, and forms. SLA and routing rules for each channel can also be set for each inbox.

Consolidate team communication within tickets with internal memos and @mentions

Stop using Slack or verbal handovers, and get everyone into the habit of writing in internal memos, ``How far have we investigated so far and what should we do next?'' We recommend that you make ``No handover without notes'' a team rule.

List view is used for daily work, and board view is used for checking progress.

List view is suitable for agents' daily work (responding in SLA order/priority order), and board view is suitable for managers' daily confirmation and stage updates using drag and drop.

Managers use “SLA Risk View” and “Board View” for morning confirmation.

Every morning, check the SLA Danger view for expired and dangerous tickets, and check the board view to see which stage tickets are stuck in. Establish a management routine based on these two views.

Next Chapter
Chapter 3: SLA design and operation — Practice setting response times, resolution times, and business hours →