I’d like to share with you a recent customer service interaction I experienced. My father just turned—let’s say a significant age—and I wanted to get him something special. When I was home last August, I spotted three old sheriff’s badges mounted artfully in a shadow box in one of our favorite shops. (My dad is a cowboy trapped in a CPA’s body.) Since it had been the better part of a year since I had been there I wasn’t sure if it was still available. I called the store a couple of weeks ago to inquire, and the woman, Sarah, assured me she had enough stock for me to figure out whether I should ship it or if my aunt could pick it up.
The day before the big birthday, I called Sarah back to purchase. She had already pulled the best one from stock and held it for me, and she didn’t even know exactly when my dad’s birthday was. We completed the credit card transaction when she offered to wrap it for me and have it ready in an hour for my aunt to pick up. In all, we spent over 5 minutes on the phone making small-talk, laughing, and figuring out that Sarah used to work with my parents at the resort where they had their coffee shop! My dad loved the gift, was completely surprised I remembered it from last summer, and was impressed I coordinated the exchange from 800 miles away.
I believe that excellent customer service principles translate across all business, so I can adapt this example from retail to our work in IT at Fandotech:
A new feature of our website is “Dear Sarah” where you can email me questions or comments related to IT and customer service. I encourage you to contact me to introduce yourself if we haven’t corresponded yet, share ideas about how I, along with the rest of the Fandotech team, can make your experience better, or what kinds of information would be useful for me to share in the column. As for Tampico in Leland, MI I think I need to have a conversation with Sarah about having us create and host their website and e-commerce so I can order what I want online any time of day…
Sarah C. Marino
Hello. My name is Sarah Marino, and I don’t have an IT background. In fact, I don’t have advanced knowledge of special applications, I can’t tell you how to get rid of viruses on your computer, and I don’t spend my spare time gaming or reading about computers and networks. Until a few weeks ago, I thought a NetApp was the one appetizer left over from a party. Nevertheless, I feel I help fill an important role here at Fandotech.
My official title is “Dispatch and Ticket Management,” which means I schedule all the field work , including coordinating projects with the project managers, and I follow up on service tickets worked on by the Technical Assistance Center (TAC) and field technicians. Before I continue, I have to qualify what I am going to say: the Fandotech team is filled with smart, talented, amazing people who have the ability to solve every problem I’ve thrown at them on behalf of our customers. However, sometimes with exceptional knowledge and expertise in an area, common sense can be taken for granted. There’s that classic urban myth/anecdote about the 18-wheeler that gets stuck in a tunnel and all these engineers, the fire department, and the police can’t figure out a way to remove it until a little girl (in my anecdote it’s a girl) in a passing car suggests letting the air out of the tires. At Fandotech, I’d like to think that I, along with a handful of others, occasionally help let the air out of the tires.

Jack Bauer, 24, Copyright Twentieth Century Fox
I work very closely with the TAC every day and help determine the escalation path for service tickets for managed service customers. So, when one of the technicians mentions he can’t solve an issue remotely and it needs to be escalated to a field technician, I start asking questions: Is it just this user experiencing slowness when opening Outlook or is it the whole office? When did it start? Jack Bauer was onsite last week—have you called him for assistance? Sometimes my questions don’t help get an immediate solution because the technician has already dutifully asked them or they are extremely basic, but every once in a while they will spark a new train of thought that ultimately leads to a quicker resolution.
The fact that I interface with all the departments and both locations at Fandotech is advantageous to the team. Sometimes I hear information in one meeting that is useful to people in another, and I try to pass that along even if it seems unrelated. When I hear the technicians and engineers talking about challenging issues, most of it goes over my head. Instead I try to think what the customer would ask if they could hear the conversation—could my network connectivity problems in one location be related to the circuit in the other? What could be going on between 12pm and 1pm that makes my server spontaneously restart every 4th day? We have many customers who are much more technically-savvy than I who ask incredibly detailed questions, and I try to take as many notes as possible and ask as many follow-up questions as I can think of. I never know if any of that information, even the smallest detail, might be useful to the team. Sometimes I won’t know the right follow-up questions to ask, but hopefully I will the next time thanks to my handy technicians.
For some people, simply talking about the problem and trying to put it in plain English, for people like me, is part of their problem-solving process. Answering my questions or explaining the resolution to me may help the technicians get their language customer-ready. And sometimes,when I tell them to take a mental break or that it’s okay to ask someone else for help, that’s just what they need to hear to get to a solution. Hey, anything I can do to help!
Perhaps I don’t have any technical certifications and I can’t customize my own Linux server for home use, but I do have at least one valuable asset in common with our technical team—curiosity. And if my curiosity and desire to get a problem resolved for a customer ends up helping the team in some small way, I’ve done my non-IT job.
Sarah C. Marino
Content Management Systems (CMS) make it easy for non-technical people to update a website, to control who can see which web pages (or portions of web pages), and to allow a much more interactive website experience by supporting discussion groups, blogs, wikis, e-Commerce, simple data entry forms, and more.
Whenever we start talking with a potential client about their desire for a new or improved website presence, the first technical decisions are whether to build the website using a Content Management System. Based on our experience, we’ve developed some indicators to help guide our clients to decide when it makes sense and when it doesn’t.
The following indicators suggest a solution that does not require a CMS:
The following indicators suggest a solution where a CMS may be insufficient to meet your needs:
Brad Hurley