Return to...
Interaction with clients
As a member of the EASI Web Team, interacting with clients is one of the most important aspects of our work. As a support team, people only reach out to us when they need some form of help, and it is important to recognize the impact our words, tone, and how they are perceived have on faculty, staff, and students across the University.
This training will cover a few topics through providing in-depth examples, demonstrating the concept as a whole, then by contextualizing it to situations you might encounter during support tickets in ServiceNow or assisting someone in person during the Open Lab.
Word Choice
Overview and example
For any communication you use, the words you choose to convey your thoughts matter. Of course, this sounds obvious– but all too often, just a few words’ difference in a sentence can provide a very different meaning to a listener or reader. For example, perhaps a supervisor was checking in with their team lead on a project they have been working on that has been rather stressful, and approaches them with one of the following:
- What’s the status on the TablePress project?
- How are you doing with the TablePress project?
Although the baseline goal of both options is the same (figuring out how work is coming along on the TablePress project), they are asking different questions. Option 1 is approaching the goal by asking for a direct response; the answer here is just the current state of the project. Option 2 is asking about the team lead’s perception of the project; bringing in their perspective and their opinion on the work, during which the state will likely come across.
It is important to note– neither of these options is better than the other, or even generally preferred. Each form has their time and place, depending on factors like:
- the dynamic between the team lead and the supervisor
- If the two have only recently started working together, option 2 might seem too forward– whereas if the two have been working together for quite some time and have a friendly dynamic, option 1 might come across as a bit cold.
- where the conversation happens
- In a scheduled check-in meeting, with the project on the agenda, option 2 gives time for the team lead to expand upon their thoughts and perspective. In an unexpected stop by their desk, however, potentially in the midst of working on this task or another, the direct approach of option 1 allows for a quick response and enables both parties to get back to their work quickly.
There are many more factors that affect how a conversation can go, and stopping to think about each of them before going into one would be exhausting– the goal here is not to require every conversation be planned down to the second. However, it is to prompt you to think before any important conversation. When approaching a colleague, a client, or a supervisor with a specific goal, thinking quickly about the situation and how that might affect your word choice gives you much better odds of that conversation going well.
How does this affect me?
This comes into play most directly when responding to support tickets, as it is our team’s most common form of communication. Often, you’ll be responding to people you don’t know, and all you know about their current situation is what the ticket says– which isn’t much. So what can you do? Write carefully, and lean on professional language. Any insights you get can be used to help you from there, but using polite and professional words is always the safe place to start. To demonstrate, we’ll look at an example message, along with a default professional response, then an example of how to tweak that response to fit what information is present.
Example Ticket Accordion Closed
Good afternoon,
I recently completed the WordPress training, and got access to my department’s website. I tried to make a new image callout shortcode on the homepage, but I cannot get it to link to the page I want it to. Can you help me?
Regards,
Client
Example Responses Accordion Closed
This is a pretty straightforward ticket– the client has explained the context (working on the homepage for the first, or nearly first time), the element they have an issue with (the image callout shortcode), and the specific problem they are having (it will not link). In addition, it does not really exhibit any particular hints about how the client is feeling, being straight to the point. Let’s look at the basic response, polite and similarly to the point:
“Good afternoon,
Thank you for reaching out to us. We have step-by-step instructions and examples of our shortcodes on our website, and you can find the image callout documentation here: https://in.nau.edu/web/image-callout/. Please follow the steps on this page, and let me know if it still does not link after.
Regards,
Pub”
This basic response ticks all the boxes: polite greeting, pointing the client to the resource rather than just fixing it for them, and encouraging follow-up if the issue persists.
However, there is an opportunity to do more than just tick the boxes; the difference between good support staff and great support staff is in what comes beyond just solving the problem. Take a look at the response below:
“Good afternoon,
I’m sorry to hear about the trouble the image callout is causing you. After looking at the page, I think this is because the link is showing up after the image, rather than on it, and the shortcode can’t process it. Can you remove the link there, and then try adding the hyperlink after clicking on the image? That should get it to appear properly.
If it helps, here is a link to our documentation on the image callout shortcode: https://in.nau.edu/web/image-callout/
Our site has pages like that for all of our shortcodes, including step-by-step instructions and some troubleshooting for common issues.
Tone
Overview and example
Alongside word choice, the other major component of effective communication is the tone you use when conveying your message. In normal conversation, it is not often noticed– unless it seems wrong. There are many ways to say the exact same words, and the tone used with them is often what conveys the speaker’s true intentions; responding to an invitation to attend a gathering with “I’d love to go” sounds very different in an excited tone versus a flat monotone, for example, demonstrating the difference between someone who is looking forward to the event as opposed to someone who would rather not attend if at all possible.
For communicating with clients, tone is incredibly important, as it is often perceived as a direct representation of one’s attitude– and sending the wrong message can turn even positive clients into angry ones. Because of this, many people who work in jobs that require a lot of interaction with the public develop what is referred to colloquially as a “customer service voice”, a specific tone that is polite, upbeat, and calm, that is intended to be as inoffensive as possible. This generally works rather well, and is worth cultivating, but is only one tool in our toolbox, especially given how much of our communication occurs through text– no matter how well you speak, the person reading an email will not hear your voice when they get your message. How do we ensure our intentions are clear using written communication? Almost paradoxically, it comes down to your word choice. Unlike the spoken form of tone, where the vocal inflection weighs far more than words on the message’s meaning, the lack of inflection in an email means the words, as they are, are everything. To illustrate this, we’ll look at a few examples of phrases that might work in spoken support, but could cause problems in written support, and how they could be phrased to reflect the tone originally intended.
Example Question Accordion Closed
Good morning,
I’ve been working on my site, but no matter what I do, the content I’m trying to put into the right sidebar is appearing at the bottom of the page. Can you help me figure out what I’m doing wrong?
Regards,
Client
Example Responses Accordion Closed
“Good morning,
Thank you for reaching out– I’m sorry to hear you’re having trouble with the right sidebar. Have you checked out our documentation? You can find it at: https://in.nau.edu/web/styleguide/right-column/
If you still need help after that, let me know and I can investigate further.
Regards,
Pub”
In a setting like our open lab, where this response could be spoken with a sympathetic and positive tone, a response like this could work fine. It is acknowledging the user’s struggle, and providing the specific resource that can help them get what they need. However, without the spoken tone, this phrasing could come across potentially condescending. The phrase “you’re having trouble” without the verbal cushion, can be taken as an implication that their struggles are a result of their own failures– and even if that is true, it is not something people ever like to hear.
In addition, the closing also reads pretty insensitive without the benefit of an upbeat voice and a smile to go with it– “If you still need help after that” could imply yet again that the client is the source of any issue, and if the documentation does not help them solve the issue it is likely a more technical problem.
“Good morning,
Thank you for reaching out about the right sidebar issue– I’d be happy to help you get it the way you want it. Have you already checked out our documentation? We have troubleshooting for common issues and helpful tips. You can find it here: https://in.nau.edu/web/styleguide/right-column/
If that doesn’t have the answers you’re looking for, let me know and I can investigate further to make sure this is working for you.
Regards,
Pub”
With this response, the problem is acknowledged, but not focused on– it quickly moves into how the Pub is ready to help solve it. By expanding slightly on the documentation as to what it provides, it makes it clear for the clients as to how it will help them solve the issue, and the closing stresses the goal of the message is to get the client what they need. It carries a lot of the positive intent the spoken version would, all in text, and that is exactly what we are aiming for.