Company Chat

A lot of the desk now runs through chat, and it goes every direction. A user messages you on Teams or Slack for help, and you turn that into a ticket and sort them out from there. You message users back for the detail you need, you ask a colleague when you are stuck, and you pull in another department when a ticket needs rights or knowledge you do not have. People outside the company reach you through a chat widget on a ServiceNow or Zendesk portal. For a lot of desks the first contact on most tickets is somebody typing one line into a box.

It looks like the easy channel. On a call you hear the hesitation, you hear the sigh when you ask them to restart it again, and you know they are still on the line. In a chat you have a cursor and a gap, and the person on the other end is answering you between two meetings.

Microsoft Teams is a trademark of Microsoft Corporation. ServiceDesk Simulator is not affiliated with, endorsed by, or sponsored by them.

Response time is what you are measured on here. Most desks set an expectation for the first reply, and a user who gets "on it, give me ten minutes while I check the mail server" at minute one will wait happily. A user who gets a perfect answer at minute twelve, with silence before it, has already messaged your manager.

"Still looking into this" every few minutes is the only evidence the user has that the thread is alive, and it costs you four seconds.

The most common way a new tech wrecks a chat is to open with everything at once. What is the exact error, when did it start, does it happen on your laptop too, have you restarted, what is your asset tag. Five questions get one answer back, usually the easiest one, and now you are guessing which.

Ask the single question whose answer cuts the problem in half, then stop typing. "Does it happen on webmail as well" splits a mail fault into the account or the device. "Is anyone else on your floor seeing it" splits a network fault into one machine or one switch. Either answer halves the work, and you asked for four words.

That second one is a scope question, and it is one of four questions that together separate what somebody reports from what is actually wrong, before you have diagnosed any of it. They are the same four in every channel and they are worked through in Voicemails, where a message is all you get and every follow-up waits for a callback.

A closed question has a small set of answers: yes, no, a number, one of two things. An open question asks somebody to describe. Both are right at different moments, and the moment decides which.

Open with the closed question that halves the problem, then keep going closed, and spend an open question only where a one-word answer would tell you nothing. And get the error message with your own eyes. "It says something about a certificate" gives you a category; the string itself, character for character, gives you the fault. Ask them to type it out exactly or send a picture of it.

Leading question

"It is not unplugged, is it?" People agree to be helpful, and you have just confirmed something nobody checked.

Double question

"Is it plugged in and does the light come on?" You get one answer and never learn which half it was about.

Assume nothing about what is in front of them until they have told you. They are on a phone, or a different version, or a screen that has been redesigned since the last time you saw it.

"Send me a screenshot" is often the fastest diagnostic instruction on the desk. It ends the argument about what the error says, it shows you the version of the screen they are genuinely looking at, and it usually carries something they never mentioned: the wrong account in the corner, an offline marker, a sync icon spinning since Tuesday.

Ask the moment a description goes vague. Say how to take one on the device they are holding, and ask for the whole screen, because the part they think matters is a guess. On anything with personal data in it, mind what else is in the frame: a screenshot with somebody else's record open sits in the ticket forever.

Raise the ticket while the conversation is still running, paste the error string into it exactly as they sent it, and close on a line the user can read back later: what you changed, and what to do if it returns.

That closing line is the chat version of the read-back a call ends on. On the phone it is said out loud and confirmed before the line drops, which is why The phone drills it. In a thread you type it once and it is still there a week later.

"That is not possible" is true and useless. "Here is what we can do" is the same fact with a next step attached, and it costs nothing to type.

Match the person's register and stay level under their panic. Somebody firing short blunt lines wants the same back, and somebody writing in paragraphs wants a sentence that shows you read it. When they arrive in capital letters, say what you are doing right now and when you will come back. Apologize once, for the thing that actually happened.

All of it runs through one panel, Company Chat, opened from the speech-bubble icon in the top bar. Two different conversations run inside it, and both are typed into the same box at the bottom, the one that says Type a message....

The second ask on the same ticket sends you to the documentation on purpose: the job is working a fault out from what is written down. Come back having read it, or having put it to the team first, and he answers straight, which is what a real team lead does too.

Ask your IT team when you are stuck. The ticket itself closes only from the chat with the person who raised it, because that thread is where the engine reads your fix from.

Left column is this panel. Right column is the real thing it stands in for, under the name the industry uses.

Two things about that control before you go looking. A Start video call sits beside it on the same threads, doing the same job with a camera. Both are Pro: on a free account pressing either opens the upgrade prompt, so read the rest of this page as what the escalation looks like.

Start voice call appears on a chat with one employee: the people who raise tickets and the coworkers beside them. The company channel, your IT team and every tech in it are chat only.

Verifying who you are talking to belongs to Directory, and the chat here assumes it. On a real desk the thread is where that happens, in writing.

A company-wide channel sits pinned above both, and during an outage that is where the announcement goes. Put an estimated time in it: a post carrying one resolves the outage tickets sitting open behind it, and a post missing one earns you a nudge to go back and add it. Everything else in there is broadcast: written to the room, answered by whoever feels like answering.