Ticket Management

Scope

This document covers new concepts and features regarding Ticket Management introduced with the release of CommitCRM version 5.3. The main features are new features include new Ticket navigation, new Ticket Inbox view and enhanced email correspondence management.

Other Ticket references: Ticket Workflow

Introduction

Tickets in CommitCRM provide a comprehensive ticketing system to help you record all the information for a call including status, priority, and nature of the issue, and track time-to-resolution.

Each ticket can support multiple activities for ongoing projects and complex service tickets, as well as access contract/billing information to determine required charging information.

Tickets are the communication point with your customers. This means customers can access Ticket information via Commit Web Interface, or communicate about a specific Ticket using email. All email communication can be logged in the Ticket level. See more details under Email Correspondence.

Ticket Information

Each Ticket in CommitCRM holds information which is relevant for the service call. It keeps information such as the Ticket description, status, due date and more. This information is displayed in the Ticket's General tab and Details tab.
In addition to the general Ticket data, each Ticket can store related information to provide quick access to all data linked to this Ticket.
The Ticket data linked to the Ticket includes:

• Account – The Account which is linked to this Ticket.
• Asset – The Asset which is linked to this Ticket.
• Contract – The Service Contract under which the Ticket was created, and for which the Charges will be billed to.
• Tasks – Pending Tasks for this Ticket (under the Pending tab).
• Appointments – Pending Appointments for this Ticket (under the Pending tab).
• Charges – Charges logged for this Ticket for work, expenses and parts.
• Messages – Internal CommitCRM messages between employees, linked to this Ticket.
• Email Correspondence – All email communication performed for this Ticket (see more details in Email Correspondence).
• Documents – Files linked to this Ticket.
• History – All of the activity performed for the Ticket – updates audit, done appointments and tasks, history notes, emails, documents, etc.

Each Tab shows relevant linked information, and most data can be accessed directly from the Ticket by right-clicking the relevant object or simply double-clicking it.

Ticket Window

The main Ticket window displays tickets by Status. To view all Tickets with a specific Status, simply click the relevant Status in the left pane. There are also other views available, such as Inbox or Dispatcher (see more details under Inbox and Dispatcher). Using these views will show the relevant Tickets, regardless of their Status.

SCREENSHOT

Ticket Navigation Pane

Tickets are displayed in the Ticket Navigation Pane view, allowing easy filtering by status and by employee.

The Ticket Navigation Pane provides the following views:

• Inbox - The Inbox view shows all tickets which are in your Inbox, meaning they have been updated by a customer. Customer updates can happen via the Customer Web Interface or when a new email arrives for this Ticket from a Customer or from an external application (via CommitCRM API). Tickets can also be added to the Inbox manually, using the Move To Inbox option when right-clicking a Ticket. See more details under Inbox.

• Dispatcher - The Dispatcher view shows all Tickets waiting to be dispatched to technicians. The same list is displayed when viewing the main Dispatcher window. See more details in Dispatching Tickets.

• All - This view shows all tickets, with all statuses, open and closed.

• Open (by status) - The main Open view shows all open tickets, i.e. tickets which have a Status which is considered to be "open" (such as New, Scheduled, etc.). Clicking any of the statuses below it will show only tickets with this status.

• Closed (by status)- The main Closed view shows all closed tickets (i.e. Canceled or Completed). Clicking any of the statuses below it will show only tickets with this status.

Ticket Manager Filter

Users who are privileged to view other users' tickets have the option to filter tickets by the Employee managing these Tickets. The Employee managing a Ticket can be seen in the Ticket's Manager field in the General tab.

The Employee filter appears at the bottom of the tree. This filter shows only tickets managed by the selected Employee. The Employee filter works on top of the status filter.

Possible options are:

• Me - show only tickets managed by the current logged-in user.
• All - show all tickets.
• Choose specific employees

Dispatcher

The Dispatcher view within the Ticket window shows the list of Tickets which are pending dispatch. Tickets can be marked for dispatching using the "Waiting for Dispatching" flag in the Ticket details. Tickets can be easily removed from the Dispatch board by clicking the "Dispatch" column on the left.

SCREENSHOT

The Dispatcher view within the main Ticket Tree provides a quick glance at the pending for dispatch Tickets. In order to actually dispatch the Ticket to technicians, use the main Dispatcher window via the applications navigation pane, which lets you appoint the relevant technicians to this Ticket. See more details in Dispatching Tickets.

Inbox

The Inbox view in the Ticket window shows all tickets which are in the Inbox, meaning they have been created or modified by a customer or by a third-party application. Tickets can also be moved to the Inbox manually when needed, to allow better tracking of those specific Tickets.
SCREENSHOT

Ticket updates can be performed by:

• Customers via the [Web Interface|Customer Web Interface]].
• Customers sending emails via [Email Connector|Commit Email Connector]].
• Third-party applications updating or creating Tickets using CommitCRM API. This can be done via Commit Email Connector (API by Email) or directly via the database (using the Programming API). See more details in the CommitCRM API User Guide.

All updates which cause the ticket to appear in the Inbox are documented in the Ticket's History tab.

The Inbox is global, meaning all users see the same Inbox and any changes made by one user will affect all users. For example, if a user removes a Ticket from the Inbox, it will be removed for all users viewing the Inbox.

Ticket Updates

Ticket updates which trigger the Ticket to appear in the Inbox includes:

• New Tickets
  • Web Interface: Customer adds new tickets via the Web Interface.
  • Email-to-Ticket: Customer sends emails which create new tickets by Commit Email Connector.
  • CommitCRM API: Third-party program creates Ticket via the API
• Ticket Updates
  • Web Interface: Customer updates ticket details or adding history notes via Commit Web Interface.
  • CommitCRM API: Third-party program updates Ticket via the API
  • Email-to-Ticket: Customer replies on emails concerning existing tickets.

Read/Unread indications

To see which Ticket updates were already read/unread, two indications are used:

1. Open/Closed envelope
2. Bold indication (for the current logged-in user)

Both Indications appear in all Ticket views, not only in the Inbox view; however, the indications appear only for Tickets which have been updated by an external party (i.e. customer, using the CommitCRM API). Tickets which are created manually by employees will not display these indications by default. In case a customer updates such a Ticket, or if a user explicitly marks a Ticket as Unread, then these indications will take place.

Envelope Indication

In addition to the bold indication which is personal, the Ticket List also shows a global envelope indication next to the Ticket Manager name. The envelope shows whether this customer update was viewed by the Ticket Manager already. The envelope indication appears next to the Ticket Manager in the list and visible to anyone who is privileged to see those Tickets.
The envelope icon varies between a closed envelope (not read) and an open one (read). The system will display a slightly different icon for the currently logged-in user's Tickets, and for other users' Tickets. This way, each user can tell which Tickets have pending updates which were not viewed by the Ticket Manager yet, even if the Ticket is not assigned to them.

SCREENSHOT

Bold Indication

For new updates in the Inbox, the Ticket Manager column in the Tickets list appears in bold until the Ticket is marked as "read". The bold indication is personal and appears only when logged in as the Ticket Manager for this Ticket.

SCREENSHOT

Marking Tickets as Read

The Ticket Manager must go through the new items in order to remove the bold indication. This can be done either by viewing the Ticket for a few seconds, or by explicitly marking the Ticket as "read" using right-click > Mark as Read.

SCREENSHOT

Marking the Tickets as read is a personal option which can be performed only by the Ticket Manager. Note that privileged users can mark Tickets which are managed by other users as read (see Ticket Options).

Adding Tickets to the Inbox

Updates performed by Customers trigger the Ticket to automatically appear in the Inbox. Tickets are automatically added to the Inbox in the following cases:

• Customer adds a new Ticket via Commit Web Interface.
• Customer updates an existing Ticket via Commit Web Interface.
• Customer adds a History Note to a Ticket via Commit Web Interface.
• Customer replies by email to a Ticket via Commit Email Connector.
• Ticket is added or updated via CommitCRM API (i.e. by a third-party program).

Tickets can also be moved to the Inbox manually. This can be done by right-clicking the Ticket and choosing "Move to Inbox". This can be useful in order to draw attention to a Ticket which requires handling by the Ticket Manager.

Removing Tickets from the Inbox

Tickets can be removed from the Inbox manually in two ways:

• Right-click the Ticket and choosing the Remove From Inbox” option.
• Drag a Ticket from the Inbox to any other status in the Ticket tree view. This will automatically change the Ticket status and remove it from the Inbox.

Removing a Ticket from the Inbox will take affect for all users.

Ticket History

Working with tickets in CommitCRM provides a great way to track all activity for a Ticket in a single point. The Ticket gets updated all the time, by Employees (technicians) or by Customers, and this activity is automatically logged under the Ticket History tab.

Ticket updates can be performed via various channels:

• Customer:
  • Updates Ticket details or adds History Notes via Commit Web Interface.
  • Sends email regarding the Ticket using Commit Email Connector.
• Employee:
  • Updates the Ticket via the CommitCRM client application or Commit Web Interface.
  • Sends email regarding the Ticket.
• Third-party Application:
  • External third-party application can use CommitCRM API to update the Ticket.

Ticket updates may include:

• Ticket details update (priority, status, etc.)
• New History Notes regarding Ticket
• Email correspondence added to the Ticket
• Done Appointments or Tasks updates
• New Charges, Documents, Messages added to the Ticket

All Ticket updates and email correspondence sent via CommitCRM application is automatically logged in the Ticket History and can be viewed via the client application or the Web Interface.

When using Commit Email Connector, all emails coming from customers are logged in the Ticket History and also trigger the Ticket to appear in the Inbox.

See more details under Email Correspondence.
SCREENSHOT of Ticket History tab with all types

Email Correspondence

Email correspondence can be managed via the CommitCRM application in two levels:

• Tracking email history regarding a Ticket.
• Managing Ticket Recipients, i.e. defining who should receive a copy of emails being sent regarding a Ticket.

Email Correspondence can be managed in CommitCRM in two possible ways: Basic and Advanced.

Basic Email Correspondence

• The Basic option tracks outgoing emails sent via CommitCRM.
• When sending an email from CommitCRM, the Ticket Recipients are automatically copied to the email recipients.
• Emails are logged as Commit Documents in the Ticket History, and can be viewed by double-clicking the document.

Advanced Email Correspondence

• The Advanced option works with Commit Email Connector.
• Tracks both incoming and outgoing emails automatically.
• When sending an email from CommitCRM, Commit Email Connector's email address(*) is used as email recipient.
• Commit Email Connector distributes emails to the Ticket Recipients.
• Emails are logged as Email Messages in the Ticket History and can be viewed in the history pane directly.
• Employees can reply on emails directly from the Ticket History's Email Message

(*) For explanation regarding Commit Email Connector terminology see Commit Email Connector user guide.

The table below compares email correspondence tracking capabilities in both modes.

Email Correspondence Features

Feature	Basic	Advanced
Send Email from CommitCRM	The Recipients defined for the Ticket are automatically copied to the email.	The Support Public Email Address of Commit Email Connector is automatically copied to the email To: address. Only Commit Email Connector distributes it to the Recipients defined for the Ticket.
Click Reply Email in CommitCRM	N/A	Employees can reply on emails directly from the Ticket History's Email Message. Reply is send to Commit Email Connector, which distributes it to the Recipients defined for the Ticket.
Handle Incoming emails	N/A	Incoming emails (from customers or employees) arrive at Commit Email Connector which: Logs email in the Ticket History. Distributes to Ticket Recipients.
Send emails via any email application	N/A	Employees can send emails from anywhere to Commit Email Connector which: Logs email in Ticket History. Distributes to Ticket Recipients.
View email correspondence in Ticket History	Only outgoing Emails are logged in the Ticket history as Commit Documents. Email text can be viewed by double-clicking the Document.	Incoming and Outgoing emails are logged by Commit Email Connector as an Email Message in the Ticket History. Email Text is displayed in the History pane directly.

Benefits in the Advanced mode:

• Easier history view: The email text itself appears in the History tab, providing a quick review of all email correspondence.
• Incoming and Outgoing email in History: Provides a complete view of all correspondence for the Ticket.
• Emails can be sent from anywhere via Commit Email Connector: Technicians can reply on emails regarding Tickets from any email application, by sending it through Commit Email Connector. This way the reply will be automatically logged in the Ticket history and will reach all External Recipients and Employee Recipients.
• Internal Email Distribution: Emails coming from Employees or Customers are distributed to all Employee Recipients defined for the Ticket, providing better control over the activity in the Ticket. This also provides quick and efficient distribution of service related information to all employees involved in a Ticket.

For mode information regarding the advanced email correspondence, see Email Distribution via Commit Email Connector.

In both cases, the Recipients defined for the Ticket are used in order to send the email to the relevant people. See more details under Ticket Recipients.

Email Distribution via Commit Email Connector

When using Commit Email Connector, all email distribution goes through Commit Email Connector. This means that all emails (incoming and outgoing) are sent to the Support Public Email Address rather than sending the email directly to the recipients. The email is then processed by Commit Email Connector, distributed to the Recipients defined for the Ticket, and logged in the Ticket history automatically.

For user not familiar with Commit Email Connector terminology, it is recommended to read Commit Email Connector user guide for better understanding of this section.

The following chart demonstrates the workflow when using Commit Email Connector:

SCREENSHOT

How does it work?

• When a Customer sends an email relating a specific Ticket, Commit Email Connector processes the email and creates a Ticket in the system for new emails. This service is called Email-to-Ticket.
• An automatic email response for new Tickets is sent to the Customer and to relevant Employees; this response contains the Ticket Number in the email subject and the reply-to address points back to Commit Email Connector.
• From this point on – all email correspondence is sent to, and handled by, Commit Email Connector:
  • The email is logged under the Ticket history (according to the Ticket Number in the subject).
  • The email is distributed to the Recipients defined for the Ticket.

Email Messages View in Ticket History

Email Messages which are automatically logged in the Ticket History show the actual email text in the main history view. The history entry shows an email icon, and the text appears next to it.

SCREENSHOT

The email icon indicates that this is an actual Email Message (as opposed to an email Document), and the email itself can be opened by clicking Show or by right-clicking the icon itself, and choosing Open Original.

When attachments exist in the original email, the icon will indicate this, and when opening the original email, it will open with the attachments.

Note: Commit Email Connector saves the original emails in a basic email format (.eml), which can be opened via Outlook Express. Eml files are basically not compatible with Outlook®, however, it is possible to override this and allow Outlook to open these files. For more details, see this suggested workaround.

Employee Correspondence

All emails sent by employees are sent via Commit Email Connector, i.e. sent to the Support Public Email Address. The email is then distributed to all Recipients defined for the Ticket and is filed under the Ticket history.

This means that employees can reply to emails from any email application (not via CommitCRM application), sending the email to Commit Email Connector, which then handles the actual distribution to all Ticket Recipients.

This way all of the emails are logged in the Ticket history automatically and customers receive all emails from the Support email address (not the employee's personal addresses).

It actually doesn't matter where the email comes from as long as:

• The email is sent to the Support Public Email Address for Commit Email Connector to process
• The Email Subject contains the Ticket number in a predefined format which is used to identify the email as relating an existing Ticket.

For example, the following email will be filed under Ticket number 0500-1000 and distributed to the recipients defined for this Ticket: To: Support@yourdomain.com Subject: Ticket [0500-1000]