DASHBOARD

The Dashboard provides an overview of all ticket-related information, including:

• High and Critical priority tickets
• Open Tickets
• Total Tickets Closed
• Unassigned Tickets

Users can also export the list of tickets directly from the dashboard.

Overview: The dashboard layout includes filters and sorting options for easy navigation. It displays tickets assigned to Customers, Partners, Distributors, and Admins in their dashboards. Tickets can be sorted according to user preferences. By default, the Open Tickets and My tabs are displayed, listing all open tickets for the user. Additional tabs like Forwarded, All, and Closed allow users to view tickets in different states.

Key Actions:

• View Ticket Details: Click on any ticket to access further information.
• Ticket Number: This is the unique identifier assigned to the ticket. In this case, the format starts with "CT" followed by the date and a sequence number. The ticket number helps track and reference the issue.
• Created On: The date and time when the ticket was initially created. This timestamp helps in tracking how long the ticket has been open.
• Last Modified: The date and time when any update or modification was last made to the ticket. This provides insight into the most recent activity on the ticket.
• Ticket Aging: Displays how long the ticket has been open, providing the total time since the ticket was created. This helps in monitoring how long the issue has remained unresolved.
• Category: This refers to the classification or type of issue the ticket relates to. Categories are often predefined and help in organizing tickets based on their nature.
• Service Type: Specifies the kind of service the ticket is related to. Similar to the category, it helps identify the context of the request or issue.
• Problem Details: This field contains a description of the issue or problem reported in the ticket. It provides relevant information about the problem to the technician or support staff handling the case.
• Assign to Technician: Tickets can be assigned to technicians directly from the dashboard. The ticket owner or the technician can perform this action.
• Change Priority: Select the appropriate priority level for the ticket based on the urgency or importance of the issue.
• Forward Ticket: Forward the ticket to another tenant within the hierarchy for further handling.
• Re-open Ticket: If the ticket has been closed but the issue persists, it can be reopened for further investigation.
• Reply to Ticket: Users can respond directly to the ticket to provide updates or request more information.
• Merge Ticket: Merge Ticket allows users to combine multiple duplicate tickets into one to streamline ticket management and maintain clarity in issue resolution.
• Forward Ticket: Forward Ticket allows an assigned user to pass a ticket to a higher authority or a more suitable person when they are unable to resolve the issue.
• Close Ticket: If a resolution is found, the ticket can be closed.

1. Assigning Ticket to technician

This process allows users to designate a specific technician to handle a support ticket, ensuring that the appropriate person is responsible for resolving the issue.

What Happens: When a ticket is opened from the dashboard, the user can click the edit (pencil) icon under the Technician field. This action opens the "Assign Technician" dialog, where the user can select a technician from a list. After selecting and clicking Save, the chosen technician's name will appear in the Technician field, indicating they are now assigned to that ticket.

An email confirmation will be sent to the technician, the ticket owner, and the tenant owner.

Why This is Given: This feature is provided to streamline ticket management and ensure accountability in resolving customer issues. By assigning tickets to specific technicians, organizations can improve response times and maintain clear ownership of support requests.

Who Can Do This: Typically, users such as administrators, module admins, Global admins, and contributors at the particular tenant's level can assign technicians to tickets. This allows authorized personnel to delegate tasks effectively within the support system.

To assign a ticket to a technician, follow these steps:

1. Open the ticket from the dashboard.
2. Click on the edit (pencil) icon located under the Technician field.
3. The "Assign Technician" dialog will appear.

4. Select a technician from the list and click Save. The technician is now assigned and displayed in the Technician field.
   

2. Changing Ticket Priority

Changing the priority of a ticket is essential for effective ticket management and resource allocation. By categorizing tickets based on their urgency and impact, organizations can ensure that critical issues receive immediate attention while less urgent matters are addressed in due course. This helps maintain operational efficiency, improves customer satisfaction, and allows support teams to focus on resolving the most pressing problems first.

To change the priority of a ticket, follow these steps:

1. Click on the edit (pencil) icon under the Priority field.
   

2. The "Priority" dialog will be displayed, showing the following options:
   

   • Low: For issues that do not significantly impact operations and can be addressed later.
   • Medium: For important issues that should be resolved in a timely manner but do not require immediate attention.
   • High: For issues that have a significant impact and should be addressed promptly, but are not urgent enough to require immediate resolution.
   • Critical: For urgent issues that severely impact operations and need an immediate resolution to restore functionality.

3. Select the appropriate priority based on the impact and click Save.

4. The new priority will be updated on the ticket.

3. Ticket Sub status

Purpose: The sub-status of a ticket is crucial for tracking its progress and allows users to see the current status of tickets at a glance.

• After a ticket is assigned to the technician, the sub-status field gets enabled for editing.
  
• The technician can click on the Edit Sub-status option to make the necessary changes based on the ticket's progress.
  

Description of Sub-statuses:

1. Unassigned:

• This status is used when no technician or team member is assigned to the ticket yet.
  

2. Assigned:

• The ticket has been assigned to a technician, who is responsible for handling it.
  

3. In Progress:

• Indicates that the assigned technician is actively working on the ticket.
  

4. Awaiting Customer Response:

• The technician is waiting for additional information or feedback from the customer before proceeding further.
  

5. Waiting for 3rd Party:

• This indicates that the resolution of the ticket depends on an external party (Microsoft) vendor, and the technician is on hold until their response is received.
  

Editing Sub-status:

• The technician can change the sub-status of the ticket as needed, based on the progress or requirements. For example:
  

  1. Set to In Progress once the technician starts working on the issue.
     
  2. Set to Awaiting Customer Response if the technician needs more information from the customer.
     
  3. Set to Waiting for 3rd Party if the issue is dependent on an external provider.
     

• If the assignment is changed or the technician is unassigned, the sub-status is reset automatically, and the new technician can update the sub-status as needed.

4. Forward Ticket

If an assigned person believes they are unable to handle a ticket, they can forward it to the next higher hierarchy. For example, if a Partner cannot resolve an issue, they can forward the ticket to their Distributor or Admin.

Note

Once the ticket is forwarded, the previous ticket handler will no longer be able to perform any actions on that ticket.

5. Closing a Ticket

Once a ticket has been resolved and a solution provided to the affected user, the ticket can be closed. The ticket can be closed either by the person who provided the solution, the person who created the ticket, or the technician who handled the ticket.

To close a ticket, the person closing it must provide proper comments, including resolution details, in the Closure Summary/Ticket dialog. Adding attachments, such as relevant screenshots, is optional. This information will be listed on the ticket details page along with the closing status.

Once a ticket is ready to be closed, follow these steps:

1. Click the Close Ticket button. A confirmation dialog window will appear asking, 'Are you sure you want to close this ticket?'
   
2. Click OK to proceed.
   

3. In the next window, fill in the Notes section with any relevant details.
   
4. Select the reason for closure from the following options:
   
   • Resolved: The issue has been successfully addressed.
     
   • Rejected: The ticket is being closed without resolution.
     
   • Duplicate: The ticket is a duplicate of another issue.
     

Once the ticket is closed, the reason for closure can be seen on the ticket details page.

6. Re-open Ticket

Note

The person who created the ticket, as well as users with the appropriate permissions, have the option to re-open it if they are unsatisfied with the resolution or if the issue reoccurs.

To reopen a ticket, follow these steps:

1. Click the Re-open Ticket button.
   

2. This will open the Reopen confirmation dialog. Click OK in the confirmation dialog to proceed.
   

3. The Re-open Ticket dialog will be displayed. Provide comments explaining why the ticket is being reopened and attach any relevant files if necessary.
   

4. Click the Re-open button to finalize the action, and the ticket will be reopened.

Note

All actions taken on the ticket, from creation to closure, will be communicated via email to all users who were mentioned when the ticket was created.

7. Contact Information

In the "Contact Information" section, you see details about the user associated with the ticket.

• Name: Shows the name of the user.
• Country Code: This displays the country code for the phone number, in this case, "+1 (US)" indicating the United States.
• Phone Number: Displays the user's contact phone number.
• Email: Shows the email address associated with the user.
• Additional User Mails: Here, you can optionally add one or more email addresses for additional users who should receive notifications about the ticket.

Edit Contact Information: Allows the user to update the contact details for the ticket by clicking the "Edit Contact Information" button.

8. Replying a Ticket

If the Technician requires more information regarding a ticket, or if the person who created the ticket wants to add additional details, they can do so by following these steps:

1. Click on the Activity tab on the ticket details page.
   

2. On the Activity details page, you have the following options:
   

   • Add a comment.
     
   • Add a comment with images or a screenshot.
     

3. To add comments and images, click the Reply button. This will open a dialog for adding comments and attachments.
   

4. Enter your comments and attach any images, then click Send Message.
   

Once a comment is added, all users who were mentioned when the ticket was created will receive a notification.

All replies from the ticket logger and ticket handler will be listed in this tab.

Everyone: When this option is selected while replying (by a Partner or higher role), the reply message is sent to everyone, including the Customers.
Technicians: When this option is selected while replying (by a Partner or higher role), the reply message is sent to all users except Customers.
- If it’s a customer ticket, the customer will not be notified.
- If it’s a partner ticket, the partner will not be notified if any comments are added.

Comment: This is a section where users can leave comments or messages regarding an issue they are facing. Timestamp: This field records the time at which the comment or action was taken. It indicates the exact date and time when the comment was posted. Created By: This field specifies who created the comment or raised the issue.

Action Buttons:
- Cancel: This button is for canceling the message you're writing, and returning the form to its previous state.
- Send Message: This button is used to send the typed message once it’s ready.

9. Logs

It records the history of activities on a ticket.

1. Log Type: - This column displays the type of activity or action that took place in the system.

2. From Value ➡ To Value:
- This column typically tracks the changes in the values before and after an update. It shows the old and new values when there is a change in the status or priority, for example.
- In this case, both logs have "N/A" (Not Applicable), meaning the logs were either actions that didn’t involve changes to any values, or this field is not relevant for the types of activities logged.

3. Event Initiated By: - This column records who triggered the event or made the change.

4. Created On: - This field captures the date and time when the activity or event occurred.

5. Message: - This column might display a more detailed message or description of the log entry.

10. Attachment

It shows a list of files that have been uploaded to a specific ticket.

1. File Name:

• This column displays the name of the uploaded file.
  

2. Size:

• This column shows the size of the file that has been uploaded.
  

3. File for:

• This column indicates the purpose or context in which the file was uploaded.
  

4. Uploaded By:

• This column shows who uploaded the file. Supported formats include PNG, JPG, video files, documents, Excel, PDF, and other common file types.
  

5. Uploaded On:

• This column records the date and time when the file was uploaded.
  

6. Download and View:

• You can preview and download the attached image or file directly from this dialog.
  
• The download icon (⬇️) allows users to download the file, and the view icon (👁️) allows users to preview the file.

11. Merging Ticket

Multiple tickets can be merged if they are identified as duplicates. Once merged, the tickets are considered closed, keeping one open.

Ticket merging can be done from the Ticket Overview page in two ways:

1. Using the "Merge Ticket" Button:

• Click the Merge Ticket button. This will open the Merge Ticket dialog. In the dialog, select the duplicate ticket you want to merge with. Once the merge is complete, the open ticket will be marked as "Closed" and labeled as "Duplicate."

2. Using the "Merged Tickets" Tab:

• Click on the Add Duplicate Tickets button in the Merged Tickets tab.
  

You can search and select multiple tickets by typing in the search field.

• Once the duplicate tickets are added, they will be marked as "Duplicate" and their status set to "Closed."
• The primary ticket will remain open and is considered the original, containing all relevant information about the ongoing issue.
• The tickets listed are associated with the Current Tenant and the Ticket Owner.

12. Unlinking Tickets

Tickets can be unlinked if the issue reoccurs or if the tickets were mistakenly merged and closed.

• To unlink tickets, navigate to the Primary Ticket or the ticket's Primary Tenant.
  
• The ticket can then be reopened.
  
• Tickets can also be unlinked from the Merged Tickets tab of the Primary Tenant.
  

13. Export Ticket

Users can export closed tickets and download the detailed information in a ZIP file. The ZIP file contains:

• A PDF file with ticket details.
• Attachments related to the ticket.

PDF file contains:

• Problem details
• Contact information
• Activities and logs
• Merged tickets

Attachments: All files or attachments added during ticket creation, replies, forwarding, or in the closing summary will be included in this section.

By default, the Ticket Overview and Contact Information are included in the export. Users can choose to include additional details such as Activity, Logs, Merged Tickets, and Attachments before exporting.

FAQs

Q. Who all receives email when a ticket is created?
A. All those users whose email id was added when creating a ticket.

Q. What kind of notifications are received on email?
A. All Kinds of email notifications are received. Ticket created, Reply, close ticket, Forward ticket, Priority changed, Technician Assigned, Ticket Re-opened

Q. How Partner will get to know that customer has created ticket?
A. Once customer creates a ticket, partner and customer both will get notification on mail. And customer created ticket will be added on the Dashboard menu for partners.

Q. How to differentiate who created tickets?
A. Customers created ticket number starts with CT, where Partners created ticket number starts with PT.

Q. As a partner if i am unable to solve the customer problem, then what i should do?
A. You can forward that ticket to respective distributor or Admin.

Q. As a partner can i create a ticket on the behalf of Customer?
A. Yes, Partner can create on the behalf of customer.

Q. Can I change the priority of the ticket after creating the ticket?
A. Yes, Priority can be changed after creating the ticket also.

Q. If partner is unable to resolve the customers issue, can they directly forward ticket to admin?
A. Yes, Partner can bypass ticket to Distributor and directly forward it to Admin.