quizbowler1057
New Member
- Reaction score
- 0
- Location
- Northeast Ohio
Hi Guys,
I haven't been around in a while. I feel like I haven't been pulling my weight, but I've been so busy that every time I post something I get busy and forget to follow up on it.
I've been very lax on my warranty policies for a while, but a recent blackmail attempt has caused me to overhaul my whole procedure. I have a few questions and then I'll post what i have so far for your info and feedback.
1. I'm not sure what info I should be keeping for warranties. I'm figuring:
Customer, purchased date, purchased from, make, model, serial no., MAC address (for network equipment for added verification)., warranty expiration.
2. What info do you keep track of and how is it different from what I have (if at all). How do you store it? I created an excel spreadsheet for temporary purposes but I'm looking for a more automated solution.
Warranty Terms:
Applies to hardware only, valid for one year from invoice date unless otherwise specified. Warranty does not apply
to normal wear or to damage resulting from abnormal use, misuse, abuse, neglect or accident, or to any incompatibility or poor performance.
No refunds. Labor covered for 5 days. No coverage for spyware/viruses. Pickup/delivery fee not included. Any warranty call found to have no defect or problem will be billed. EVERYTHING is invoiced, even if it's a warranty repair and the balance is zero the time and parts are still recorded so the customer knows how much time went into the repair. Serials and MAC addresses listed on the original invoice. Invoice must be kept as proof of warranty.
I think that's it. I just have to put it into nicer words. And here's a final, sort of related question:
Lets say you go spend two hours installing AVG on a clients machine. They call you 5 hours later and say "My computer won't turn on". They describe what appears to be a motherboard issue (power works, fans run, no video or POST). Has nothing to do with what you did and for the two hours you worked on it you never saw any indication of a problem. But in their eyes all they see is it was working, you did stuff, now it's broke. Must be related.
I seem to get a lot of stuff like this where the cause doesn't seem to be related but the person I'm servicing for doesn't know enough about PCs to understand installing AVG (or whatever) wouldn't stop your computer from POSTing.
Comments and feedback horribly appreciated!!!
I haven't been around in a while. I feel like I haven't been pulling my weight, but I've been so busy that every time I post something I get busy and forget to follow up on it.
I've been very lax on my warranty policies for a while, but a recent blackmail attempt has caused me to overhaul my whole procedure. I have a few questions and then I'll post what i have so far for your info and feedback.
1. I'm not sure what info I should be keeping for warranties. I'm figuring:
Customer, purchased date, purchased from, make, model, serial no., MAC address (for network equipment for added verification)., warranty expiration.
2. What info do you keep track of and how is it different from what I have (if at all). How do you store it? I created an excel spreadsheet for temporary purposes but I'm looking for a more automated solution.
Warranty Terms:
Applies to hardware only, valid for one year from invoice date unless otherwise specified. Warranty does not apply
to normal wear or to damage resulting from abnormal use, misuse, abuse, neglect or accident, or to any incompatibility or poor performance.
No refunds. Labor covered for 5 days. No coverage for spyware/viruses. Pickup/delivery fee not included. Any warranty call found to have no defect or problem will be billed. EVERYTHING is invoiced, even if it's a warranty repair and the balance is zero the time and parts are still recorded so the customer knows how much time went into the repair. Serials and MAC addresses listed on the original invoice. Invoice must be kept as proof of warranty.
I think that's it. I just have to put it into nicer words. And here's a final, sort of related question:
Lets say you go spend two hours installing AVG on a clients machine. They call you 5 hours later and say "My computer won't turn on". They describe what appears to be a motherboard issue (power works, fans run, no video or POST). Has nothing to do with what you did and for the two hours you worked on it you never saw any indication of a problem. But in their eyes all they see is it was working, you did stuff, now it's broke. Must be related.
I seem to get a lot of stuff like this where the cause doesn't seem to be related but the person I'm servicing for doesn't know enough about PCs to understand installing AVG (or whatever) wouldn't stop your computer from POSTing.
Comments and feedback horribly appreciated!!!