What Are Your Expectations For Technician Ticket Notes?

As the title suggests, what do you expect to see in tech notes? Are your expectations set to include precise details, or is a close-out with an "issue resolved, power cycled "X" unit and system was up-and-running" enough?

During my time as a tech/installer, I would fall on the more detail-oriented side. I'd include the contacts I met/spoke with, the hardware (with model #'s) I interacted with, and troubleshooting steps I performed or, if on a project, how many devices I had installed, where, and how many were left to go.

I ask because there were people before me that left the company, and the notes gave me little info about issues that were particular pain points, and no inclination on how best to prepare for a visit (should I bring XYZ device to replace, what wiring, etc.,), and I would end up with a stuffed van for something that required only a small power supply after a site has a surge or a reader went down that I didn't have, thus increasing time on a task where I could have resolved in 1 trip. I'd make good relationships with contacts that knew me and knew I could solve an issue quickly, and having pertinent info beforehand was always a boon.

Login to read this IPVM discussion.
Why do I need to log in?
IPVM conducts unique testing and research funded by member's payments enabling us to offer the most independent, accurate and in-depth information.

*** **** ** ** your ****** ******** *******? Did *** *** ******* to *******?

*** *******,

**, * *** ***, as * ****'* **** know ** *** ********* you ***** **! *'* upload ******** *** ****, but ***** ****-******** ************* was ****** ** * separate ********. ******* ****, sure ***** **** **** nice ****.

***.. *** *** *** the ***** ** ** it ***** *** *** never *********** *** ***** way :)

**** *** **** ******* to ******* *** *** see *** *** ******* of ***** ******* **** purchase ** *******.

**** "***** ****** "*" unit" * ****** ** not * ***!!!!

******** ****!? * *** work **************** ******!? **********

**** **** * **** you ****** **** ****** than *** ****** ****.

**** *** *** **** perspective, * *** *** that ********* **** ****** is ******.

*** **** ******, **** as * ****** *** responding, *** "****** *****, issue ********" **** ** fine, *** * ***** want ** **** *** it ********, *** **/**** the ***** ***** ** expected ** *******, ** more ******* ***** ** needed.

**** * *** *** invoice *** **** ******* being *********, * **** to *** *** **** the **** ****, *** with **** *** **** interacted.

**** ** **** ********. We **** **** ******* that **** ***** *** last ***** ** **** and ****** **** **** a ***-**** ***********.

**** ******, ** ****** you **** ** ******* the ******, *** *** integrator ******** ***** ****** give *** ****** ****** that ** * (*** user) **** *** **** for *** **** ** related ***** *** **** tech **** **** **** going **. ** *** ticketing ****** *****'* ***** you ** **** ******** notes *** *** ****** and ********, * ***** suggest ** *** *** extra ******* *******, *** have *** *** ***** summary *** *** ****** at *** ****** (** at ***, **** ** executive *******).

* **** *** *********** where * **** **** out *** * ********* issuing, *** *** ****** from ******** ****** **** either *** ** ** had *** *** **** any ******* **** *** done, ** **** **** they ***** ******* ******** from *******, *** **** frustrated ** ******* ** cost ***** ***** *****.

** *** **** ******** notes *** ******-****** ***** and *** **** **** the ********** ** *** ticket. ***** ** ***** tag ********** *** ** we **** *** ******* to *** ******* *** see *** *** ******* of *** *******. *** issue ** ****** ******* on **** **** ** through *** *** ***** to ********* *** ***/**** for *** ****** ** this ***** * ********* technical ******. **** ** where ** ********.

** **** ***** ** too **** ****** ** most *****. ** ****** be ****** ** **** another ****** *** **** the ***** *** ************ reconstruct **** *** **** and ***** ** *** left ** ** ********** should *** ******** ********** be ***********.

****** *** **** ** do ** ** *********. Sometimes **'* **********'* ***** notes *** ****** ******* techs **** ********* ** hurry ** *** **** on ** *** **** job. *******, *** **** saved ** ****** ***** ticket ***** *** *** up ******* * *** of **** ****** ** gain ******* **** * chronic ******* *** ******* reconstructing **** ******* **** did. ****** **** ** the **** *** **. saving ** *** ***** end. *** ********** *****, the ***** ** ****** to ****** *** **** someone **** *** *** maybe ****** ** *** the ******** *** *********** that ****'* *** ** the ***** *** **** your ******* * *** appearance ** *** ******.