|
|
|
If you're having that issue and its costing you money then you need to bring it up with your manager and find a solution. It's not a technology issue.
It is a technology issue because the IT department took away a perfectly good phone and replaced it with an over-complicated system that is unreliable.
Was it perfectly good from IT's perspective, did they just change the phone system for the fun of it? Was it in warranty? Did the vendor still support it?
If you think anything in IT will remain static then you're going to have a bad time.
We are about to migrate to Teams Phone (Operator Connect).
Doing away with all desk phones. They just aren't used any more.
Hopefully it goes OK, there will be some that just don't like change, but most won't even notice I suspect.
I'm not a fan of ditching dedicated handsets. They are a relatively simple appliance like a toaster that just works.
We have clients who have physical handsets on their desks and we almost never get calls with support issues. One larger client has phones on only 1/3 of desks and the softphone-only users have been less happy with the solution, and wifi issues when working from home has resulted in negative feedback for mobile app softphone users. We use the same back end setup everywhere.
I use my softphone 90% of the time. Lifting my headset off its dock answers the call whether my computer is locked or unlocked. Before I got the headset integration working, hunting for my softphone on my busy desktop caused much frustration. If my computer uptime is 10+ days sometimes the softphone misbehaves and I grab my desk handset instead. The physical act of answering the phone by lifting something is (in my opinion) more efficient, even though there is an expense to it.
“Don't believe anything you read on the net. Except this. Well, including this, I suppose.” Douglas Adams
alasta:
It is a technology issue because the IT department took away a perfectly good phone and replaced it with an over-complicated system that is unreliable.
There's so much behind that statement that it'd take a day to write the response. It should suffice to say you have clearly got no context for the how or why the "perfectly good phone" was taken away. It's not always IT leading initiatives like this, regardless of whether it's a technology solution or not. Instead of blaming IT, if you want to lay blame, lay it on the steering committee that would have made all the key decisions and provided all the approvals and funding to do the work. I get pretty sick of IT getting short shrift and blamed for everything under the sun, when in reality any project is a business project, regardless of the technology involved. IT people don't just wake up one day and say to themselves "I'm going to piss off every employee today by taking away a tool they use to do their job". There would have been context behind the decision, as mentioned earlier, probably license costs, support costs, end of life hardware, so on and so on and so on until the cows come home. Your org has clearly made a conscious decision that the risk of Teams going down is not high enough value to warrant supplying a 2nd means of communication to their staff. In that case I would expect my staff to just wait until Teams is back, given we've made that conscious decision that we can tolerate some loss of productivity if it happens. But there's no point talking to IT about it, business decisions come from business stakeholders and sponsors.
elpenguino: ... The last time it happened at work, I walked upstairs and had a nice chat to my help desk colleague, told him why I couldn't call, ...
I'm happy for you that your Help desk colleagues are only a flight or two of stairs away instead of 2-4 time zones. 😎
Please keep this GZ community vibrant by contributing in a constructive & respectful manner.
alasta:
It is a technology issue because the IT department took away a perfectly good phone and replaced it with an over-complicated system that is unreliable.
Yeah, the current state of IT in general sadly.
You're best bet - if you're able and it's feasible, is to take matters into your own hands. If you want it done right - just do it yourself.
IT folks are usually helpful if they see you trying to make things easier for them. There is a fair bit of groupthink, and an unfortunate degree of power-of-authority styled approach (one has to earn some street cred first).
For things like IP phones, just start from first principles and work your way from there.
PABX systems need to be replaced, upgraded and maintained, whereas teams is a managed service. It might be that it saved a heck of a lot of money to move to teams.
trig42:
We are about to migrate to Teams Phone (Operator Connect).
Doing away with all desk phones. They just aren't used any more.
Hopefully it goes OK, there will be some that just don't like change, but most won't even notice I suspect.
I migrated from Skype on prem to Teams OC last month, most of the business handed back their desk phones as they were never used. So we just have a few shared phones in cafes etc left.
|
|
|