Service procedures for computer and phone repair.
- Thread starter Haroon92
- Start date
Archon Prime
Well-Known Member
- Reaction score
- 1,232
- Location
- Canada
Look! Some things I found on google to get you started...
https://www.ifixit.com/Wiki/General_Computer_Repair_Procedures
http://wrightpctech.com/item/7-computer-repair
https://www.ifixit.com/Wiki/General_Computer_Repair_Procedures
http://wrightpctech.com/item/7-computer-repair
- Reaction score
- 3,493
- Location
- Manchester UK
I'm not being funny here. but this is pc repair 101.
if you need a service procedure for computer repairs, your going to be really struggling with the intranet job.
if you need a service procedure for computer repairs, your going to be really struggling with the intranet job.
Come on man; have some faith in me...lol
What I was really speaking of was a flow chart. From the customer enters the door. The first step would be to listen to their complain. The second would be to inform them that we will have to do an assessment and the fee that will be charged. Thirdly, Let the fill out the drop off form sealing the form with their signature...etc. That's what I'm talking about really.
Archon Prime
Well-Known Member
- Reaction score
- 1,232
- Location
- Canada
So training material? lol Yeah I go with the "flow". I don't think anyone really uses a "procedure". Waste of time imo.
- Reaction score
- 3,493
- Location
- Manchester UK
Again, you don't need a procedure chart or flow chart for this.
You have just mentioned in this post what you want to do, so stick to it.
I just was wondering if there is a better way...Thanks.
Krynn72
Well-Known Member
- Reaction score
- 2,294
- Location
- Connecticut
Yep, the Technibble Computer Business Kit has some checklists for common computer repairs. Use those and modify to your needs.
I also remember seeing a flow chart for diagnostics somewhere on the internet, but it was a bit dated even a couple years ago. I'm sure you can find it on Google.
To the people arguing against process sheets, I'd guess you're probably not a large operation? The point to procedures and checklists and flow charts is to make a consistent level of service for every customer and help your employees work together, picking up where each other drops off, etc. They are not pointless unless you are a sole operator and even then they could still provide some benefit over relying on fallible human memory.
Well said...Here is someone that understands me perfectly. "help your employees work together, picking up where each other drops off", the main reason.
Tech Savvy
Active Member
- Reaction score
- 211
- Location
- New Jersey
Also, I think @callthatgirl has an operations manual that she sells that contains a couple of workflow documentations(intake, discharge, phone calls, opening/closing shop...etc)
Plus take these kits and tools, but make them your own, if something doesn’t work for you, don’t put up with it, change it. If something is annoying, change it. In the beginning I was constantly changing how I did things, what phrases I was using to actually sell things or products to use as add ons.
Plus take these kits and tools, but make them your own, if something doesn’t work for you, don’t put up with it, change it. If something is annoying, change it. In the beginning I was constantly changing how I did things, what phrases I was using to actually sell things or products to use as add ons.
Thanks. I Found it, I think.
cypress
Well-Known Member
- Reaction score
- 1,496
- Location
- South Florida
Yeah I read over the operations manual that @callthatgirl had done years back and it was very helpful as well.
This a procedure I have in the process flow: The customer drops of the machine, signs the assessment form, and the next step would be to carry out the assessment, and after the asssessment has been completed, the customer is contacted to come and pick up the invoice before proceding with repairs. But I'm kind of concerned, because not everyone would be happy to come back to the store just to agree to proceed with repairs and collect an invoice. Comments..Thanks.
Porthos
Well-Known Member
- Reaction score
- 14,299
- Location
- San Antonio Tx
95% of the time I already know what needs to be "done/fixed" on any computer I receive. This is done at the time of dropoff.
All booting computers are booted in front of the client at drop off and look at installed programs. ( With experience you can spot crap a mile away)
A HD smart test is run I also inform them that that "GOOD" quick test is not a guarantee the drive is 100% good.
I get the client to show me what they think is wrong if I already did not figure it out myself.
Create an Image or a fabs backup depending on issue.
Do work order and get signature. If more advanced diags are needed collect diag fee in advance to credit to bill at the end.
NON-Booting computers.
Boot from PE disk and test drive. If drive is bad stopthere and clone drive (charge accordingly (it will be a lengthy process)
If drive is good I get a fabs backup because It will probably need a clean install of Windows. (especally Win 8 or 10.)
My intake is basically an interview of the clients needs/issues and the computer. I have found that this process gives a client more trust that you know what you are doing and that you care about their data.
If the only way you know to fix a computer is Googling and using youtube "you might be a Redneck" I mean"pizza-tech"
Markverhyden
Well-Known Member
- Reaction score
- 11,221
- Location
- Raleigh, NC
To be honest build your own. Only you know what your environment is. Of course something to reference as well helps. If you have not you should purchase the Technibble Business Kit which is full of stuff. I seem to remember they did have some operations type forms amongst others.
Last edited:
- Reaction score
- 3,493
- Location
- Manchester UK
Another vote here for the TN bus kit.
As your just starting off with your technician career, it has a lot of things which im sure you would find invaluable.
As your just starting off with your technician career, it has a lot of things which im sure you would find invaluable.
Customer doesn't have to travel back to authorize repair they get a quote which shows the price. They either approve the quote or they don't.
If they approve it we move forward with the additional work and bill them at the end. This allows them to make a single trip back once the PC is ready.
Sent from my SM-G870W using Tapatalk
If they approve it we move forward with the additional work and bill them at the end. This allows them to make a single trip back once the PC is ready.
Sent from my SM-G870W using Tapatalk
GTP
Well-Known Member
- Reaction score
- 9,998
- Location
- Adelaide, Australia
My workflow is pretty simple.
Client calls (on phone or in person) says PC is shite, slow, dead, acting weird, or all of the aforementioned.
I say " drop it off (or leave it with me if they're in the office) and I'll get it fixed up for you."
Client drops off computer and gives brief description of the problem.
I wave my magic wand on said POC and lo! It works! Ring client with good news, client collects, takes invoice, transfers money via EFT at their leisure within a couple of days.
New clients pay cash until we get "friendly."
Happy days!
Client calls (on phone or in person) says PC is shite, slow, dead, acting weird, or all of the aforementioned.
I say " drop it off (or leave it with me if they're in the office) and I'll get it fixed up for you."
Client drops off computer and gives brief description of the problem.
I wave my magic wand on said POC and lo! It works! Ring client with good news, client collects, takes invoice, transfers money via EFT at their leisure within a couple of days.
New clients pay cash until we get "friendly."
Happy days!
Similar threads
