During a French Team meeting I felt like the communication between presenter and attendees could only go one way. I'm sure this was not intended like this, but due to the growth of the team, to the training and to the Knowledge Transition, I sensed that we could not afford to waste that precious meeting hour on various topics. This would be more a thing to do with people you spend several hours per day together.
I raised the following questions in hope of consolidating our experience on the job and adopt a coherent behavior.
Some questions are older and are answered already. I think it doesn't hurt to repeat it once more, on a written format.
Would be awesome to get a spreadsheet with all the OSS Queues that support which site and in which language.
Current workaround:
*OS2
or *OSS
We have a Distribution List! In fact, we have many of them. Just try and type neo
in the To: field of Outlook or Skype search.
We could update the information for (TS-EMEA-L1-SD1 SERVICE DESK GMT A1) to contain the Group email address. This way it wouldn't send an email to hundreds people, but to one Distribution List only.
Sorting by Language would be a dream.
There are CIs that have the same Name, but different Class. This is not visible if you don't open the Search box. Should we always chose the one that a has Class 'Service Offering'?
Two parameters to pay attention: Language and Location.
We are supporting countries that are within the regions of Europe (except FR), North America and France. No APAC or AEME.
We are allowed to support only with the selected language, or guide the user in English to contact the right Service.
Resolved Incidents are still Active until they are Closed, after X days.
Resolved Active Incidents can be Re-Opened.
Inactive Incidents need a new Call.
How should we use the TS-EMEA-L1-SD BACKLOG group? Assign there everything that wasn't resolved in 1 day?
When to create a New Call?
Create a new ITS Call as soon as
Call type | Action |
---|---|
Incident |
Image Not Showing
Possible Reasons
|
Request |
Image Not Showing
Possible Reasons
|
Status Call |
Image Not Showing
Possible Reasons
|
Hang Up |
Image Not Showing
Possible Reasons
|
Wrong Number |
Image Not Showing
Possible Reasons
|
General Inquiry |
Image Not Showing
Possible Reasons
|
It's Friday and you have the early shift that ends at 4 PM.
At 4:30 PM you just receive a ticket In Progress on your name.
Clock is ticking.
On Monday you have the late shift, starting at 12 PM, with a ticket in Progress for 3 days.
When the user is answering the Pending ticket during the night, it goes In Progress but doesn't show up in my queue until a specific time. (1:13 PM?) How to behave for a better SLA?
Most are really hard to use. Basically, everything except the intro. I don't want the user to think I'm an Artificial Intelligence. And I know how to apologize and thank appropriately.
Is that idea not dead yet? Is that really the future?
UxApp: I really don't want to know what an Indian Chessmaster is doing during COVID-19. And I'm not a Yoga type of guy. There is no way to stop these notifications from inside the App. Oh wait! I'm interested in the Hackathon. But that is restricted. Still receiving the notification though.
Authenticator: Provided code is displayed only for the current minute. If you requested your code at 11:24:56, you have 4 seconds to enter it, then request a new one. Request your code at 11:24:02 and it will be valid for 58 seconds. Except if you messed up in Ultimatix, then you need a new code, requestable only after the whole minute has passed.
Timesheet: Daily? Why? Am I not getting paid if I don't? What about weekly, or monthly? I'm not getting paid every day. If this is a mandatory application, make a training or a guide for it. And don't implement features if they are not working, like the Copy one.
Should I continue in English with a user that clearly is speaking the Local Lang? Or should I warn the user that the ticket should be reassigned to English support if the comments are not provided in Local Lang?
How to behave with users having 2 languages set in SNOW? ('I am confortable speaking X') Should we only take in consideration the first one? Or should we stick to the Lang used in the ticket?
Or should I say Citrix alternative? Actually, it is the very specific combination of Skype within Citrix that bothers me quite a lot.
Citrix is useful to browse the Intranet and access tools from the Shared Folder (GUEST & GUEST-ADM) but the most used tools are working from outside as well (Cloud Contact, Service-Now, Office E3).
Skype for Business is lighter and faster than Microsoft Teams, but it will be replaced soon and we will face issues that will get an impact on the Availability. I also don't think it is good to have the same channel to be contacted by users or colleagues. These should be different ones. At 9 AM, I always have a scare jump from the Good Morning
SCTASK2494185 assigned to my name, but I can't remember receiving training about SC Task. Also I don't know where to check when one is assigned to me.
HackMD is a collaborative document-editing in Markdown. Markdown is a simple and easy-to-use markup language you can use to format documents. But the spotlight goes on the collaborative part. Where DropBox, Google Drive, even Personal OneDrive are forbidden on the network due to their File Sharing nature, HackMD is only hosting text documents. This can be used for Quick Guides sharing (e.g. How to log a ticket) or complete together a check list or share some tips and tricks. Please check some features below.
Markdown Guide if you are interested to write pretty stuff: https://www.markdownguide.org/
HasteBin alternative of PasteBin for quick notes, clipboard or code sharing: https://hastebin.com/
Where to find information about shifts? For yourself, or for a colleague?
Might be interesting to know how many agents are covering the line at a certain time or if someone is having a day-off.
At my previous workplace, we were only allowed to call users in between 10 AM and 4 PM (local time) to avoid disturbing them and a better management with the incoming calls. Is there any similar rule?
Related to Call management comes immediately into my mind that we should always know who is on the line, ready to catch the next call, if there are calls waiting in the queue. I saw these informations are provided by BT, but please make it possible to share this via Internal Link for example. Current workaround is to use the button "Make Call" on BT and search manually all colleagues.
Would also be great to have it for the Neo Chat. Current workaround is to add the Neo ServiceDesk Distribution List to your Contacts in Skype.
Fresco will be replaced by OneDrive and SharePoint soon. Why not take the initiative to already migrate all documents there and start using it. Already copied what was possible from the Network Drive of Budapest. And sharing information with cool presentation is relatively easy too.
Also would be great to have at least one File Sharing platform in the exception list for when documents need to be sent to new joiners (without Ultimatix account yet).
Office License is an E3, which means that we can connect to Office Web Apps on any device. Teams should be available easily from any browser and should be used as main professional communication channel.
If you are not constantly working on the VDI, you should modify your Skype settings to avoid the Inactive Status. If you don't move the mouse inside the VDI, you'll go Inactive on Skype, which will cause 2 bad situations:
To avoid that, go into your Skype Settings and modify Change Status to Inactive/Away after something like 60 minutes.
This goes by pair with the CMS, but if we know that someone is missing from the line we will be more careful to secure the incoming calls and not go on break at the same time. The say when you are back, so that other people can take their Lunch/Short Break too.
I have created for myself few SNOW Filters that allow me to see:
This way I can see when a colleague has a ticket in pending for longer and I can try to help. Or if user just commented back that Incident is resolved, I can just close the ticket instead of an SLA Breach.
See the advantages of the behaviors above and tell me which you'd rather adopt:
Individualism behavior where things are shared equaly and everyone has it's own share of work, no less, no more.
Teamwork behavior where tickets are always being checked by different agents that are currently available to help reduce the backlog and react much faster than a colleague that just finished his shift.
If you are inviting someone on meeting in Outlook, please mind to set the Availability to Free.
If you are invited by someone on meeting in Outlook, please mind to check you Skype Status and think about the Neo Chats.
As said earlier, I have few Filters. Are you interested?
Also worth noting that the New SNOW Dashboards doesn't have the interesting feature of Self-Refreshing itself after a period of time. Your Homepage does. Set your Homepage.
CCNG, PST, OST, GUEST, OSS, CMS, SD, SSD, SSF, CC, SA, SJML, ITS, PFA, KR, BR, BTW, ETC…
I think it's pretty cool to know why some file extensions are called like that.
Also office jargon/slang can be used more effectively with colleagues for a faster communication IYKWIM.
We could store some of them that are specific for us, but I recommend checking the words above with the links below FYI.
https://www.abbreviations.com
https://acronyms.thefreedictionary.com
In theory, I think we can set Skype to go in Status "Off-Work" automatically at the end of your shift. Also go Available at the begining. Never late again! Except it's still a work in progress. See below one of my attempt:
Outlook Work Day for better Skype for Business management
(https://outlook.office.com/calendar/options/calendar/view > Meeting hours)
I'm a guy who like scripts. They do repetitive tasks for you, without efforts. I'm not the best at it, I'm currently learning a lot, but if you have any idea, I would enjoy a cooperation. What I learned, is that Windows Shortcut Links can act like a command. And if you queue several commands, you have a script! By the way, when you open your Active Directory with your PAM account, that's a script that you run. And the good news is that I have a better one for you. What about double-clicking that icon and have it open as Admin with typing anything? What login to BT as soon as your computer is logged in? I have more, but I'd like to get your feedback on that.
Here some of my scripts:
It's a bit different than the one you have on local machine. No biggy, but if that bothers you check that:
Show all folders (View > Folder Pane > Normal)
Insert Zscaler rant. Tired of typing about it. My heart is sad.
Might not be the same as you. Might be more complicated, might be easier.
I might also be tired of writing all this at the moment, but you'll get it. Eventually. I just think that's important to share our workflow.
Honestly, there never was anyone who requested to be called in the middle of the night. I never experienced a Priority ticket yet. And I'm not sure how to check wich tickets are SLA Breached. Result: the file is forever empty.
Round 2: Canada! Why do we have to send a separate empty file for Canada too?
And then I sent the links to check the numbers directly with the correct filter. I think that's more reliable than sending an email with potential human errors. But that's just me.
I got a French guy from France on the phone once. Didn't check the queue/skill on BT. But he was the head of something. He gave me a bunch of ticket numbers that got escalations for France and told me that all of the topics were already discussed during the KT. That was confusing…
I have the answer now: don't touch French stuff, only redirect them to call ComputaCenter. At least until the Cut Over.
I think I had to make screenshots for the first FR Meeting, but now I see the MoM are sent by email. That's really cool. Especially if I couldn't pay attention whenever I got a Call/Chat and I could re-read it afterwards. Should we save them online too (Fresco/SharePoint)?
Agent Name | CALL Opened by | INC Opened by | INC Assigned to |
---|---|---|---|
Dhia Jebabli | 40 | 32 | 21 |
Ghazoua Jberi | 16 | 14 | 3 |
Marwa BenAbdallah | 5 | 4 | 3 |
Micheal Dima | 71 | 65 | 63 |
Qemal Affagnon | 56 | 32 | 18 |
Something is wrong. I would like to talk about it.
The points above are mainly reflecting issues that happens on every teams. To justificate that FR Team is performing worse I have to show different issues that are not happening in other teams.
I suggest as a solution to allocate some time in a weekly Team Meeting dedicated to handling the line. Checking the settings of the tools and sharing experiences and tips. Promoting communication.
To all, thanks for reading! And hope to see your comments. MikaWed, Jun 17, 2020 5:22 PM