T1 - Ticket Documentation

This has been intended as a step-by-step guide for the creation and documentation of tickets, It is of great importance to complete all fields as they help keep track of issues and provide important details to make any future decisions 

 

All of the fields below are a must and should not be left blank 

 

 

Step 

Information that needs to be collected or confirmed 

Freshdesk field 

Answering the call 

Collect 

  1. Caller Name 

  1. Phone number 

  1. Email address 

  1. Installer or Homeowner? 

  1. Company name 

Add or edit the contact fields as necessary  

 

 

Confirm the reason of the call 

  • aGate serial number 

  • Confirm that there is no ticket already created for the same contact or serial number. 

  • Site State (you can use Fleetview) 

Any time the serial number is collected the ticket needs to be documented as “troubleshooting” 

 

 

Update component fields 

Confirm the components 

  • aGate or aPower? 

 

Document whatever is closest to the reason, if unlisted then select unlisted 

 

Failure type 

After troubleshooting is completed document if the issue was caused by a firmware anomaly, installation error etc 

 

Also provide a brief description of the issue 

 

Document the ticket 

Make sure to leave detailed notes of what was done during the call, if needed document the following 

 

  • Step by step troubleshooting performed 

  • Alarm logs or screenshots  

  • A brief description of the issue 

  • A brief resolution  

  • Please document if additional steps need to be taken upon a a call back from the caller 

 

D
David is the author of this solution article.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.