Ryan,

I agree 100%. We use checklists too for new employees, but without a way in our system to store it it becomes a very cumbersome task to manage. If Repairshopr had it built in, we would instantly be able to go back and see who performed what task and why the ball was dropped on it in a customer satisfaction issue.

Copied from Power User @Chuck:

-----------------------------------------------------------------

Most repair shops have checklists relating to the "steps" in repairing devices such as phones and computers. When you explain the "type" that is great to help differentiate the type of repair that it is. This is useful if you have certain employees that are designated as "repair" specialists. It helps them quickly find types of repairs... even if they are not necessarily assigned to them. Since RS doesn't have departments or employee groups yet, this is the way you can find ticket types that may pertain to you but could be assigned to a different tech.

I think what everyone is asking for, including us, is a way to create a template that could be followed for repairs. The problem with ticket type is that computers have a variety of repair processes... from data backup processes to os reinstallations...

The actual type of repair is the same... computer... but the repair process for requested repairs can be VERY different.

Example: Fresh OS reinstallation is very different than per say a manual adware/malware removal process.

When visiting/talking with other repair shop owners (cell phones, computers, tablets, etc...) many have some sort of repair process written down from either a word or excel document. This is a crucial step when new employees are hired and to keep processes the same for repairs. Most of the time, the process is the same (obviously with exceptions that can occur), so a checklist is important to set the "standard" for that repair. Each checklist would have a validation performed by either another employee or by a manager to ensure that the repair is complete and meeting the standards set by the shop.

The problem with using canned responses is each tech would need to search through the responses in a ticket to find out where the repair is at. With some tickets... this will not be a quick or easy process.

If each user had a single point of reference (per say a checklist or many checklists), each user could simply see which steps have not been completed.

Maybe it would be beneficial to have each of us requesting this Checklist to send you examples. This may provide insight on how this checklist helps communicate "where" the repair is at without getting overly complicated...

We were very excited about the ticket types since we were going to create a checklist with it... but soon realized that it would not fit what we needed...

It didn't solve our issue because...
1. Couldn't select more than 1 checklist to use on a repair ticket
2. If you changed between checklists, the previous entries/selections were lost.

We quickly adapted and used the "ticket types" for our checkin process for equipment. We used it to select the "fixed" rate programs that the client has approved for us to do. If it wasn't a fixed rate repair, we choose the custom per hour ticket type. This allowed us to have checkin criteria such as model, make, approved services, condition, and other details that were great for reference.

I think bottom line, each shop is going to have different repair checklist and we would all love to get rid of written/printed checklists and go completely digital.

The functions of "ticket Types" are perfect for creating a digital checklist. We just need the functionality to allow to select from a checklist group that would relate to the ticket type. In that group, you could select the checklists that are part of this repair. Then based on these selections, each tech could do the work and then easily click the "checkbox" stating that they are done with this part of the repair.

It is much more simple for us to look at a checkbox than to read through comments. Either it is done (checked) or it is not done (unchecked). That is what we need. Simple and clean.

Relating to your Canned responses idea... wouldn't it be better for this to be related to client repair updates or standardized comments than for internal note/repair process communications? In my humble opinion, it would be easier to segregate the repair process out of the comments using the checklist. This way, techs know where to look to see progress of the repair versus trying to sort through the dialog between the client and the techs.

We still use a paper checklist at this point until RS has a solution that allows us to get rid of the paper.

All in all...

It would be great if...

Comments = dialog between the client and tech or between tech to tech dialog - used for better understanding when notes or checklist does not provide enough clarity.

Notes = most important data used in ticket - easy reference

Checklist = status of repair - how far along it is in the process.

I hope that helps - I'm sure others would love to do a conference call to discuss if needed. This feature would sure help us out!

----------------------------------------------

Just want to reference this existing topic that is essentially what you are saying (I think).

http://feedback.repairshopr.com/forums/165658-general/suggestions/5460412-need-a-checklist

This topic has already been completed (not satisfactorily) and I'd like to see this idea get completed the way we (and you) are intending. I'm going to paste in some important info from that other topic, and let me know if you agree or disagree with any of it.

Yeah it would be great to have the 4 steps at the top of the ticket be changeable or able to be toggled.