I85PREP
⌘ K
HubSpot Service Software study materials
HubSpot Service Software study resources

HubSpot Service Software practice questions

One question at a time. Build your HubSpot Service Software understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

In the Service Hub help desk, what does the inbox primarily represent for a support team?

  1. A marketing calendar that schedules email campaigns to contacts
  2. A shared channel where conversations from connected email addresses and channels are organized for the team Correct answer.
  3. A billing module that invoices customers for support time
  4. A private mailbox that only the assigned owner can view and reply to

Explanation

The help desk inbox is a shared workspace that collects incoming conversations from connected channels so any authorized team member can view, assign, and respond. It is not tied to a single private mailbox, and it does not handle marketing scheduling or billing.

Question 2Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

A support agent wants to convert an incoming help desk conversation into a tracked support record that can carry pipeline status and reporting properties. Which object does the ticket represent?

  1. A deal record that tracks revenue forecasting
  2. A contact record that stores email and phone details
  3. A company record that groups associated contacts
  4. A support request with its own status, priority, and owner fields Correct answer.

Explanation

A ticket is the Service Hub object built to represent a support request, and it carries support-specific properties such as status, priority, and ticket owner. Contacts and companies describe people and organizations, while deals track sales revenue.

Question 3Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

When a customer replies to a support thread, where does the reply appear by default in the help desk?

  1. On the existing conversation thread so the full exchange stays together Correct answer.
  2. Only in the customer's contact record timeline, not in the inbox
  3. In a deleted folder until an agent restores it
  4. As a new separate ticket that must be manually linked

Explanation

Replies from the same thread are threaded onto the existing conversation, preserving context for any agent who picks it up. The conversation stays in the inbox and is also reflected on the associated records' timelines.

Question 4Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

A team lead wants every new help desk conversation to be assigned automatically to the next available agent. Which help desk capability supports this?

  1. Inbox routing rules that assign conversations based on availability or criteria Correct answer.
  2. Form submission notifications sent to the record owner
  3. List segmentation based on ticket properties
  4. Workflow-based contact scoring

Explanation

Help desk inbox routing settings can automatically assign incoming conversations to specific users or to agents based on availability and rules. Contact scoring, form notifications, and list segmentation do not perform live conversation assignment.

Question 5Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

Which ticket property is designed to capture how urgent a support request is relative to others?

  1. Ticket status
  2. Ticket priority Correct answer.
  3. Ticket source
  4. Ticket pipeline

Explanation

Priority is the property that ranks urgency so agents can triage which requests need attention first. Status tracks where the ticket is in its lifecycle, pipeline defines the stages, and source records where the ticket originated.

Question 6Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

An agent resolves a customer issue and wants the ticket to reflect that the work is finished. Which action best matches the ticket lifecycle?

  1. Move the ticket to a closed status in its pipeline Correct answer.
  2. Delete the ticket to remove it from reporting
  3. Change the ticket owner to the customer
  4. Convert the ticket into a marketing email

Explanation

Closing a ticket means moving it to a closed stage in its pipeline, which records resolution and removes it from active queues while preserving history. Deleting it loses reporting data, and the other options are not lifecycle actions.

Question 7Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

What is the purpose of associating a ticket with a contact in Service Hub?

  1. It links the support request to the person so their history and details appear alongside the ticket Correct answer.
  2. It automatically deletes other open tickets for that person
  3. It prevents the contact from submitting future support requests
  4. It converts the contact into a company record

Explanation

Associations connect records so agents can see the customer's details and prior interactions while working the ticket. Associations do not delete records, block future requests, or change a contact into a company.

Question 8Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

Which statement best describes the role of a knowledge base in the Service Hub support workflow?

  1. It stores internal billing records for finance review
  2. It replaces the help desk inbox entirely
  3. It hosts help articles that agents can reference and customers can self-serve Correct answer.
  4. It manages the sales pipeline for new deals

Explanation

A knowledge base holds help content used both by agents answering questions and by customers searching for answers themselves. It complements the help desk rather than replacing it, and it is unrelated to billing or sales pipelines.

Question 9Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

A support manager wants to measure how long agents take to send a first reply to new conversations. Which metric should the manager review?

  1. First response time Correct answer.
  2. Email click-through rate
  3. Contact creation rate
  4. Ticket close rate by pipeline stage

Explanation

First response time measures the interval between a customer's message and the agent's first reply, which is exactly the wait the manager wants to track. Close rate, contact creation, and email click-through measure different outcomes.

Question 10Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

An agent wants to save a set of recurring replies for common questions so teammates can insert them consistently. Which help desk feature is intended for this?

  1. Deal stages
  2. Contact lists
  3. Ticket pipelines
  4. Snippets Correct answer.

Explanation

Snippets store reusable blocks of text that agents can quickly insert into replies, keeping messaging consistent across the team. Pipelines, lists, and deal stages organize records or processes, not reply content.

Question 11Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

A customer submits a request through a support form. The team wants the form submission to create a ticket automatically with the customer's details attached. What should be configured?

  1. A form-to-ticket automation that creates a ticket and associates the contact Correct answer.
  2. A blog subscription that adds the contact to a newsletter list
  3. A deal rotation rule that assigns the submission to a sales rep
  4. A marketing campaign that sends a follow-up email

Explanation

Automation can create a ticket from a form submission and associate the submitting contact so the request enters the help desk with context. Marketing campaigns, deal rotation, and newsletter subscriptions do not produce support tickets.

Question 12Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

Two agents are viewing the same help desk conversation. One agent assigns it to themselves. What is the primary benefit of explicit assignment in a shared inbox?

  1. It hides the conversation from the customer permanently
  2. It deletes the conversation from other agents' views
  3. It automatically closes the ticket and stops all notifications
  4. It signals ownership so teammates know who is responsible and avoid duplicate replies Correct answer.

Explanation

Assignment makes responsibility visible in a shared space, which reduces duplicated effort and clarifies who should respond next. It does not hide the conversation from the customer, auto-close the ticket, or delete it from teammates' views.

Question 13Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

A support team receives a high volume of password reset questions. Which combination best reduces agent workload while still helping customers?

  1. Disable the help desk inbox during peak hours
  2. Increase the number of ticket pipelines to ten
  3. Require every customer to call instead of writing
  4. Publish a knowledge base article and surface it in the support channel for self-service Correct answer.

Explanation

Deflecting common questions with a findable self-service article reduces repetitive ticket volume while still answering the customer. Adding pipelines, closing the inbox, or forcing phone calls does not resolve the repetitive question efficiently.

Question 14Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

What is the effect of setting a ticket's status to a closed category within its pipeline?

  1. The ticket is removed from all reporting permanently
  2. The ticket counts as resolved and typically leaves the active queue while remaining reportable Correct answer.
  3. The ticket is converted into a contact record
  4. The ticket is permanently locked and can never be reopened

Explanation

Closed statuses indicate resolution, so tickets usually drop out of active queues while still being available for reporting and history. Closed tickets can generally be reopened if the customer returns, and they are not converted or purged from reporting.

Question 15Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

A manager wants tickets for billing issues to follow different stages than tickets for technical issues. What should the manager configure?

  1. Multiple deal pipelines, each with its own forecast
  2. Multiple contact lists, each with its own filters
  3. Multiple email templates, each with its own signature
  4. Multiple ticket pipelines, each with its own stages Correct answer.

Explanation

Ticket pipelines let a team define distinct stage sets for different request types, such as billing versus technical support. Contact lists, email templates, and deal pipelines organize other things and do not define ticket stages.

Question 16Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

An agent receives a conversation in a language they do not speak. Which help desk practice best supports a timely response?

  1. Delete the conversation and ask the customer to resubmit in another language
  2. Assign the ticket to the customer's company record
  3. Close the ticket immediately without replying
  4. Route the conversation to a teammate with the relevant language skill Correct answer.

Explanation

Routing to an agent with the right language skill keeps the response timely and accurate, which is the purpose of skill-based assignment in a shared inbox. Closing, deleting, or misassigning the conversation does not serve the customer.

Question 17Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

Which scenario best illustrates the difference between a conversation and a ticket in Service Hub?

  1. A conversation is the message exchange, while a ticket is the tracked support request created from it Correct answer.
  2. A conversation is a company record, while a ticket is a contact record
  3. A conversation is a sales opportunity, while a ticket is a marketing email
  4. A conversation and a ticket are identical records with no distinction

Explanation

The conversation holds the actual exchange of messages, and the ticket is the structured record used to track, assign, and report on the request. They are related but distinct, and neither is a sales or company object.

Question 18Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

A team wants to ensure that tickets left in a pending state too long are flagged for follow-up. Which approach fits the help desk model?

  1. Rely on agents to remember to check pending tickets manually
  2. Move all pending tickets to the sales pipeline
  3. Delete pending tickets after one day
  4. Create an automation that checks ticket age or status and notifies the owner Correct answer.

Explanation

Automation based on ticket properties such as status and time in stage can flag stale tickets and notify the responsible agent, which is more reliable than memory. Deleting tickets loses work, and sales pipelines do not apply to support tickets.

Question 19Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

An agent wants to see a customer's earlier support tickets while replying to a new one. What feature makes this possible?

  1. The deal forecast report
  2. The marketing email editor
  3. The associated records panel showing the contact's related tickets Correct answer.
  4. The blog comment moderation queue

Explanation

Associations between the ticket, contact, and other tickets let an agent view prior support history in context. Marketing editors, blog moderation, and deal forecasts do not surface a contact's support history.

Question 20Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

A support leader wants to understand which ticket sources generate the most volume. What is the most direct way to answer this?

  1. Report on the ticket source property across tickets in a given period Correct answer.
  2. Count the number of agents logged in today
  3. Check the number of deal stages configured
  4. Review the number of marketing contacts created

Explanation

The ticket source property records where each ticket originated, so grouping tickets by source reveals volume distribution. Agent logins, contact counts, and deal stages do not describe ticket origins.

Question 21Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

A customer emails support, then follows up with a second email about the same issue before an agent replies. What is the desirable help desk behavior?

  1. Delete the second email as a duplicate
  2. Create two unrelated tickets with no shared context
  3. Thread the follow-up into the same conversation so the agent sees the full context Correct answer.
  4. Forward both emails to the marketing team

Explanation

Threading related messages into one conversation preserves context and prevents an agent from answering only part of the issue. Creating unrelated tickets fragments context, deleting the follow-up loses information, and marketing is not the right destination.

Question 22Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

A team notices that tickets are frequently reassigned between agents, slowing resolution. Which help desk configuration most directly addresses the root cause?

  1. Refine routing rules so conversations reach the best-suited agent or team on arrival Correct answer.
  2. Disable ticket reporting to reduce overhead
  3. Require agents to reply only after reassigning twice
  4. Add more ticket pipelines to increase flexibility

Explanation

Frequent reassignment usually signals that initial routing does not match requests to the right skills or teams, so improving routing rules addresses the cause. Adding pipelines, disabling reporting, or mandating reassignment does not fix misrouting.

Question 23Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

A manager wants to distinguish tickets that were reopened after closure from tickets that were never closed. Which data practice supports this analysis?

  1. Rely on agents' memory of which tickets were reopened
  2. Track status changes over time so reopening events are recorded in the ticket history Correct answer.
  3. Delete closed tickets to simplify the dataset
  4. Count only tickets currently in the new status

Explanation

Reopening is a transition between statuses, so it is only measurable if status changes are recorded over time in the ticket's history. Memory is unreliable, deleting tickets removes evidence, and counting only new tickets excludes the events of interest.

Question 24Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

A help desk team wants agents to see suggested knowledge base articles while drafting a reply so answers stay accurate and consistent. Which capability aligns with this goal?

  1. A deal-stage automation that updates forecasts
  2. A separate spreadsheet maintained outside the help desk
  3. A blog subscription confirmation email
  4. Knowledge base content surfaced within the conversation reply experience Correct answer.

Explanation

Surfacing knowledge base articles inside the reply experience lets agents reuse vetted answers without leaving the conversation. External spreadsheets, deal automation, and subscription emails do not deliver approved content at the point of reply.

Question 25Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

A support operation wants to compare resolution speed across two ticket pipelines with different stage structures. Which consideration matters most for a fair comparison?

  1. Comparing only the total number of tickets created
  2. Confirming that the time metrics are defined and measured consistently across both pipelines Correct answer.
  3. Using the number of agents as the sole measure of performance
  4. Assuming the pipelines are identical because both are tickets

Explanation

Different stage structures can distort comparisons unless the time metrics are defined the same way in each pipeline. Assuming equivalence, counting volume only, or using headcount alone does not produce a valid resolution-speed comparison.

Question 26Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

In a Service Hub help desk, which inbox setting determines which incoming conversations an agent or team can see?

  1. Inbox access and assignment settings that scope conversations to specific users or teams Correct answer.
  2. The knowledge base domain connected to the account
  3. The email signature template attached to the agent's profile
  4. The pipeline stage order configured for the associated ticket object

Explanation

Help desk inboxes control visibility through access and assignment configuration, so conversations route to the right users or teams. Pipeline stages describe ticket progression, signatures affect message content, and the knowledge base domain affects article hosting, not inbox visibility.

Question 27Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

A support team wants every new ticket to start in a specific stage and be assigned to a queue. Which Service Hub configuration accomplishes this?

  1. A workflow that sets ticket pipeline, stage, and owner when a ticket is created Correct answer.
  2. A saved reply that includes the queue name in the message body
  3. A form field that asks the customer to choose an agent
  4. A contact property that records the customer's preferred channel

Explanation

Automation workflows can set ticket properties such as pipeline, stage, and owner at creation time, which standardizes intake. Saved replies, contact properties, and form fields do not control ticket routing or stage assignment.

Question 28Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

What does a ticket pipeline represent in Service Hub?

  1. A library of reusable reply templates
  2. A list of contacts who have opted into marketing email
  3. A set of agents grouped by their working hours
  4. A defined sequence of stages that a ticket moves through toward resolution Correct answer.

Explanation

A pipeline defines the ordered stages a ticket passes through, and each pipeline can model a distinct support process. Contact lists, agent groups, and reply templates are separate objects that do not define ticket progression.

Question 29Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

An agent is replying to a customer in the help desk and wants to insert a personalized greeting and company signature automatically. Which feature should the agent use?

  1. A workflow that closes the ticket after sending
  2. A ticket property that stores the customer's name
  3. A saved reply combined with the agent's configured signature Correct answer.
  4. A knowledge base article linked in the reply

Explanation

Saved replies insert reusable message content, and the configured signature appends the agent's standard closing automatically. Ticket properties, closing workflows, and knowledge base links do not personalize the greeting and signature in the composer.

Question 30Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

Which Service Hub object is designed to store the record of a customer's support request and its resolution lifecycle?

  1. The marketing email object
  2. The blog post object
  3. The product library object
  4. The ticket object Correct answer.

Explanation

Tickets are the object that track a support request through stages until resolution. Marketing emails, products, and blog posts serve marketing, sales, and content purposes rather than support lifecycle tracking.

Question 31Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

A support manager wants to route chat conversations to agents who are currently available. Which help desk capability supports this?

  1. A ticket pipeline with a single stage
  2. A contact property for preferred language
  3. A knowledge base category structure
  4. Inbox routing that considers agent availability and assignment rules Correct answer.

Explanation

Help desk routing can consider availability and assignment rules so live conversations reach agents who can respond. Pipeline stages, contact properties, and knowledge base categories do not distribute live chats by availability.

Question 32Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

What is the primary function of the conversations inbox in Service Hub?

  1. To publish knowledge base articles to the public site
  2. To consolidate customer messages from connected channels into a shared workspace for replies Correct answer.
  3. To generate quotes for the sales team
  4. To score leads based on email engagement

Explanation

The conversations inbox brings messages from connected channels together so agents can view and reply from one place. Publishing articles, lead scoring, and quote generation belong to other tools and objects.

Question 33Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

A customer's ticket has been resolved and the team wants the record to remain available for future reference without appearing as active work. Which ticket status category fits?

  1. A closed status category Correct answer.
  2. An open status category
  3. A waiting-on-us status category
  4. A new status category

Explanation

Closed status categories indicate the ticket is no longer active while preserving the record for reporting and history. Open, new, and waiting-on-us categories all represent tickets that still require attention.

Question 34Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

A support lead wants tickets created from live chat to be distinguishable from tickets created by email. Which configuration achieves this most directly?

  1. Capture the original source channel on the ticket and report on that property Correct answer.
  2. Disable email as a channel
  3. Rename the pipeline for chat tickets only
  4. Ask agents to add a note naming the channel

Explanation

Recording the source channel on the ticket creates a reportable attribute that separates chat from email intake. Renaming pipelines, manual notes, and disabling channels are either unreliable or disruptive and do not cleanly segment by source.

Question 35Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

Two agents handle the same shared inbox. A conversation arrives while one agent is out to lunch. What ensures the waiting customer still gets a timely response?

  1. A ticket property that records the lunch schedule
  2. A saved reply that tells the customer to wait
  3. Assignment rules that route unassigned conversations to an available agent or team queue Correct answer.
  4. A workflow that deletes the conversation

Explanation

Routing unassigned conversations to available agents or a monitored queue prevents messages from sitting idle when a specific agent is away. Holding replies, schedule properties, and deletion do not deliver a response.

Question 36Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

A team wants to ensure that a ticket cannot skip from the first stage directly to the final stage without passing through intermediate stages. What should they configure?

  1. Enforce stage progression within the pipeline so tickets move through defined stages in order Correct answer.
  2. Add more saved replies to the pipeline
  3. Remove all closed statuses from the pipeline
  4. Increase the number of agents on the team

Explanation

Pipeline stage definitions and progression rules control how tickets advance, keeping work in the intended order. Saved replies, staffing, and status removal do not govern stage order.

Question 37Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

A manager wants automatic reminders when a ticket has been in the same stage beyond a service target. Which approach fits Service Hub?

  1. A workflow triggered by time in stage that notifies the owner or escalates the ticket Correct answer.
  2. A saved reply that mentions the target
  3. A contact list that includes all customers
  4. A knowledge base article about response times

Explanation

Time-based workflow triggers can detect tickets stalled in a stage and notify owners or escalate them. Contact lists, saved replies, and articles do not monitor elapsed time or trigger reminders.

Question 38Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

An agent wants to view a customer's full interaction history, including prior conversations and tickets, while replying. Which Service Hub capability provides this context?

  1. The pipeline settings page
  2. The contact record with associated conversations and tickets shown alongside the inbox Correct answer.
  3. The knowledge base editor
  4. The saved reply library

Explanation

The contact record surfaces associated conversations and tickets so agents can see prior interactions in context. Pipeline settings, saved replies, and the article editor do not present a customer's history.

Question 39Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

A support team wants to measure agent performance on first response and resolution across a period. Which Service Hub reporting approach is most appropriate?

  1. A marketing email performance report
  2. A sales pipeline forecast report
  3. A help desk report built on conversation and ticket data with time-based metrics Correct answer.
  4. A website traffic analytics report

Explanation

Help desk reports draw on conversation and ticket data and can include time-based metrics such as first response and resolution. Marketing, sales forecast, and traffic reports measure different objects and cannot answer support performance questions.

Question 40Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

An agent is drafting a reply and wants to reference an internal note that customers should not see. Which help desk feature should the agent use?

  1. A saved reply inserted into the customer message
  2. A ticket property updated on the record
  3. A private note on the conversation visible only to the team Correct answer.
  4. A public reply sent to the customer

Explanation

Private notes let agents record internal context on a conversation without exposing it to the customer. Saved replies and public replies are customer-facing, and a property update does not communicate context to teammates in the thread.

Question 41Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

A support operation wants to compare average time to close between two teams handling different products. Which configuration supports a fair comparison?

  1. A single pipeline with no stage definitions
  2. Different status labels for each team with no shared categories
  3. Manual spreadsheets maintained by each team
  4. Separate pipelines per product with consistent status categories and shared time metrics Correct answer.

Explanation

Separate pipelines can model each product while consistent status categories and shared metrics keep the comparison meaningful. Undefined stages, divergent labels, and manual spreadsheets undermine comparability.

Question 42Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

A customer replies to a closed ticket with a new question. What is the most appropriate handling in Service Hub?

  1. Change the original ticket's source property
  2. Ignore the reply because the original ticket is closed
  3. Reopen or create a new ticket so the new question is tracked through the lifecycle Correct answer.
  4. Delete the original ticket and start over

Explanation

A new question after closure should be tracked by reopening or creating a ticket so it moves through the lifecycle and is reported accurately. Ignoring, deleting, or editing source data loses tracking and misrepresents the work.

Question 43Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

A team wants to reduce duplicate tickets when a customer sends several messages about one issue in a short window. Which practice best addresses this?

  1. Disable email intake to prevent duplicates
  2. Thread related messages into one conversation and create a single associated ticket Correct answer.
  3. Ask agents to merge tickets manually at month end
  4. Create a separate ticket for every inbound message

Explanation

Threading related messages and associating one ticket keeps a single issue tracked once. Per-message tickets multiply records, disabling email removes a channel, and month-end merging is reactive and error-prone.

Question 44Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

An agent needs to see which team owns a conversation before replying. Which inbox element conveys ownership?

  1. The knowledge base article category
  2. The ticket's product association
  3. The assigned user or team shown on the conversation Correct answer.
  4. The customer's marketing subscription status

Explanation

The conversation's assigned user or team indicates ownership and who is expected to respond. Subscription status, article category, and product association do not communicate conversation ownership.

Question 45Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

A support leader wants to know whether adding a self-service knowledge base reduced ticket volume for common questions. Which analysis is most appropriate?

  1. Review the number of saved replies created
  2. Compare ticket volume for the affected question types before and after the knowledge base launch Correct answer.
  3. Count the number of articles published
  4. Measure agent login frequency

Explanation

Comparing ticket volume for the targeted question types before and after launch isolates the knowledge base effect. Article counts, login frequency, and saved reply counts are activity measures that do not demonstrate deflection.

Question 46Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

A manager wants to ensure tickets reopened after closure are counted separately from tickets closed once. Which data practice supports this?

  1. Rely on the ticket's creation date only
  2. Track reopen events or a reopen count property on the ticket and report on it Correct answer.
  3. Count all closed tickets as reopened
  4. Use the customer's contact owner as the indicator

Explanation

Recording reopen events or a reopen count makes the distinction measurable in reporting. Creation date, contact owner, and blanket assumptions cannot identify which tickets were reopened.

Question 47Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

A team wants agents to see relevant knowledge base articles suggested while composing a reply. Which configuration enables this most directly?

  1. Connect the knowledge base to the help desk so article suggestions appear in the conversation composer Correct answer.
  2. Store articles as ticket attachments
  3. Email articles to agents daily
  4. Add article titles to every saved reply

Explanation

Linking the knowledge base to the help desk surfaces relevant articles to agents as they draft replies. Embedding titles, emailing articles, and attaching them manually do not provide contextual suggestions.

Question 48Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

A support operation wants to compare resolution speed across two pipelines whose stage structures differ in number of stages. Which approach yields the most valid comparison?

  1. Compare the number of agents assigned to each pipeline
  2. Compare the number of stages in each pipeline
  3. Compare the pipelines' names
  4. Compare elapsed time from creation to closed status rather than stage counts Correct answer.

Explanation

Elapsed time to closure is comparable even when stage counts differ, because it measures the outcome rather than the process shape. Stage counts, staffing, and names do not represent resolution speed.

Question 49Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

A help desk receives a spike in conversations outside business hours. Which configuration best maintains coverage without overstaffing?

  1. A ticket property recording the time of day
  2. An automated acknowledgment plus routing to an on-call queue or next-day follow-up Correct answer.
  3. A saved reply that apologizes for the delay
  4. A workflow that closes all after-hours conversations

Explanation

Automated acknowledgment sets expectations while routing to on-call staff or scheduled follow-up maintains coverage efficiently. Closing conversations, apologizing without routing, and logging time alone do not ensure a response.

Question 50Service Hub Software (help desk, ticketing, and shared inbox fundamentals)

An agent is assigned a ticket but will be out of office for two days. The support manager wants the ticket to stay owned by a person while making clear that another agent should pick it up. Which Service Hub ticket property best supports this?

  1. Keep the original agent as ticket owner and set a ticket status that signals the ticket is waiting on the team Correct answer.
  2. Leave the ticket unassigned and rely on the shared inbox notification to surface it
  3. Change the ticket owner to a shared team queue and remove any individual assignment
  4. Reassign the ticket owner to the backup agent and add the original agent as a follower

Explanation

Ticket ownership in Service Hub is a single assigned owner, and ticket status communicates where the ticket stands in the support process. Keeping the original owner while using a waiting-type status preserves accountability and signals that the ticket needs attention from someone else. Followers can stay informed without changing ownership.