{"id":4669,"date":"2019-02-19T12:53:20","date_gmt":"2019-02-19T17:53:20","guid":{"rendered":"http:\/\/lisa.rushworth.us\/?p=4669"},"modified":"2026-05-15T14:39:45","modified_gmt":"2026-05-15T19:39:45","slug":"did-you-know-you-can-use-teams-as-a-support-channel","status":"publish","type":"post","link":"https:\/\/www.rushworth.us\/lisa\/?p=4669","title":{"rendered":"Did you know \u2026 you can use Teams as a support channel?"},"content":{"rendered":"

To be honest, I wasn\u2019t sure this was true until we tried it. But my group is promoting Teams usage within the company, so it made sense to try<\/em> using Teams as a tool for users to engage support. I don\u2019t mean technically<\/em> work \u2013 anything where someone can report an issue & someone else can read\/respond to the issue can be used as a support channel! Smoke signals and carrier pigeons would technically<\/em> work. I mean \u2018you can use Teams as a support channel without subjecting yourself to rampant chaos, long wait times, and irritated participants.\u2019<\/p>\n

What did we do? Some employees transitioned to a new company under a divestiture. While the individuals would be terminated in PeopleSoft (i.e. we\u2019re not going to keep paying them), they needed to retain access to many systems during a transition period. Since terminating an employee in PeopleSoft automatically terminates their Active Directory and LDAP accounts (a great thing from a security perspective), these individuals needed to be changed to temporary IDs. Coordinating account changes for fifty people is an undertaking, and the actual conversions were spread across a full day. After their account is converted, each individual needs to perform a series of steps to get their computer and applications functioning with their new ID. And problems occur.<\/p>\n

I built a Teams space for the transitioning employees and support staff who would be assisting with the account conversions. End-user documentation and the schedule of whose account is being converted when was stored in the Teams space. On the account conversion day, we had a bridge open and<\/em> used a Teams channel for issue reporting.<\/p>\n

What happened? Well, first I\u2019ll tell you what didn\u2019t<\/em> happen. The Teams channel didn\u2019t become a confusing mess of issue reports that became onerous to manage. Now I\u2019m not saying I want to replace user tickets with a bunch of public Teams spaces you can join when you\u2019ve got an issue \u2026 but in a limited and controlled environment, Teams was a great supplement that allowed us to better support the transitioning individuals.<\/p>\n

People who had never used Teams before didn\u2019t<\/em> find it difficult (although they also had the bridge-line as a backup) \u2013 they used the https:\/\/teams.microsoft.com<\/a> URL, signed in, and were quickly able to chat with the support team.<\/p>\n

When issues were reported, support staff could quickly reply to indicate they were looking at the issue. And unlike a bridge call, three people can easily type<\/em> at the same time. As a support person, I clicked the little bookmark to \u2018save\u2019 an issue on which I was working.<\/p>\n

<\/p>\n

Typing \/saved<\/strong> into the command bar at the top of my Teams client<\/p>\n

<\/p>\n

Provided quick access to threads on which I was working. When multiple issues are reported to a bridge line, I find myself with a Notepad document with who and what.<\/p>\n

<\/p>\n

When the problem was a misunderstanding of or a gap in the documentation, I was able to update the end user documentation directly in Teams. These updates were immediately available to users.<\/p>\n

Individual chat and screen sharing within Teams \u2013 without having to ask someone how to spell their name three times \u2013 was an enormous help in walking users through reconfiguration tasks. Where I\u2019ve used Skype for this before, telling someone who<\/em> I am so they could chat or share their screen with me was time consuming. And I had to tell a LOT of people.<\/p>\n

In Teams, you can use the \u201cmeet now\u201d button at the bottom of the channel discussion to start an ad hoc meeting that anyone can join.<\/p>\n

<\/p>\n

Or hover your mouse over the individual\u2019s avatar on their post and click the \u201cChat\u201d icon to start an individual chat.<\/p>\n

<\/p>\n

From within the individual chat, the individual needing assistance could use the sharing control to share their screen.<\/p>\n

<\/p>\n

And they could even give keyboard\/mouse control to support staff.<\/p>\n

<\/p>\n

But the best thing about using Teams as a support channel? Participants read channel posts, followed previously-provided instructions, and sorted their own problem.<\/p>\n

And in the days following the account conversion? I left the Teams space open for anyone who encountered a problem. Leaving the Team open means support staff can keep an eye on the channel without dedicating a lot of time to waiting to see if problems arise.<\/p>\n

The one thing that would have made the experience even better \u2013 pinning posts to the top of the channel<\/a>. It would have been great to pin the three process updates where everyone could find them instead of relying on participants to read through the entire channel history.<\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

To be honest, I wasn\u2019t sure this was true until we tried it. But my group is promoting Teams usage within the company, so it made sense to try using Teams as a tool for users to engage support. I don\u2019t mean technically work \u2013 anything where someone can report an issue & someone else …<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[677],"tags":[675,691,729,666,686],"class_list":["post-4669","post","type-post","status-publish","format-standard","hentry","category-office-365","tag-did-you-know","tag-microsoft-office","tag-microsoft-office-365","tag-microsoft-teams","tag-ms-teams"],"_links":{"self":[{"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/posts\/4669","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=4669"}],"version-history":[{"count":3,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/posts\/4669\/revisions"}],"predecessor-version":[{"id":12264,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/posts\/4669\/revisions\/12264"}],"wp:attachment":[{"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=4669"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=4669"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=4669"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}