@Troy: I think a new topic has been opened for that request: http://feedback.repairshopr.com/forums/165658-general/suggestions/6810446-multiple-checklist-on-a-single-ticket

@EveryoneElse: Please vote for the above new topic if that is what you are looking for.

This needs to be re-reviewed. The idea has been skewed and misunderstood. The revised topic should be more like "Ability to Reference and Edit (Multiple) Procedure Lists for a Single Ticket".

Hey Thomas... As a current workaround we are using a program called foxit Phantom PDF. We are creating digital "fillable" pdf checklists. They are filling our "paper" to "digital" migration needs.

This may be a good temporary solution until RS has a solution that is usable. We just leave the checklist in a folder (on the root drive, in a folder on the desktop, etc...) and go through the checklist. We also use something called hotkeyP which allows for time and date stamps by using a keyboard combination such as "CTRL+SHIFT+A". This then inserts the date and time stamp with the Tech name. Works well for now.

When the work is done, we manually add the checklist to the client file/ticket as a file upload.

It would be great to see this as a feature so we can get rid of this work around :)

We're currently using the custom fields to mark off symptoms, and to note things like whether they dropped off their power adapter for their laptop. These custom fields are great for check-in. But this doesn't work well for the type of checklist being requested here. We too require techs to go through series of steps for each type of repair, signing off on each step as they go. This way, we can pick up right where someone left off. This would be a great feature in RepairShopr!

On another note Troy~ The custom ticket fields would work, as you stated, if the client was only approving a single repair option (1 process for the repair). Where this stops working is when the client requests more than a "single Process repair".

Example...

I want you to backup my data (1 process)
I want you to do diagnostics to find if my computer has bad parts in it (1 process)
I want you to set my computer back to factory specs (1 process)
I want you to optimize my computer and get rid of all the advertising that came on it from factory (1 process)
I want you to install and configure my antivirus (1 process)
I want you to install my printer (1 process)
I want you to install and setup my email (1 process)
I want you to install and setup my quickbooks program (1 process)
Perform QA of all work and checklists (overview process)
I want you to train me when all of these customizations are done (1 process)

The list can go on and on and each of these requests can have a specific process and steps on them. If we were allowed to create a checklist and attach multiple checklists to a ticket... we could complete these tasks more easily.

Sometimes you can group these tasks together such as: Basic Maintenance, Advanced maintenance, Complete Maintenance, Complete Maintenance Plus!

Each of these upgrades adds to the checklist of work that we perform. Sometimes a client wants to add antivirus to their maintenance package. Antivirus programs have customizations that need to be done on them as well like security settings, alerting, protection auto decisions, etc...

Just trying to give a little more insight~

-Chuck

Hi Troy,

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!

Thanks for listening!

A loyal supporter of RS!

Hey @brad - this seems like it would be simple to implement a template in Canned Responses and just tell your techs to use it

I think that good note taking would let the tech taking over know exactly what has been done and what needs to be. I would like to see templates that we could customize for internal notes. The techs fill out the form or template.
EXAMPLE:
Performed: Running Apple service diagnostics.
Status:RIP(Repair in Progress)
Parts Used:Hard drive
Parts Ordered:NA
Next:If passes clean and call customer ready for pickup.
Additional Notes:

Take a look at and vote for my idea that's essentially suggesting the same thing but with a nice report to go along with it

http://feedback.repairshopr.com/forums/165658-general/suggestions/5456798-multi-point-assessment-tool-report

I think this is a great idea as well. It would certainly be helpful in keeping the staff on track, and make it easy to follow up on someone who might be out of the office that day.

This would be very helpful indeed!