How to manage your daily workflow

Karl Palachuk

There are several roles that need to be performed within the service delivery department of any IT service provider business. The most obvious of these are your technicians. Once you get a few techs on your staff, you'll eventually have a service manager (see this blog for details of their roles and responsibilities). 

One role you’ll need to understand quickly is that of the "Tech on Call for the Day". Discussion around this role can also be applied to a Service Coordinator function – I will use the terms Service Coordinator and Tech on Call interchangeably. Notice that I'm very careful to refer to this as a role, because it might be performed by almost anyone in the company. When you're just starting out, the owner will wear this hat along with the technician hat, service manager hat, front office hat and all the other hats. 

I like to refer to the role as Tech on Call for the Day because it's a very good way to transition into having levels of responsibility in your service department. You can rotate this role between each of the techs on a schedule that makes sense for you. You might rotate every day or every week. 

Rotating this role takes these responsibilities away from the owner or service manager, allowing that person to be more productive in higher-level activities. Rotation has other benefits as well. It allows you to "test drive" each of the techs to see how they might do with additional responsibility. It's also a great way to make sure each of the techs understands the rules of service board management, setting priorities, scheduling work, etc. 

Of course, you have to decide who will and who will not rotate into this position and how frequently. In the beginning, the owner or Service Manager will have to spend a lot of time with the Tech on Call for the Day. 

Tech on Call for the Day Duties

The list of duties for this role is essential to your daily procedures and as such it should be reviewed and changed periodically. Please do not consider this list static and be open to input from anyone who rotates into the role. This will help you continue to fine-tune your processes.

Tasks to be performed by the person assuming the Service Coordinator / Tech on Call For The Day role:

1/ When you are "on point" for the day, you will be monitoring the Service Board and updating it at least every hour.

2/ Take over the phones. This means that you will catch incoming calls. The actual process for this will vary depending on your phone system.

Remember, the Coordinator role is there to accept new requests from clients but you are not there to answer billing or service related questions. If that happens, simply explain to the client your role is there to take down the issue and then enter it into the system. For further questions please refer the client to management. 

Also remember: This is not a "help-desk" position. The Coordinator is not authorized to answer the phone and start solving the client's problem. Nothing in this position eliminates the need to enter service requests into the PSA system, prioritize them and work them from highest to lowest priority and from oldest to newest. Tickets have to get into the system; but we are not interrupt-driven (LINK) with regard to work priorities. 

It is helpful to give this person a call script so they know what to say under various circumstances. Don’t throw them in and hope they can swim!

3/ You will be managing the outsourced monitoring and help desk (RMM / back office) and therefore need to be the designated coordinator in their system. Log into their system and make this change, or call them to notify them. In general, follow whatever process they need.

4/ You are in charge of letting the remote monitoring service know when we are doing maintenance on a server that would require either downtime or reboots. Use the message board and post a message accordingly. Again, follow their process.

5/ Perform the daily monitoring duties.

6/ Process the new Service Requests that come into the system. 

7/ Work on Priority 4 Service Tickets. This is one way we make sure that the P4 tickets get attention. You need to be interruptible enough to take phone calls and perform all the little tasks above. Working low-priority tickets is a perfect combination as you can switch tasks fairly easily.

8/ Unless the Service Manager has a reason to do otherwise, you will work service tickets that involve working with line-of-business tech support, shadowing them as they access client machines and generally making their support work as successfully as possible. Ideally, this work is scheduled at a specific time. And since our primary responsibility is simply to monitor the vendor's access, it fits well with the coordinator role.

9/ As higher-level tickets enter the system, you will coordinate with technicians to make sure that they are working on the highest-level, oldest tickets in the queue. If technicians are scheduled to be out at client offices, you will keep track of who is where and how they will proceed through their day. Sometimes, jobs are finished faster than expected. At other times, they drag on longer than expected. The "coordinator" piece of this job is to balance all the resources (people) available to you against tickets that need attention.

In general, the Service Coordinator will help to move tickets through the system. In a perfect world, this role would not be needed because the process of prioritizing tickets and then working them from highest to lowest priority and from oldest to newest will always keep everyone doing exactly what they should be. But since you are also dealing with human beings, there is a good portion of "art" in addition to the science of managing tickets. 

Implementation notes 

First, you need to define the specific duties to be performed by the Tech on Call for The Day. These will be some subset of duties already being performed by one or more people. In fact, it may include some things that should be getting done but aren't. Write out the duties in a manner similar to the list above. 

Second, you need to determine a rotation schedule. Who will rotate through this role? How often will you rotate? Will the service manager or owner be on the rotation list? 

Third, once you've written out the duties and rotation, you need to do some training. All the technicians should be familiar with the basic tasks required for this position. But very often, we don't pay close attention to the details of jobs that are not our own. So they might know the broad outline but not the details of performing the tasks. Training of some kind is in order. 

Fourth, set a schedule and begin the rotation. Do some debriefing after one day, three days, and one week. Accept lots of feedback, give lots of feedback, and fine-tune the process in response to the realities of your business. 

Benefits of having a Tech on Call for the Day

The most obvious benefit is that this process is an evolutionary stage as your business moves from one-tier to a multi-level service department. It is a good way to transition to having a full-time service coordinator, but it allows you to see how each technician will do without making permanent changes.

The rotation will also increase the efficiency of your team as each technician learns a higher level of detail about the flow of tickets through the system and the fine points of service coordination. Setting priorities, coordinating schedules, and working with clients. When everyone on the team has a higher level of understanding of these functions, they will all be better at supporting and reinforcing one another. That takes your team and your service delivery to the next level.

Three key take-aways from this blog:

  1. We often pay no attention to the details of a job that is not our own. Rotating the Coordinator position will help everyone learn these tasks.
  2. The Service Coordinator is the most interruptible person on the tech team. But even they can’t be too interruptible.
  3. When you start this process, you’ll need to help and monitor each tech as they learn the tasks in this role. It’s harder than it looks!

(Used with permission of Karl W. Palachuk,