Networked Help Desk

Last updated
Networked Help Desk
Networked Help Desk Logo.jpg
Networked Help Desk logo
AbbreviationNHD
First publishedJune 2011
Latest version1.0 [1]
Organization Zendesk
Base standards HTTP, JSON, REST [1]
Related standards JSR 91: OSS Trouble Ticket API [2]
DomainIssue tracking, Bug tracking, Customer relationship management, Project management. [1]
Website networkedhelpdesk.org

Networked Help Desk is an open standard initiative to provide a common API for sharing customer support tickets between separate instances of issue tracking, bug tracking, customer relationship management (CRM) and project management systems to improve customer service and reduce vendor lock-in. [3] [4] The initiative was created by Zendesk in June 2011 in collaboration with eight other founding member organizations including Atlassian, New Relic, OTRS, Pivotal Tracker, ServiceNow and SugarCRM. [5] [6] The first integration, between Zendesk and Atlassian's issue tracking product, Jira, [5] was announced at the 2011 Atlassian Summit. [7] By August 2011, 34 member companies had joined the initiative. [8] A year after launching, over 50 organizations had joined. [9] Within Zendesk instances this feature is branded as ticket sharing. [10] [11] [12]

Contents

Basis

Support tools are generally built around a common paradigm that begins with a customer making a request or an incident report, these create a ticket. Each ticket has a progress status and is updated with annotations and attachments. These annotations and attachments may be visible to the customer (public), or only visible to analysts (private). Customers are notified of progress made on their ticket until it is complete. If the people necessary to complete a ticket are using separate support tools, additional overhead is introduced in maintaining the relevant information in the ticket in each tool while notifying the customer of progress made by each group in completing their ticket. For example, if a customer support issue is caused by a software bug and reported to a help desk using one system, and then the fix is documented by the developers in another, and analyzed in a customer relationship management tool, keeping the records in each system up-to-date and notifying the customer manually using a swivel chair approach is unnecessarily time-consuming and error-prone. If information is not transferred correctly, a customer may have to re-explain their problem each time their ticket is transferred. [13] [14]

For systems with the Networked Help Desk API implemented, it is possible for several different applications related to a customer's support experience to synchronize data in one uniquely identified shared ticket. [15] While many applications in these domains have implemented APIs that allow data to be imported, exported and modified, Network Help Desk provide a common standard for customer support information to automatically synchronize between several systems. [13] Once implemented, two systems can quickly share tickets with just a configuration change as they both understand the same interface. [16]

Communication between two instances on a specific ticket occurs in three steps, an invitation agreement, sharing of ticket data and continued synchronization of tickets. [16] The standard allows for "full delegation" (analysts in both systems each make public and private comments and synchronize status) as well as "partial delegation" where the instance receiving the ticket can only make private comments and status changes are not synchronized. [10] [17] Tickets may be shared with multiple instances. [11]

Implementation list

SystemImplementorsLanguageStatusLaunch dateRefs
Request Tracker Ruslan Zakirov of Best Practical Perl Complete2011-08-10 [18]
YouTrack Java Complete2013-01-31 [19]
Zendesk Darren Boyd, Pierre Schambacher and Josh Lubaway Ruby Complete2011-06-01 [20] [21]
HostBill PHP Complete2012-05-05 [22] [23] [24] [25]
Jira (from Atlassian)JavaComplete2011-06-01 [26]
Node.js JavaScript Incomplete [27]

See also

Related Research Articles

Programming languages can be grouped by the number and types of paradigms supported.

<span class="mw-page-title-main">Request Tracker</span> Open source ticket-tracking software

Request Tracker, commonly abbreviated to RT, is an open source tool for organizations of all sizes to track and manage workflows, customer requests, and internal project tasks of all sorts. With seamless email integration, custom ticket lifecycles, configurable automation, and detailed permissions and roles, Request Tracker began as ticket-tracking software written in Perl used to coordinate tasks and manage requests among an online community of users.

Notable issue tracking systems, including bug tracking systems, help desk and service desk issue tracking systems, as well as asset management systems, include the following. The comparison includes client-server application, distributed and hosted systems.

Google Developers is Google's site for software development tools and platforms, application programming interfaces (APIs), and technical resources. The site contains documentation on using Google developer tools and APIs—including discussion groups and blogs for developers using Google's developer products.

diagrams.net Free and open-source diagram editor

diagrams.net is a cross-platform graph drawing software developed in HTML5 and JavaScript. Its interface can be used to create diagrams such as flowcharts, wireframes, UML diagrams, organizational charts, and network diagrams.

Confluence is a web-based corporate wiki developed by Australian software company Atlassian. Atlassian wrote Confluence in the Java programming language and first published it in 2004. Confluence Standalone comes with a built-in Tomcat web server and hsql database, and also supports other databases.

Jira is a proprietary product developed by Atlassian that allows bug tracking, issue tracking and agile project management. Jira is used by a large number of clients and users globally for project, time, requirements, task, bug, change, code, test, release, sprint management.

In FOSS development communities, a forge is a web-based collaborative software platform for both developing and sharing computer applications.

Bitbucket is a Git-based source code repository hosting service owned by Atlassian. Bitbucket offers both commercial plans and free accounts with an unlimited number of private repositories.

Assembla is a web-based version control and project management software as a service provider for enterprises. It was founded in 2005 and acquired by Idera, Inc. in 2018. It offers Git, Perforce Helix Core and Apache Subversion repository management, integrations with other collaboration tools such as Trello, Slack, GitHub and JIRA. Assembla also offers integrations with customer's managed private clouds.

<span class="mw-page-title-main">Atlassian</span> Australian enterprise software company

Atlassian Corporation is an Australian-American software company that develops products for software developers, and project managers among other groups. The company is domiciled in Delaware, with global headquarters in Sydney, Australia, and US headquarters in San Francisco.

Crucible is a collaborative code review application by Australian software company Atlassian. Like other Atlassian products, Crucible is a Web-based application primarily aimed at enterprise, and certain features that enable peer review of a codebase may be considered enterprise social software.

<span class="mw-page-title-main">HipChat</span> Web service for internal/private chat

HipChat was a web service for internal private online chat and instant messaging. As well as one-on-one and group/topic chat, it also featured cloud-based file storage, video calling, searchable message-history and inline-image viewing. The software was available to download onto computers running Windows, Mac or Linux, as well as Android and iOS smartphones and tablets. Since 2014, HipChat used a freemium model, as much of the service was free with some additional features requiring organizations to pay per month. HipChat was launched in 2010 and acquired by Atlassian in 2012. In September 2017, Atlassian replaced the cloud-based HipChat with a new cloud product called Stride, with HipChat continuing on as the client-hosted HipChat Data Center.

<span class="mw-page-title-main">YouTrack</span>

YouTrack is a proprietary, commercial browser-based bug tracker, issue tracking system, and project management software developed by JetBrains.

<span class="mw-page-title-main">Zendesk</span> American customer service software company

Zendesk, Inc. is a Danish-American company headquartered in San Francisco, California. It provides software-as-a-service products related to customer support, sales, and other customer communications. The company was founded in Copenhagen, Denmark, in 2007. Zendesk raised about $86 million in venture capital investments before going public in 2014.

Help Scout, legally Help Scout PBC, is a global remote company headquartered in Boston, Massachusetts, specializing in help desk software. The company provides an email-based customer support platform, a knowledge base tool, and an embeddable search/contact widget for customer service professionals. Help Scout's primary product is a web-based SaaS help desk that complies with HIPAA regulations.

Q&A software is online software that attempts to answer questions asked by users. Q&A software is frequently integrated by large and specialist corporations and tends to be implemented as a community that allows users in similar fields to discuss questions and provide answers to common and specialist questions.

<span class="mw-page-title-main">Aha! (company)</span> American software company

Aha! is a cloud-based software company that provides product development software for companies in the United States and internationally. Aha! offers Software-as-a-Service (SaaS) products for organizations to set strategy, ideate, plan, showcase, build, and launch new products and enhancements.

Tuleap is an application lifecycle management system which facilitates agile software development, design projects, V-model, Requirement Management, and IT Services Management. It is open source, released under the GNU General Public License, version 2.

References

  1. 1 2 3 "The Networked Help Desk 1.0 Protocol". 2011-06-01. Retrieved 2016-05-06.
  2. "The Java Community Process(SM) Program - JSRs: Java Specification Requests - detail JSR# 091". 2007-08-21.
  3. "Open Standard for Customer Service and Help Desks". 2011-06-01.
  4. Asay, Matt (2011-06-01). "One help desk API to unite them all: Down with the Software Tower of Babel". The Register . Retrieved 2016-05-06.
  5. 1 2 Carr, David F. (2011-06-07). "Help Desk Shuffle: Will New Standard Help?". InformationWeek . Retrieved 2016-05-06.
  6. "Networked Help Desk Members" . Retrieved 2016-05-06.
  7. Latkiewicz, Matthew (2011-06-07). "Zendesk's JIRA Integration Rocks!" . Retrieved 2016-05-06.
  8. "NetworkedHelpDesk.org Welcomes 34 New Member Companies". 2011-08-12. Retrieved 2016-05-06.
  9. "NetworkedHelpDesk.org: One Year Later". 2012-05-31. Retrieved 2016-05-06.
  10. 1 2 "Share Customer Support Tickets Seamlessly with Zendesk". 2011-06-02. Archived from the original on 2011-10-28. Retrieved 2016-05-06.
  11. 1 2 Latkiewicz, Matthew (2011-06-06). "Share Support Tickets Across Multiple Zendesks With Our New Ticket Sharing Feature". Archived from the original on 2014-01-22. Retrieved 2016-05-06.
  12. Latkiewicz, Matthew (2011-06-06). "Networked Help Desk: An Open Standard for Better Customer Service" . Retrieved 2016-05-06.
  13. 1 2 Feil, George (2011-06-08). "Building the Web 3.0: NetworkedHelpDesk" . Retrieved 2016-05-06.
  14. Weinberger, Matthew (2011-06-07). "NetworkedHelpDesk.org: Helping Partners Break Help Desk Barriers?" . Retrieved 2016-05-06.
  15. Finley, Klint (2011-06-07). "New API Aims to Unite Customer Service Applications". ReadWrite . Archived from the original on 2013-09-23. Retrieved 2016-05-06.
  16. 1 2 Hinchcliffe, Dion (2011-06-18). "Enabling collaboration with open APIs". ZDNet . Retrieved 2016-05-06.
  17. "API Walkthough" . Retrieved 2016-05-06.
  18. "GitHub - bestpractical/rt-extension-nhd". GitHub . 2011-08-10. Retrieved 2016-05-06.
  19. "Integration with Zendesk". Archived from the original on 2016-05-21. Retrieved 2016-05-06.
  20. "GitHub - zendesk/ticket_sharing: Ticket Sharing". GitHub . Retrieved 2016-05-06.
  21. "Résumé of Darren Boyd". Archived from the original on 2017-11-11. Retrieved 2016-05-06.
  22. "HostBill 3.4.1 Release – introducing ticket sharing". Archived from the original on 2017-10-02. Retrieved 2016-05-06.
  23. "Configuring support: Ticket Sharing" . Retrieved 2016-05-06.
  24. "Configuring Support". Archived from the original on 2016-03-30. Retrieved 2016-05-06.
  25. cdn.hostbillapp.com/modules/ticketing-system/ticket-sharing.swf
  26. Yan, Steven. "Setting up and using Zendesk for JIRA Server (OnPremise)" . Retrieved 2016-05-06.
  27. "networkedhelpdesk" . Retrieved 2016-05-06.

Further reading