
Knowledge Base vs Help Desk: Key Differences and When to Use Each
A knowledge base publishes reusable answers, while a help desk receives and manages individual support requests. Use a knowledge base when people can solve a repeatable problem by following approved information. Use a help desk when a request needs an owner, private context, investigation, action, status tracking, or escalation.
The two systems are not direct substitutes. A knowledge base is primarily a content and knowledge-governance system. A help desk is primarily a request-management workflow, support function, or software platform. Many organizations use both because common questions and individual cases are different types of work.
Quick decision: Choose a knowledge base for answers that can be published once and reused. Choose a help desk for requests that must be received, assigned, investigated, and resolved. Use both when self-service needs a reliable path to human support.
Contents
- Knowledge Base vs Help Desk at a glance
- What a knowledge base is
- What a help desk is
- The key operational differences
- Help center, ticketing system, and service desk terminology
- When a knowledge base may be enough
- When a help desk may be enough
- When you need both systems
- How a knowledge base and help desk work together
- Which system should you implement first?
- Built-in vs standalone knowledge bases
- Software evaluation checklist
- How AI changes the comparison
- What to measure
- Common mistakes
- Final decision checklist
- Frequently asked questions
Knowledge Base vs Help Desk at a Glance
| Comparison point | Knowledge base | Help desk |
|---|---|---|
| Primary purpose | Publish, organize, govern, and maintain reusable knowledge | Receive, track, assign, and resolve individual requests |
| Primary unit of work | Article, guide, procedure, FAQ, policy, or document | Ticket, request, case, incident, or conversation |
| Best suited to | Repeatable questions and documented processes | Account-specific, private, unusual, or action-dependent issues |
| Typical interaction | A reader searches or browses approved content | A requester communicates with an agent or automated workflow |
| Typical workflow | Draft, review, approve, publish, measure, update, retire | Receive, classify, prioritize, assign, investigate, respond, resolve, close |
| Ownership | Article owner, knowledge manager, or subject-matter expert | Assigned agent, queue, team, or resolver group |
| Information type | Reusable and approved information | Case-specific information, communication, evidence, and actions |
| Privacy | May be public, authenticated, internal, or restricted | Usually contains private requester and case information |
| Status and priority | Content may have draft, review, published, and archived states | Requests usually have status, priority, assignment, and escalation fields |
| Service-level tracking | Not normally the core function | Often used to track response or resolution commitments |
| Core analytics | Search behavior, content use, feedback, freshness, and knowledge gaps | Volume, backlog, response time, resolution time, escalations, and workload |
| Can it work alone? | Yes, when reusable information is the primary need and another escalation route exists | Yes, especially when requests are unique or the team is still discovering repeated issues |
| Can software include both? | Yes. Many support suites include knowledge features | Yes. Many help-desk platforms include a knowledge base or help center |
The simplest distinction is that a knowledge base manages answers, while a help desk manages requests. The line can look less obvious when one product bundles both capabilities, but the underlying workflows remain different.
What Is a Knowledge Base?
A knowledge base is a governed collection of reusable information. It may contain how-to articles, troubleshooting procedures, policies, product documentation, standard operating procedures, FAQs, technical references, or employee guidance.
A knowledge base can serve several audiences:
- Customers: public or login-restricted self-service articles.
- Employees: internal processes, workplace guidance, and operational references.
- Support agents: troubleshooting steps, decision guidance, approved answers, and escalation instructions.
- Developers or partners: technical documentation, integration guidance, and API references.
- AI systems: approved source material for search, article suggestions, agent assistance, or grounded answers.
The knowledge base is not merely a folder of documents. A reliable implementation also needs ownership, review, approval, permissions, findability, version control, feedback, and a process for retiring obsolete content.
The knowledge base unit of work
The unit of work is normally an article or another reusable knowledge object. Its lifecycle may look like this:
- A recurring question or documentation need is identified.
- An author drafts the answer.
- A subject-matter expert verifies it.
- An authorized person approves publication when required.
- The content is published to the appropriate audience.
- Search, use, and feedback are monitored.
- The article is updated, restricted, replaced, or archived when conditions change.
This lifecycle is different from resolving one requester’s issue. The objective is to create a dependable answer that can be reused safely across many relevant situations.
What Is a Help Desk?
A help desk can refer to a support function, a team, a workflow, or the software used to manage that work. Its central purpose is to receive individual requests and move them toward resolution with clear ownership and a recorded history.
A help desk may serve customers, employees, partners, vendors, or other requesters. Depending on the environment, requests may arrive through email, web forms, chat, messaging, phone, monitoring systems, or connected applications.
The help desk unit of work
The unit of work is usually a ticket, case, request, incident, or conversation. Its lifecycle may include:
- The request enters the system.
- It is categorized and assigned a status or priority.
- An agent, team, or automation becomes responsible for it.
- The issue is investigated and additional information may be collected.
- The request is answered, fulfilled, escalated, or transferred.
- The requester is informed of the outcome.
- The request is resolved and closed, with the option to reopen or create a follow-up when appropriate.

The help desk preserves context that does not belong in a public article, including account details, conversation history, attachments, approvals, troubleshooting evidence, and actions performed for a specific requester.
The Key Operational Differences
1. Reusable knowledge vs individual case management
A knowledge base is designed for answers that remain useful beyond one interaction. A help desk manages a particular request with its own requester, circumstances, ownership, and outcome.
For example, an article can explain how to download an invoice. A help-desk ticket is appropriate when a customer sees the wrong invoice, cannot access the account, or needs a billing record corrected.
2. Published information vs private context
Knowledge-base content should be written for an identified audience and stripped of unnecessary personal or case-specific information. Help-desk records often contain private data that is necessary to investigate the request.
Internal knowledge can also be restricted, but it should still contain reusable guidance rather than an unfiltered collection of private ticket histories.
3. Findability vs intake
A knowledge base succeeds when people can find and understand the right information. Its design depends on clear titles, search, navigation, metadata, synonyms, related content, and well-structured articles.
A help desk succeeds when requests reach the correct workflow. Its design depends on channels, forms, required fields, categories, routing, queues, assignment rules, priorities, and escalation paths.
4. Content ownership vs ticket ownership
An article owner is accountable for the continuing accuracy and usefulness of a piece of knowledge. A ticket owner is accountable for progressing a specific request toward resolution.
These responsibilities can belong to the same employee, but they should not be confused. Closing a ticket does not automatically update the relevant documentation, and publishing an article does not resolve an open customer case.
5. Content states vs request states
A knowledge article may move through draft, review, approval, published, restricted, and archived states. A ticket may move through new, open, pending, on hold, escalated, resolved, or closed states.
The exact labels differ by platform, but the distinction matters: one lifecycle governs information quality, while the other governs request progress.
6. Content analytics vs support operations analytics
Knowledge-base analysis focuses on whether people can locate, understand, and use content. Help-desk analysis focuses on request demand, workload, speed, routing, resolution, and service performance.
Neither measurement set proves success by itself. An article view does not prove that a task was completed, and a closed ticket does not always prove that the requester received a durable solution.
7. Governance vs queue management
A knowledge-base program needs content standards, subject-matter review, publishing controls, ownership, freshness rules, and retirement procedures. A help-desk operation needs queue design, staffing, assignment rules, escalation, quality assurance, and workload management.
An integrated product may support both, but the organization still needs separate operating practices for knowledge and requests.
8. Self-service vs assisted resolution is useful—but incomplete
It is common to describe a knowledge base as self-service and a help desk as assisted support. That is helpful, but not absolute.
- Agents may use an internal knowledge base while resolving tickets.
- A public knowledge base may include comments, feedback, or interactive AI answers.
- A help desk may automate intake, routing, answers, or simple fulfillment.
- A knowledge article may be used after a problem occurs, so it is not always proactive in a literal sense.
- A customer may read an article and still need a person to complete an account-specific action.
The stronger distinction is reusable knowledge versus managed requests.
Knowledge Base, Help Center, Help Desk, Ticketing System, and Service Desk
These terms are often bundled inside one product, which can make them appear interchangeable. They describe different functions.
| Term | Practical meaning |
|---|---|
| Knowledge base | The governed collection of reusable support or reference content |
| Help center | The user-facing destination that may contain a knowledge base, community, request forms, and a ticket portal |
| Help desk | The support function, team, workflow, or platform that manages individual requests |
| Ticketing system | The component that records and tracks requests as tickets, cases, or conversations |
| Service desk | In IT service management, a broader service-focused function that may handle incidents, service requests, access, information, approvals, and related practices |
| Internal wiki | A collaborative space for broad organizational knowledge that may be less structured around support workflows and controlled answers |
| Self-service portal | An interface where users may search knowledge, submit requests, access services, view account information, or track ticket status |
Official Zendesk help-center documentation, for example, describes a help center as a customer-facing site that can combine a knowledge base, community, customer request submission, and ticket management. That is one product implementation, but it illustrates why “help center” should not automatically be used as a synonym for “help desk.”

In IT environments, the help desk and service desk distinction may also matter. Atlassian’s current ITSM explanation describes the help desk as more focused on resolving user-reported issues, while the service desk covers a broader service-management relationship.
When a Knowledge Base May Be Enough
A knowledge base may be the first or only dedicated system you need when reusable information is the main requirement and individual case management is handled elsewhere.
It is a strong starting point when:
- Most questions are repeated across many users.
- The answers are reasonably stable and can be approved in advance.
- Readers can complete the task without a private account change.
- The organization primarily needs product documentation, policies, procedures, onboarding, or reference material.
- A separate contact or escalation route already exists.
- There is no formal promise to investigate each reader’s individual situation through the knowledge platform.
- The team can assign owners and maintain the articles after publication.
Examples
- A software company publishes setup and configuration documentation.
- An organization creates an employee handbook and internal procedures.
- A developer platform publishes API guides and error references.
- A small product team documents common questions while handling rare cases through an existing email address.
A knowledge base still needs an escalation path. Self-service may fail because the answer is missing, outdated, difficult to find, unclear, inapplicable to the user’s situation, or dependent on an action the reader cannot perform.
When a Help Desk May Be Enough
A help desk may deserve priority when the immediate problem is unmanaged requests rather than missing published information.
Start with a help desk when:
- Requests are being lost in individual inboxes, spreadsheets, or chat messages.
- Every request needs a clear owner and status.
- The team needs categories, priorities, queues, routing, and escalations.
- Requests contain private, account-specific, or sensitive information.
- Cases require investigation, approval, fulfillment, or changes in another system.
- Response or resolution commitments must be monitored.
- Leaders need visibility into volume, backlog, workload, or unresolved cases.
- The support operation is new and has not yet identified which answers are stable and repeatable.
A small team can begin by documenting reliable answers in ticket macros or internal notes, but those items should not be mistaken for a governed knowledge base. Macros may contain temporary language, and tickets may include personal data, context-specific decisions, inconsistent answers, or obsolete instructions.
When You Need Both a Knowledge Base and Help Desk
Use both when the organization must provide reusable answers and a managed path for exceptions, failures, private cases, or actions that require a person or authorized automation.
| Situation | Knowledge-base role | Help-desk role |
|---|---|---|
| Password problem | Explain the standard reset procedure | Handle an account that remains locked or requires identity review |
| Billing question | Explain how to find invoices and understand standard billing terms | Investigate a duplicate charge or account-specific billing error |
| Product setup | Publish the supported installation steps | Investigate an environment-specific error |
| Return or cancellation | Explain the general policy and process | Review an exception, missing refund, or disputed outcome |
| Internal IT support | Document standard VPN configuration | Provision access or investigate a connection failure |
The knowledge base handles the known and repeatable part of the experience. The help desk handles the individual context and ensures that unresolved work has an owner.
How a Knowledge Base and Help Desk Work Together
The strongest model is a closed loop: knowledge supports ticket resolution, while ticket demand reveals which knowledge should be created or improved.

- A user searches or browses the knowledge base.
- The content resolves the issue, or the user requests assistance.
- When a ticket is created, useful self-service context is passed to the help desk.
- An agent reviews the request and searches approved knowledge.
- The agent links, quotes, or applies the relevant article while investigating the specific case.
- The request is resolved or escalated.
- Repeated questions, unsuccessful searches, and undocumented resolutions become knowledge candidates.
- Private and case-specific information is removed.
- A reusable answer is validated, reviewed, and published.
- Search, article feedback, and ticket patterns show whether the new content is helping.
Pass useful context when self-service becomes a ticket
A well-designed handoff can reduce repetition for the requester and improve routing. Appropriate context may include:
- The search query.
- The article viewed.
- The steps already attempted.
- The product, service, or feature involved.
- The error shown.
- The user’s language.
- The point at which the documented process failed.
Do not collect or transfer unnecessary personal, confidential, or security-sensitive information merely because the systems can be connected.
Turn ticket demand into governed knowledge
Support data can reveal missing articles, unclear wording, new terminology, and recurring problems. Current Zendesk documentation shows one implementation in which agents search and link knowledge from tickets, while support data and agent contributions help develop the knowledge base.
Atlassian similarly documents workflows that can suggest articles while a requester completes a form and let teams use request patterns to identify knowledge gaps. These are product-specific examples of a broader principle: assisted-support demand should inform the reusable knowledge program.

Do not copy a ticket directly into a public article. Before publication:
- Remove personal, confidential, and account-specific information.
- Separate the reusable answer from the individual decision.
- Confirm that the resolution is approved and broadly applicable.
- Identify the intended audience and access level.
- Assign an owner.
- Apply the normal review and approval process.
- Check for security, policy, legal, or privacy implications.
Knowledge-Centered Success and support workflows
Knowledge-Centered Success (KCS®), formerly known as Knowledge-Centered Service, is a methodology maintained by the Consortium for Service Innovation. Its central idea is to reuse, improve, and create knowledge as part of the workflow rather than treating documentation as a completely separate activity.

KCS® is a service mark of the Consortium for Service Innovation™.
Which System Should You Implement First?
Implement the system that solves the most urgent operational failure. Do not choose based only on which category appears simpler or less expensive.
| Your main problem | Start with | Reason |
|---|---|---|
| The same stable questions are answered repeatedly | Knowledge base | One reviewed answer can serve many readers |
| Requests are lost or have no clear owner | Help desk | Ticketing creates accountability and visibility |
| Cases require private investigation or account changes | Help desk | A managed request preserves context and action history |
| The primary need is product or developer documentation | Knowledge base | Publishing, search, structure, and content maintenance are the core needs |
| Users need self-service plus a tracked escalation path | Both | The systems handle different stages of the same support journey |
| The team does not yet know which issues are repeatable | Help desk, then knowledge base | Ticket data can reveal stable documentation candidates |
| There is already a large article library but support remains fragmented | Help desk | The immediate gap is request coordination, not content volume |
| There is a mature ticket operation but agents give inconsistent answers | Knowledge base | The gap is governed, reusable knowledge |
A practical implementation sequence
- List the support tasks the organization must handle.
- Separate repeatable information needs from individual actions and investigations.
- Identify where requests or answers currently fail.
- Select the first system based on the highest-impact gap.
- Define ownership, permissions, and success measures before launch.
- Add the second capability when the limitations of the first become clear.
- Connect the workflows and create an ongoing improvement loop.
Built-In vs Standalone Knowledge Base
Help-desk software often includes a knowledge-base component. A separate documentation or knowledge platform may also integrate with the help desk. Neither approach is automatically better.
A built-in knowledge base may fit when
- The organization wants simpler administration and fewer integrations.
- Agents need to search and link articles without leaving the ticket workspace.
- The content serves a limited number of audiences or sites.
- The publishing and approval requirements are straightforward.
- Shared identity, permissions, and reporting are important.
- The bundled capabilities meet the tested requirements.
A standalone platform may fit when
- Documentation is a major product experience rather than a secondary support feature.
- The organization manages several audiences, brands, products, portals, or documentation sets.
- Publishing, review, localization, design, or developer-documentation requirements are advanced.
- Content must integrate with several support or business systems.
- Portability, structured content, export, or migration controls are priorities.
- The built-in knowledge feature fails important workflow tests.
Evaluate the actual edition and configuration available to your organization. Features, limits, integrations, and AI capabilities can vary by vendor, product, and plan.
Knowledge Base and Help Desk Software Evaluation Checklist
Knowledge-base capabilities
- Article editor and reusable templates
- Draft, review, approval, publication, and archive workflows
- Article ownership and review reminders
- Version history and rollback
- Public, authenticated, internal, and restricted content
- Audience and author permissions
- Search quality, synonyms, tags, and metadata
- Related articles and content relationships
- Localization and translation workflow
- Search analytics and zero-result reporting
- Article feedback and content-gap reporting
- SEO and custom-domain controls for public content
- APIs, export, and migration options
- AI answers grounded in approved sources
- Source visibility and permission-aware retrieval
Help-desk capabilities
- Required support channels
- Ticket, request, or case management
- Queues, ownership, assignment, and transfers
- Statuses, priorities, categories, and custom fields
- Routing and workflow automation
- Escalations and approvals
- Response and resolution targets
- Internal collaboration and private notes
- Requester identity and customer history
- Customer or employee portal
- Reporting on volume, backlog, workload, and resolution
- CRM, IT, product, messaging, and business-system integrations
- Audit, privacy, security, and retention controls
- AI classification, summarization, suggestions, or workflow execution where appropriate
Combined-workflow capabilities
- Suggesting articles before a request is submitted
- Passing self-service context into a ticket
- Searching knowledge inside the agent workspace
- Linking or quoting approved articles in replies
- Creating or requesting articles from recurring tickets
- Preserving permissions during agent and AI search
- Connecting ticket topics to knowledge gaps
- Sending article feedback to the correct owner
- Reporting on knowledge use during assisted support
- Exporting both content and support history
Test these workflows with representative content and requests. A feature listed on a product page may not satisfy the organization’s actual permission, localization, publishing, or integration needs.
How AI Changes the Knowledge Base vs Help Desk Comparison
AI can connect the two systems more closely, but it does not remove their functional differences.
| AI use | Knowledge-base role | Help-desk role |
|---|---|---|
| Generated answer | Provides approved source information | Receives the request when no reliable answer is available |
| Agent assistance | Supplies procedures, policies, and troubleshooting guidance | Provides ticket context, conversation history, status, and workflow |
| Virtual agent | Supports grounded answers to repeatable questions | Creates, routes, or escalates a request when automation cannot complete the task |
| Knowledge-gap discovery | Stores the new or improved approved content | Provides recurring request patterns that reveal missing knowledge |
| Ticket automation | May supply classification guidance or standard answers | Performs routing, summarization, prioritization, or authorized workflow actions |
The knowledge base should remain the governed source for reusable information. The help desk should remain the system that records and manages individual requests. An AI system may use both, but it should not create new policy or expose restricted knowledge simply because the information is technically searchable.
Important safeguards include:
- Ground answers in approved, current sources.
- Preserve source visibility where appropriate.
- Apply audience and content permissions before retrieval.
- Define what the system should do when evidence is missing.
- Escalate sensitive or ambiguous cases.
- Test both correct-answer and no-answer scenarios.
- Remove obsolete and contradictory sources.
- Protect personal and account-specific information.
- Require human review for consequential decisions.
Do not describe an AI support system as hallucination-free. A cited answer can still misinterpret a source, omit an exception, or apply the wrong content to the request.
What to Measure in Each System
Knowledge-base measures
- Search success and search refinement
- Zero-result searches
- Task-completion signals
- Contact after an article or search session
- Article helpfulness and qualitative feedback
- Content freshness and ownership coverage
- Broken links and failed journeys
- Knowledge gaps reported by readers or agents
- Agent reuse of approved articles
- Performance by audience, product, language, or topic
Help-desk measures
- Request volume
- First response time
- Resolution time
- Backlog and queue age
- Response or resolution target attainment
- Transfer and escalation rates
- Reopened requests
- Repeat contact
- First-contact resolution
- Requester satisfaction
- Agent workload and quality-assurance results
Combined measures
- Self-service sessions that become tickets
- Context preserved during escalation
- Tickets linked to knowledge articles
- Recurring ticket topics converted into approved content
- Time agents spend searching for information
- Repeat contact after an article is used
- Incorrect or outdated knowledge reports
- Differences between known and previously undocumented issues
Be careful with “ticket deflection.” The absence of a ticket does not prove that the reader solved the problem. Some people abandon the process, use another channel, or continue without a satisfactory answer.
The Consortium for Service Innovation’s self-service measurement guidance recommends combining behavioral data, feedback, and observation rather than treating one activity metric as conclusive proof of success.
Common Knowledge Base and Help Desk Mistakes
- Buying a knowledge base when the real problem is lost requests: Better articles will not create ticket ownership or queue visibility.
- Buying a help desk when the real problem is inconsistent answers: Ticketing can organize requests while agents continue giving conflicting guidance.
- Treating ticket history as a knowledge base: Tickets contain private details, duplicated explanations, temporary workarounds, and context-specific decisions.
- Publishing articles without owners: Content becomes unreliable when nobody is accountable for reviewing changes.
- Assuming the knowledge base will eliminate support: Some situations require judgment, investigation, access, or action.
- Making escalation difficult: A user who cannot complete self-service should have a clear and appropriate next step.
- Using “help center,” “help desk,” and “knowledge base” as identical terms: This creates unclear requirements and poor software evaluations.
- Measuring page views as successful resolution: A heavily viewed article may be popular, confusing, or associated with a widespread problem.
- Measuring closed tickets without checking outcomes: Closure may reflect workflow completion rather than requester success.
- Connecting AI to ungoverned content: Automation can distribute outdated or contradictory information faster.
- Ignoring access controls: Public users, employees, agents, and specialized teams may require different content visibility.
- Selecting a suite without testing both workflows: Strong ticketing does not guarantee strong knowledge management, and the reverse is also true.
Final Decision Checklist
Choose a knowledge base first when most of these statements are true:
- The main problem is repeated questions or missing documentation.
- The answers can be approved and reused safely.
- Readers can complete the standard task without private intervention.
- Search, navigation, publishing, and content maintenance are the core requirements.
- A separate support or escalation route already exists.
Choose a help desk first when most of these statements are true:
- The main problem is untracked or poorly coordinated requests.
- Every case needs ownership, status, and history.
- Requests include private or account-specific information.
- Agents must investigate, approve, change, or fulfill something.
- Routing, queues, escalation, and workload reporting are essential.
Choose both when most of these statements are true:
- Users need immediate answers for common questions.
- Exceptions and failures need a tracked human or automated workflow.
- Agents need approved knowledge while resolving cases.
- The organization wants a structured handoff from self-service to assistance.
- Ticket demand should drive knowledge creation and improvement.
The final decision should be based on the work that must be managed, not the product category name. A single suite may provide both capabilities, or the organization may connect separate platforms. In either case, keep the content lifecycle and request lifecycle clearly defined.
Frequently Asked Questions
What is the main difference between a knowledge base and a help desk?
A knowledge base manages reusable answers and documentation. A help desk manages individual support requests that require ownership, context, communication, tracking, or action.
Can a knowledge base replace a help desk?
Not when the organization must investigate private cases, perform account-specific actions, track request status, or manage escalations. A knowledge base can handle many repeatable questions, but unresolved or exceptional situations still need an appropriate assistance channel.
Can a help desk work without a knowledge base?
Yes, especially when request volume is low, cases are mostly unique, or the team is still identifying stable answers. Over time, repeated tickets and inconsistent responses often create a strong reason to build a governed knowledge base.
Is a help desk the same as a ticketing system?
Ticketing is usually a core help-desk function, but a help desk may also include multiple intake channels, automation, routing, collaboration, reporting, customer portals, service targets, and knowledge integration. A basic ticketing system may provide a narrower set of capabilities.
Is a knowledge base the same as a help center?
Not necessarily. A knowledge base is the organized content. A help center is the user-facing destination and may include that knowledge base along with a community, request forms, ticket tracking, or other self-service features.
Is a help desk the same as a service desk?
Not always. In IT service-management contexts, a help desk is often associated with resolving user-reported issues, while a service desk may provide a broader point of contact for incidents, service requests, access, information, approvals, and additional ITSM practices.
Which should a small business implement first?
Start with the system that addresses the most costly current failure. Use a knowledge base when repeated questions consume the team’s time. Use a help desk when requests are being lost, lack ownership, or require private investigation. Add the other capability as the support operation matures.
Can a knowledge base reduce support tickets?
It can reduce the need for assisted support when people find accurate information and complete the task successfully. Fewer tickets alone do not prove that result, so combine behavioral data, user feedback, and support trends before claiming successful deflection.
Should the knowledge base be built into the help desk?
A built-in knowledge base may simplify administration, agent workflows, identity, and reporting. A standalone platform may be more suitable for complex publishing, multiple audiences, advanced documentation, localization, or portability. Test the actual workflows and current product capabilities before choosing.
Sources Checked
- Zendesk: Using Support and Knowledge together
- Zendesk: Getting started with the help center
- Atlassian: Writing and sharing knowledge-base articles
- Atlassian: Article suggestions in request forms
- Atlassian: Help desk, service desk, and ITSM distinctions
- ServiceNow: What is a help desk?
- Consortium for Service Innovation: Knowledge-Centered Success Practices Guide
- Consortium for Service Innovation: Measuring Self-Service Success
Sources and product information checked on November 10, 2026.



