| Networked Help Desk | |
| First Published: | June 2011 |
| Version: | 1.0[1] |
| Organization: | Zendesk |
| Base Standards: | HTTP, JSON, REST |
| Related Standards: | JSR 91: OSS Trouble Ticket API[2] |
| Abbreviation: | NHD |
| Domain: | Issue tracking, Bug tracking, Customer relationship management, Project management.[3] |
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.[4] [5] 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.[6] [7] The first integration, between Zendesk and Atlassian's issue tracking product, Jira,[6] was announced at the 2011 Atlassian Summit.[8] By August 2011, 34 member companies had joined the initiative.[9] A year after launching, over 50 organizations had joined.[10] Within Zendesk instances this feature is branded as ticket sharing.[11] [12] [13]
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.[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.[16] Once implemented, two systems can quickly share tickets with just a configuration change as they both understand the same interface.[17]
Communication between two instances on a specific ticket occurs in three steps, an invitation agreement, sharing of ticket data and continued synchronization of tickets.[17] 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.[11] [18] Tickets may be shared with multiple instances.[12]
| System | Implementors | Language | Status | Launch date | Refs < | -- This column is for a general reference and does not replace the need to identify references for specific features if the feature is not explained in the general reference --> |
|---|---|---|---|---|---|---|
| Request Tracker | Ruslan Zakirov of Best Practical | Perl | Complete | 2011-08-10 | [19] | |
| YouTrack | Java | Complete | 2013-01-31 | [20] | ||
| Zendesk | Darren Boyd, Pierre Schambacher and Josh Lubaway | Ruby | Complete | 2011-06-01 | [21] [22] | |
| HostBill | PHP | Complete | 2012-05-05 | [23] [24] [25] | ||
| Jira (from Atlassian) | Java | Complete | 2011-06-01 | [26] | ||
| Node.js | JavaScript | Incomplete | [27] |