HubSpot Service Software study materials
HubSpot Service Software study resources

HubSpot Service Software: Service Hub Software: help desk, ticketing, and shared inbox fundamentals

HubSpot Service Software · Work through your exam, one topic at a time.

All guide sections

Service Hub Software: help desk, ticketing, and shared inbox fundamentals

Service Hub Software: help desk, ticketing, and shared inbox fundamentals

This domain tests how HubSpot Service Hub organizes customer communication and service work: the shared inbox, the ticket object, pipelines, properties, and the handoff between a conversation and a ticket. Expect scenario questions about where a message appears, what a ticket records, and which setting controls ownership or visibility.

Core rules

  • A conversation is a communication thread. A ticket is the record of work that must be tracked, measured, and reported. They are related but not interchangeable.
  • The shared inbox connects channels such as team email, live chat, forms, and messaging. Agents see conversations in one place; assignment, status, and team permissions control who handles them.
  • Tickets live in pipelines. Each stage represents a service lifecycle, and ticket properties such as priority, source, category, and owner drive filtering, automation, and reporting.
  • Creating a ticket from a conversation associates the thread with the ticket, preserving context. Closing a conversation does not automatically mean the ticket is resolved; the ticket stage must reflect the work.
  • Inbox views and ticket views are saved filters. They change what an agent sees, not the underlying record.

Worked example

A customer emails support@. The message appears in the shared inbox. The agent replies, then creates a ticket from the conversation. A workflow sees the ticket's priority property set to high and assigns it to the escalations team, while the ticket stage moves from New to In progress. The agent later moves the ticket to Closed after confirmation and closes the conversation. Reasoning: the conversation held the message, the ticket held the work and ownership, and the property triggered routing.

Traps

  • Treating the inbox as the system of record.
  • Closing a conversation while leaving the ticket open, or the reverse.
  • Assuming every channel automatically creates a ticket.
  • Hard-coding an owner instead of using routing or assignment rules.