I don’t really have a typical day, as my role at Supreme gets me involved in a vast array of technologies, all over the country, but an average day is typically like the following:
9:00. First job of the day, while the morning kettle is boiling, is to check my e-mail. IT Support tickets logged overnight will send me an e-mail automatically, and of course I have to check through my standard e-mail in case a customer has informed me directly about an issue. Meanwhile, the first line engineers will be checking through their e-mail as well, looking at the automatically generated logs from the servers we support, looking for any issues and flagging them up for attention. So if a backup fails for example, this is when we will pick it up. Assuming that there is nothing that requires our urgent attention, the next thing the technical team does is to go through any open support tickets together, and prioritize any outstanding work. At this point I know roughly the work I’m going to be doing that day, and I can plan around it.
10:00. It’s more likely than not that I’ll have some sort of scheduled meeting that day, and I prefer to do this in the morning when I can, in case I get tied up in technical work later in the day. This can be anything that requires a representative of the technical team to talk to an existing or prospective customer. Often I’ll attend sales meetings, to make sure anything discussed is correct from a technical side. Considering how many people don’t like meetings, I have to admit I enjoy these. I rarely lead the meetings, but I’m often called upon to explain various technologies, and the advantages and disadvantages of different ways of doing things. I’m a sociable person who loves talking about technology, so that suits me just fine.
12:00. Lunchtime. Unless there is something causing severe problems for a customer, in which case we’ll likely be working right through. Fortunately, the non-technical staff here our kind enough to go out and fetch us some nutrition (Nothing that can mess up a keyboard!) if we’re working right through. I learnt early in IT support you shouldn’t skip lunch entirely. You need your brain, and you don’t think as well if you’re hungry.
13:00. If it’s a good day, then we should have had any problems reported today sorted out by now, and our decks are clear. Much as I’d love to put my feet up and bask in the glory of an empty help-desk queue, we can’t get away with that. I.T. moves fast, and our customers are always looking for something new. So often this time is used to carry out research on the part of customers, such as choosing a good CRM system, or planning ways of providing extra features that have been requested. Failing that, we’re training. We bank on our engineers being skilled, so learning has to be a continuous process.
If it’s a less good day, on the other hand, then we’ll be working on technical problems, either on going ones or newly reported that afternoon. We want our customers systems to give us as little trouble as possible, so we try to make sure the fixes we make are solid, and problems will not re-occur. But despite that, sometimes we’ll have a run of issues. So everyone pitches in, and if you have to stay late…Well, I knew that when I got into I.T. My wife knew it was coming when she married me!
17:00. Normally this is when I aim to finish. But I could be on a customer site in another city, so it doesn’t bear much relation as to when I get home. And often there’ll be some “homework”. A server reset to do outside of hours, or a user who isn’t available till late this whole week. These tend to be “courtesy” jobs however, occasional work for the convenience of our customers. We’ve set ourselves up to work wherever we have an internet connection, which feels like a mixed blessing sometimes!
I hope this gave you an insight as to how I work – don’t forget if you need any on-going IT support to call the team on 0800 001 5942 or simply email firstname.lastname@example.org
Also if you liked the article why not follow me on or like us on Facebook?