After all, when you receive service, one of the first questions is "When can I expect that to be done?" Part of the appeal of a 30 minute oil change is that you know the time frame without asking.
There are lots of variables here. How do you communicate with clients (PSA portal, voice mail, email, telephone)? How do clients try to communicate with you (Facebook, Twitter, LinkedIn, web form, fax)? Then there's the response times as defined in your service agreement, as defined in your PSA system, and as you've "implied" via your personal communication.
On top of all that you have unspoken assumptions . . . on both your side and the client's. Let's start there.
First: Drop Your Assumptions
The unspoken assumptions of the client and the service provider are the biggest cause of problems. Most of the time this is YOUR fault because 1) You didn't set reasonable expectations; 2) You assume the client wants everything right now; and 3) In any service relationship, the person receiving the money in exchange for service is responsible for managing that relationship.
How do you set reasonable expectations? Well, you can start with a one-sheet handout that describes your priority system (see SOP Friday: Setting Job Priorities) along with a one-paragraph summary of your written response times from your service agreement.
You also set reasonable expectations every time you communicate with a client. You can mention your after hours policy ("We don't work evenings and weekends."). When a service request comes in you can try to schedule the work for 1-2 days out.
When you answer the phone and enter a new service request, you need to give the client an idea of when you'll be able to work on their issue. Note: It does NOT have to be immediately, within 15 minutes, or within an hour. It can be "this afternoon," tomorrow, or next week.
You are valuable and you schedule your time for maximum efficiency. You prioritize service requests from Highest to Lowest and Oldest to Newest. That's reasonable. Set reasonable expectations.
Now let's look at the mechanics of response times.
Guaranteed Response Time
In your Service Agreement, you should state two or three kinds of response times. And don't just let them sit on the paper: Explain them to your clients. You don't want them to think all their problems will be fixed in 60 minutes, no matter what the issue is.
Response Type One: Acknowledgement
This means that you communicate with the client and let them know that you've received their request. This is, strictly speaking, your "Response Time." You have responded and now you can give them a reasonable expectation of when you can start working on the request.
It is very reasonable to promise to acknowledge all service requests within one hour. Depending on your processes, this might be by email, voicemail, or telephone. I don't recommend merely clicking "acknowledged" in your PSA tool. Your client probably doesn't hang out all day on your portal.
Response Type Two: Work Begins
This is what most clients think of as response time, until you educate them. This is when the status moved from "Acknowledged" or "Schedule This" to "In Progress."
You will have different times for different priorities. You might have 1-2 hours for a Priority One ticket; 4 hours for a Priority Two; 24 business hours for P3, and 1 business week for a P4.
You might not have guaranteed times for working on P3 and P4 tickets as you'll want to schedule those anyway. Clients only care about fast response to urgent matters (P1/P2). They are often concerned that P3 and P4 tickets won't ever be resolved, so you need to make sure that's not the case. But you may not need to have guaranteed response.
Response Type Three: Resolution
We never use this. We do not guarantee that issues will be resolved within a specific amount of time. You might try this, but NEVER get yourself in a position of losing money systematically because you over-promised.
Promising a resolution time is not (usually) a reasonable expectation. You want to set reasonable expectations, so don't promise a specific time to resolution unless you have to.
All of these are "Guaranteed" Response Times. That means they're written down in your service agreement and you signed it. That's a promise!
They Gotta Use The System
In order for these response times to work, clients must use your system. See How Do Service Requests Get Into Your System?. That means, the client needs to call your service phone number. Or enter a ticket in the portal. Or sent an email that's turned into a service request by Email2AT or a similar program.
If clients call a cell phone, that doesn't count. If they talk to a tech in the field, that doesn't count. If they Tweet something on Twitter or post a complaint on Facebook, that doesn't count. If they bitch on Yelp, that doesn't count.
When someone checks voice mail or gets a request in person, they should put in a ticket. But the clock starts when the ticket is entered, NOT when the client goes around your process. Once your team knows there's a problem, you need to enter a ticket and begin working your process. But it is unreasonable for a client to go outside your process and then hold you responsible for your promises.
What you tell your employees is a different story . . .
Actual Response Time
Meanwhile, at your office, you have a tighter process.
It should be your goals to Acknowledge all service requests within one business hour. And if you have an office manager or someone who stays at the office most of the time, they should be able to acknowledge tickets within 15-30 minutes.
Technicians are NOT expected to check voice mails all day long, or to ever receive a service request by cell phone or voice mail.
Technicians are NOT expected to hang out on email all day, or ever receive a service request to their email address. Technicians check email three times a day.
Internally, you need to have a process to acknowledge all service requests within one business hour. This is very manageable and reasonable. Just do it.
Service delivery (actually starting to work on an issue) depends on the priority. You need to make sure you have a chart that lists your response times. In my opinion, it's okay to set internal goals that are much stricter than the promises in your service agreement. I think one hour to begin work on a P1, two hours for P2, and eight business hours for P3 is very manageable and reasonable.
If your internal process is always better than your written promises, you'll have no problems keeping your written promises.
Your PSA system will automatically track how long it takes to go through each step of the service delivery process. Too many statistics can be worse than not enough. But you should track time to Acknowledge, Time to Begin Work, and Time to Resolution for each service request. You can then run reports by priority and get additional information about how you're doing.
Special Case: Priority One or Server Down - After Hours
There is one important exception to response times that needs a little attention. Servers almost never go down. But when there's a true emergency that needs immediate attention, you need to have a standard process for that.
Quite simply, your response time should be As Soon As Possible.
After hours, on weekends, or on holidays, the response time will be as soon as possible given the resources available. With luck, you have one person assigned to be "on call" for emergencies. This person must never work on non-emergencies outside of business hours.
For a P1 emergency comes up, here's a simple process that works for us:
- Call each person on the client call down list systematically until someone is reached (this list is stored in your PSA system)
- Inform them that there is an issue with their system
- Request directions as to how to proceed. After hours work is always billable, so it must be approved.
- If you reach a voice mail system, leave a message stating that there is a problem and ask how they wish to proceed. Leave the main service phone number/extension.
- Continue calling through the list until you reach someone or exhaust the list.
Once you reach someone:
- If after hours work is requested, inform or remind the client of our after hours rate and then find out when to proceed.
- If after hours work is requested, inform the client that there must be someone from the client's company available to get our technician in and out of the building and office as needed.
Note: The client must have a representative with full access present at all times in the office while our technician is on site.
There are other restrictions for after hours work, but that's another article. ;-)
The Bottom Line: Reasonable Expectations
Never forget that you are running a service business. We get into this business because we want to provide service. But if you don't stay profitable, even during an emergency, then you won't be around to provide service in the future.
The thing about Standard Operating Procedures is that they provide a "normalcy" to what you do every day. You CAN expect problems. You can expect emergencies. You can develop a standard response that keeps the client happy and keeps you from pulling out your hair.
Your job stress will be much lower when you realize that you can schedule work in advance and never run around putting out fires. Many people say they want that, but not everyone is willing to implement processes and procedures to make it happen.
Your Comments Welcome.
- - - - -
About this Series
SOP Friday - or Standard Operating System Friday - is a series dedicated to helping small computer consulting firms develop the right processes and procedures to create a successful and profitable consulting business.
Find out more about the series, and view the complete "table of contents" for SOP Friday at http://www.smallbizthoughts.com/events/SOPFriday.html.
- - - - -
Next week's topic: Email Rules and Etiquette for the Consultant
by Karl W. Palachuk
Now only $39.95 at SMB Books!
Ebook or Paperback