Microsoft Teams Integration with ServiceDesk Plus

ManageEngine
21 Dec 202016:43

Summary

TLDRThis tutorial demonstrates how to integrate ManageEngine's Service Test Plus with Microsoft Teams, enhancing collaboration and support. It covers prerequisites like a valid HTTPS domain and access roles in Service Test Plus and Azure. The video guides users through setting up the integration in Service Test Plus, configuring bots in Microsoft Teams, and updating necessary information in Azure. It also shows how to set up the request tab in Teams, add commands, and distribute the app across the organization. Viewers learn to execute bot commands, initiate chats with technicians, and manage service requests directly from Teams.

Takeaways

  • πŸ”— The video demonstrates how to integrate Service Test Plus with Microsoft Teams, allowing users to use Teams as an additional channel for IT and enterprise support.
  • πŸ†• Microsoft Teams integration with Service Test Plus was introduced in version 1.20, so users should ensure they are updated with the latest releases.
  • πŸ”’ Prerequisites for integration include hosting Service Test Plus on a domain with a valid certificate, accessible via HTTPS, and possibly using Azure's application proxy for public access.
  • πŸ‘€ Roles required for setup include Service Test Plus SD Admin Console, Azure Global Administrator, Teams Administrator, and Azure Applications Administrator.
  • πŸ”§ The integration process involves configuring Service Test Plus, Microsoft Teams (desktop or web app), and the Azure portal.
  • πŸ“„ The integration setup requires three key pieces of information, detailed in the help card and documentation provided by Service Test Plus.
  • πŸ€– The video guides through setting up a bot in Microsoft Teams, which involves naming the bot, enabling file upload/download support, and creating the bot within Teams.
  • πŸ”‘ It's necessary to generate an application password for the bot in Microsoft Teams and update this password in Service Test Plus for authentication.
  • 🌐 The video explains how to obtain the Application ID and Tenant ID from Azure, which are crucial for completing the integration setup in Service Test Plus.
  • πŸ”„ The process includes configuring redirect URLs in Azure for authentication between the Teams app and the bot, and setting API permissions to allow Service Test Plus to access Microsoft's identity platform.
  • πŸ“ The video also covers optional configurations like setting up command shortcuts in Teams to simplify user interactions and updating the app details in Service Test Plus for instance identification.
  • πŸ’¬ The integration enables chat functionality between end users and technicians through Microsoft Teams, with the ability to create service requests directly from the chat.

Q & A

  • What is the purpose of integrating Service Test Plus with Microsoft Teams?

    -The purpose of integrating Service Test Plus with Microsoft Teams is to leverage Microsoft Teams as an additional channel for IT and enterprise support, allowing users to manage and collaborate on service requests within the Teams platform.

  • Which version of Service Test Plus introduced the Microsoft Teams integration?

    -The Microsoft Teams integration with Service Test Plus was introduced in version 1.20.

  • What are the prerequisites for integrating Service Test Plus with Microsoft Teams?

    -The prerequisites for the integration include ensuring that Service Test Plus is hosted on a domain with a valid certificate, using HTTPS protocol, and is publicly accessible. Alternatively, the application proxy feature in Azure can be used to host Service Test Plus publicly.

  • What roles are required to set up the Microsoft Teams integration for Service Test Plus?

    -To set up the integration, access is required to Service Test Plus SD admin console, Azure as a Global Administrator or Teams Administrator, and Azure Applications Administrator.

  • What information is needed to configure the Microsoft Teams integration in Service Test Plus?

    -The integration requires three key pieces of information: Application ID, Tenant ID, and a generated Application Password.

  • How can the necessary information for the integration be obtained?

    -The necessary information can be obtained by following the integration documentation provided by Service Test Plus, which includes details on prerequisites, rulesets, and steps for configuration.

  • What is the role of App Studio in the integration process?

    -App Studio in Microsoft Teams is used to import an existing app, configure the bot, and set up the manifest for the Service Test Plus integration.

  • Why is the Application ID and Tenant ID required from Azure for the integration?

    -The Application ID and Tenant ID from Azure are required to register the Service Test Plus app with Microsoft and to configure the necessary permissions and authentication settings for the integration.

  • How does the configuration of the request tab view in Microsoft Teams enhance the user experience?

    -Configuring the request tab view in Microsoft Teams enhances the user experience by providing a single console within Teams where users can view and manage service requests from Service Test Plus.

  • What optional configurations can be set up to improve user interaction with the Service Test Plus bot in Microsoft Teams?

    -Optional configurations include setting up commands that allow users to interact with the Service Test Plus bot using shorter commands, thus improving efficiency and user interaction.

  • How can users initiate a chat with a technician from within Microsoft Teams after the integration?

    -Users can initiate a chat with a technician by executing the '/chat' command within Microsoft Teams, which communicates with Service Test Plus and establishes a chat session.

Outlines

00:00

πŸ”— Introduction to Integrating Service Test Plus with Microsoft Teams

This paragraph introduces the video's purpose, which is to guide viewers through the integration of Manage Engine's Service Test Plus with Microsoft Teams. The integration allows users to use Microsoft Teams as a channel for IT and enterprise support. The video emphasizes the need to keep Service Test Plus updated and outlines the prerequisites for integration, such as having a valid certificate, HTTPS protocol, and public accessibility. It also mentions the required roles for setting up the integration, including Service Test Plus SD Admin Console, Azure Global Administrator, Teams Administrator, and Azure Applications Administrator.

05:00

πŸ›  Setting Up Microsoft Teams Integration

The paragraph details the steps for setting up the Microsoft Teams integration with Service Test Plus. It begins with logging into the Service Test Plus admin console and accessing the integrations section, specifically for Microsoft Teams. The integration requires three key pieces of information, which are elaborated in the provided documentation. The viewer is guided to log into Microsoft Teams, navigate to App Studio, and import an existing app using a provided ZIP file from the documentation. The paragraph explains the process of configuring the bot within the app, including naming it, enabling file upload/download capabilities, and creating the bot within Microsoft Teams.

10:01

πŸ”‘ Registering App and Configuring Azure

This section continues the integration process by focusing on registering the app with Microsoft and configuring it in Azure. It involves copying the Application ID and Tenant ID from Azure and updating them in Service Test Plus. The paragraph also covers the generation of a new application password in Microsoft Teams and its subsequent update in Service Test Plus. The viewer is instructed to add a redirect URL in Azure for authentication between the Teams app and the bot. Furthermore, it explains how to configure API permissions in Azure to allow Service Test Plus to access Microsoft's identity platform API, which is necessary for fetching and updating user information.

15:05

πŸ“ Configuring Request Tab and Bot Commands in Microsoft Teams

The paragraph discusses the configuration of the request tab view in Microsoft Teams, which is an optional step to enhance user experience by reducing the need to type full commands. It guides the viewer to add new commands and configure the app details with the App ID generated during the bot creation. The configuration is tested and distributed within the organization by downloading a Service Desk zip file and uploading it as a custom app in Microsoft Teams. The paragraph concludes with a demonstration of executing commands to view all requests and initiating chats with technicians, showcasing the integrated functionality between Microsoft Teams and Service Test Plus.

πŸ’¬ Chat and Request View Integration

This final paragraph demonstrates the chat feature within Microsoft Teams, which serves as a collaborative platform for communication between users and technicians. It shows how users can initiate a chat, discuss issues, and have those discussions reflected in Service Test Plus. Additionally, it highlights the request view feature, which consolidates request-based operations from Service Test Plus into a single console within Microsoft Teams. The paragraph concludes by showing how updates made in Teams, such as adding notes or closing a ticket, are immediately reflected in Service Test Plus, emphasizing the seamless integration and collaboration facilitated by the platform.

Mindmap

Keywords

πŸ’‘ManageEngine ServiceTest Plus

ManageEngine ServiceTest Plus is a software testing tool designed to automate the testing of IT services. In the context of the video, it is the primary subject being discussed, particularly its integration with Microsoft Teams. The video aims to educate viewers on how to leverage this integration for enhanced IT service management and support within an organization.

πŸ’‘Microsoft Teams

Microsoft Teams is a platform that combines workplace chat, video meetings, file storage, and application integration. The video script describes how ServiceTest Plus can be integrated with Microsoft Teams to provide an additional channel for IT and enterprise support, showcasing the collaboration capabilities of Teams in a service management context.

πŸ’‘Integration

Integration in this video refers to the process of combining different software systems to work together. The main theme revolves around integrating ServiceTest Plus with Microsoft Teams, which allows for a more streamlined workflow and communication between IT support teams and users within the organization.

πŸ’‘Azure

Azure is Microsoft's cloud computing service that offers a range of cloud services, including virtual machines, cloud storage, and application hosting. The video mentions using Azure's application proxy feature to host ServiceTest Plus publicly and accessing the Azure portal to configure the integration settings, demonstrating Azure's role in facilitating the integration process.

πŸ’‘ServiceTest Plus Admin Console

The ServiceTest Plus Admin Console is the administrative interface for managing the ServiceTest Plus application. The video script instructs viewers on logging into this console to perform the integration with Microsoft Teams, highlighting its importance in the setup and management of the ServiceTest Plus environment.

πŸ’‘App Studio

App Studio is a feature within Microsoft Teams that allows users to create and manage custom applications. The video script guides viewers through using App Studio to import and configure the ServiceTest Plus app within Teams, showcasing how App Studio simplifies the process of custom app development and deployment.

πŸ’‘Manifest Editor

The Manifest Editor is a tool within App Studio used to edit the manifest file of a Teams app. The manifest file contains essential information about the app, such as its name, description, and permissions. The video script mentions using the Manifest Editor to import an existing ServiceTest Plus app, indicating its use in the customization and configuration of the app.

πŸ’‘Bots

Bots in the context of the video refer to automated software agents that can interact with users within Microsoft Teams. The script describes configuring a bot named 'ServiceTest Plus' to enable file uploading and downloading, illustrating how bots can be used to enhance functionality and user interaction within Teams.

πŸ’‘API Permissions

API Permissions refer to the access rights granted to an application to use specific APIs. In the video, configuring API permissions in Azure is discussed as a necessary step to allow ServiceTest Plus to access Microsoft's identity platform API, which is crucial for fetching and updating user information within the service management process.

πŸ’‘Request Tab

The Request Tab in Microsoft Teams is a customizable section within a Teams channel that can display specific content or applications. The video script details how to configure the Request Tab to display ServiceTest Plus information, demonstrating how Teams can be tailored to provide quick access to service management functionalities.

πŸ’‘Chat Feature

The chat feature in Microsoft Teams allows for real-time communication between users. The video script explains how this feature can be used to initiate and manage chats between end-users and technicians within ServiceTest Plus, highlighting the collaborative aspect of Teams in an IT support setting.

Highlights

Introduction to integrating Service Test Plus with Microsoft Teams for enhanced collaboration.

Service Test Plus integration with Microsoft Teams was introduced in version 1.20.

Prerequisites for integration include a valid certificate and public accessibility for Service Test Plus.

Access to Service Test Plus SD admin console, Azure, and Microsoft Teams is required for integration.

Detailed documentation provides prerequisites, rules, and steps for the integration process.

Instructions on how to log into Service Test Plus and access the Microsoft Teams integration settings.

The integration process requires only three pieces of information, outlined in the help card.

Demonstration of logging into Microsoft Teams and navigating to App Studio for integration setup.

Importing the Service Test Plus app from a zip file into Microsoft Teams App Studio.

Explanation of configuring bots in Microsoft Teams and registering the app with Microsoft.

Instructions for generating a new password for the bot and updating it in Service Test Plus.

Accessing Azure to obtain the application ID and tenant ID for integration.

Adding the redirect URL from Service Test Plus to Microsoft Azure for authentication.

Configuring API permissions in Azure to allow Service Test Plus to access Microsoft's identity platform.

Updating the bot endpoint in Microsoft Teams to complete the integration setup.

Configuring the request tab view in Microsoft Teams for Service Test Plus.

Optional configuration to prevent users from typing full commands, streamlining the user experience.

Setting up the Service Test Plus app for the entire organization in Microsoft Teams.

Testing the integration by executing commands and viewing supported operations in Microsoft Teams.

Demonstration of initiating and ending a chat between Microsoft Teams and Service Test Plus.

Accessing the request view in Microsoft Teams to perform request-based operations.

Real-time reflection of updates made in Microsoft Teams to the Service Test Plus application.

Transcripts

play00:00

thank you for downloading manage engine

play00:02

service test plus

play00:03

in this video we are going to learn how

play00:05

to integrate service test plus with

play00:07

microsoft teams

play00:08

using this integration users can

play00:10

leverage the collaboration app from

play00:12

microsoft teams

play00:13

as an additional channel for it and

play00:15

enterprise support

play00:17

microsoft teams integration with service

play00:19

test plus was introduced in version

play00:21

120 so please ensure you stay updated

play00:24

with all our releases

play00:26

now before we proceed with the

play00:27

integration let's take a look at the

play00:29

prerequisites required for the

play00:31

integration

play00:32

make sure your service test plus is

play00:33

hosted on a domain with valid

play00:35

certificate

play00:36

with https protocol and is accessible

play00:39

publicly

play00:40

you can also use the application proxy

play00:42

feature in azure to host your services

play00:44

plus publicly

play00:46

what are the rules that's required to

play00:48

set up microsoft teams integration

play00:51

you will be working on the integration

play00:52

setup of service test plus

play00:54

microsoft teams desktop or web app and

play00:56

your azure portal

play00:58

make sure you have access to all the

play01:00

following areas in the following roles

play01:03

service test plus sd admin console azure

play01:06

global administrator or

play01:08

teams administrator and azure

play01:10

applications administrator

play01:12

now that we have understood the

play01:14

prerequisites and the rules that's

play01:16

required

play01:16

let's log into service test plus and

play01:18

perform the integration

play01:20

log into service test plus admin console

play01:23

and

play01:24

under integrations you will have

play01:26

microsoft teams

play01:28

the team's integration and service test

play01:30

class requires only three piece of

play01:31

information

play01:32

and right below is the help card where

play01:36

we are going to have detailed

play01:37

information on

play01:38

where we could get the free piece of

play01:40

information and how it could be

play01:41

configured

play01:42

so click on the integrations

play01:45

documentation that we have

play01:47

and here is the documentation the

play01:50

documentation has the prerequisites the

play01:52

rule sets required

play01:53

and the steps that needs to be performed

play01:56

so

play01:56

log into teams.microsoft.com once you've

play02:00

logged into teams.microsoft.com

play02:02

head on to apps and look for app studio

play02:08

click on app studio click on open

play02:10

[Music]

play02:13

now if this is the first time you're

play02:15

clicking on app studio you'll get an

play02:16

option to add

play02:18

if it is already added just click on

play02:20

open head to manifest

play02:21

editor and click on import an existing

play02:24

app now where do we get this app from

play02:28

head to the documentation and

play02:31

right underneath where we add the app

play02:35

here we have mock-up service test plus

play02:37

zip

play02:38

file click on it to download the file

play02:41

once the file is downloaded head back to

play02:43

microsoft teams

play02:45

click on import an existing app so here

play02:48

is the app

play02:49

file that i've just downloaded click on

play02:51

it

play02:52

open it now as we've just imported the

play02:55

file the file has been imported

play02:58

in this file we have packaged

play03:00

information such as the application name

play03:03

description version developer

play03:05

information

play03:06

icons and other basic information to

play03:08

ease the configuration process

play03:11

now that we have imported this app

play03:14

the next step we have to configure is

play03:17

the bots

play03:18

so right under this particular app

play03:21

as we could see the icon the name is

play03:24

already pre-populated

play03:25

i'm just gonna access box and i'm gonna

play03:28

click on

play03:28

setup under this particular console

play03:32

i'm going to name the bot as service

play03:34

test plus

play03:35

i'm going to enable the option my bot

play03:37

supports uploading and downloading files

play03:40

and the scope is personal and i click on

play03:42

create a bot

play03:44

here when i click on create the bot here

play03:46

this is where we are registering the app

play03:48

with microsoft

play03:49

and the configurations are further

play03:51

continued in azure

play03:53

so once i've imported the bot i get

play03:56

the app id for the bot and this app

play04:00

id i have to use it right into my

play04:03

teams integration service test plus but

play04:06

i would also require the tenant id and

play04:08

the application password

play04:09

so what i'm gonna do right now is i'm

play04:12

gonna head to microsoft teams

play04:15

and over here i'm gonna click on

play04:16

generate new password

play04:18

i'm gonna copy this password

play04:22

and paste the same password into service

play04:24

test plus

play04:25

now i've copied the password that is

play04:28

generated

play04:29

from my bot and i've updated the same

play04:31

into service test plus

play04:32

i add on back to microsoft themes and

play04:35

click on

play04:36

ok now what's next

play04:40

let's head on to azure to access the

play04:43

application id and the tenant id

play04:46

so right in the documentation we have

play04:49

the link to access the azure portal

play04:51

click on the link and you'll have access

play04:53

to azure portal

play04:56

so once i access azure through the link

play04:58

from the documentation

play05:00

it takes me right into the bot that i've

play05:02

just created

play05:04

click on the particular service and over

play05:07

here you get access to the application

play05:09

id and the tenant id

play05:12

copy the application id from azure

play05:14

update the same

play05:15

right into service test plus likewise

play05:18

copy the tenant id

play05:20

and update the same tenant id into

play05:22

service test plus

play05:24

click on save once we click on save we

play05:27

get couple of other information that is

play05:28

required

play05:29

we have the redirect url and the bot

play05:31

endpoint

play05:32

now we need to transfer this redirect

play05:35

url into microsoft

play05:36

azure so click on copy in service test

play05:40

plus

play05:41

under azure you have redirect urls

play05:45

click on add redirect url click on add a

play05:48

platform

play05:49

web and paste the redirect url over here

play05:53

and make sure you enable id tokens

play05:57

after pasting the redirect url the

play06:00

redirect url is required for

play06:02

authentication between

play06:03

the teams app and the bot so once you

play06:07

have provided all this information

play06:09

click on configure now once the redirect

play06:13

url is added

play06:14

we need to configure the permissions for

play06:16

the bot

play06:17

how do we do that so right into azure i

play06:20

have access to

play06:21

api permissions i click on that and i'm

play06:25

going to click on

play06:26

add permission once i've done that i

play06:30

click on microsoft graph

play06:32

i click on delegate permission

play06:36

and over here i'm just going to click on

play06:38

open

play06:39

id this step is to allow service desk

play06:42

plus

play06:43

to access microsoft's identity platform

play06:46

api so that we fetch basic information

play06:50

about the users

play06:51

and to update the microsoft user's

play06:54

information into

play06:55

service desk database so after enabling

play06:58

this particular option

play07:00

i click on add permissions

play07:03

now that we have configured the api

play07:06

permissions

play07:07

in azure we have to copy

play07:11

the endpoint url from service test plus

play07:15

and update the same into microsoft teams

play07:18

so i copy the bot endpoint

play07:22

and i'm going to access microsoft teams

play07:25

so all the configuration that we are

play07:28

performing in

play07:29

teams is right underneath the service

play07:31

test plus bot

play07:33

all right so all you have to do is just

play07:36

paste

play07:36

the bot endpoint that you have

play07:38

configured from

play07:39

service test plus now the part endpoint

play07:42

is being updated

play07:44

now that we have integrated service test

play07:46

plus with teams and have registered the

play07:48

part with microsoft

play07:50

we are now going to configure the

play07:51

request tab view in microsoft teams

play07:54

let's take a look at what is required to

play07:56

configure the same

play07:58

we have not navigated to any other

play08:00

segment so all you have to do is

play08:02

click on tabs right underneath the

play08:05

capabilities

play08:06

and under add a personal tag click on

play08:08

add tab

play08:10

now what are the information that is

play08:12

required and where would i get the

play08:13

complete details

play08:15

so i access the documentation and right

play08:18

into the documentation is where i have

play08:21

all the details on how to add the

play08:23

request tab

play08:25

now the important information is that

play08:27

while adding i need to provide the

play08:29

name the entity id as how it is

play08:32

displayed

play08:33

so let's go ahead and add the same into

play08:36

microsoft teams

play08:37

i provide the name

play08:42

i provide the entity id now we need to

play08:45

copy

play08:45

and update the content url and the

play08:47

website url

play08:49

which is nothing but your service

play08:51

testplus url where

play08:53

it is hosted now i'm gonna update my

play08:55

service test plus url on both these

play08:57

segments

play08:58

and once after i've done that there are

play09:01

a couple of other

play09:02

content that i need to upend into this

play09:04

particular url

play09:05

so right into the documentation i have

play09:07

the url that i need to

play09:09

update so for the content url i'm just

play09:11

going to copy this highlighted segment

play09:13

paste the same right into my content url

play09:17

likewise for website url i'm copying

play09:20

the content that is required and the

play09:23

content i just copied from the

play09:24

documentation i'm updating it into

play09:27

microsoft teams i click on save so with

play09:30

this we have now configured the

play09:32

request tab for microsoft teams

play09:35

once the request tab is configured i'm

play09:37

going to perform

play09:38

optional configuration this is to

play09:40

prevent the users from typing the whole

play09:42

command

play09:43

you can use this optional configuration

play09:45

to do this

play09:46

so right under capabilities i access

play09:49

bots in microsoft teams

play09:51

and over here i have comments i click on

play09:54

add

play09:55

and i'm going to execute the comment to

play09:58

know what needs to be executed over

play10:00

there

play10:00

the information is again provided in

play10:03

your

play10:04

admin guide

play10:05

[Music]

play10:07

so here is how you add the new command

play10:10

so referring the steps

play10:11

i'm just gonna provide the details over

play10:13

here

play10:15

the help desk information and i click

play10:17

choose the scope as personal

play10:19

and i click on save now once after i've

play10:23

added the commands

play10:24

the other important information that i

play10:26

need to configure is that

play10:28

i need to update this particular app id

play10:31

that was

play10:31

generated the moment we created this bot

play10:34

into the app details so i'm just going

play10:36

to copy this

play10:38

and right under app details i'm just

play10:41

going to

play10:42

paste that information over here why do

play10:45

we do this

play10:47

this is basically to ensure that this

play10:50

particular configuration

play10:51

is for the specific instance of service

play10:54

test plus

play10:55

now if i'm going to have more than one

play10:57

instance of service test plus

play10:59

to verify which is the corresponding

play11:02

instance

play11:03

we need to provide the app id over here

play11:05

so by default we have a prefixed app id

play11:08

but it is suggested to append the app id

play11:11

with

play11:11

what we have received when we have

play11:13

created the bot

play11:15

now that these steps are configured

play11:17

let's move on to the next configuration

play11:19

now that we have appended the app id we

play11:22

are now going to set up the service test

play11:23

plus app for the

play11:24

entire organization so let's see how we

play11:27

do

play11:28

that and what is required to do the same

play11:30

head on to the teams app

play11:32

and we are still under the service test

play11:34

plus app

play11:35

so at the very bottom we have this

play11:37

option that's called test and distribute

play11:40

click on test and distribute and click

play11:42

on download

play11:45

so this has now downloaded a service

play11:47

disk zip file

play11:49

navigate to the app segment on the left

play11:51

hand side panel on microsoft teams

play11:54

scroll to the bottom click on upload a

play11:56

custom app

play11:58

choose upload for sdp bot and choose the

play12:01

corresponding

play12:02

app that we have just downloaded

play12:04

[Music]

play12:07

once you have uploaded the app the app

play12:09

has now been updated right into

play12:11

microsoft themes so once after i have

play12:14

uploaded the app

play12:15

i get an option to sign into microsoft

play12:18

account

play12:19

once i click on it i just have to

play12:21

consent

play12:22

and i click on accept once after i've

play12:26

accepted it

play12:27

the authorization is completed

play12:28

successfully and i can perform

play12:30

all my operations that is required from

play12:33

my microsoft teams

play12:40

now i can execute commands just to see

play12:42

what are all the supported operations

play12:44

that i could perform

play12:46

also to know what are all the supported

play12:48

bot commands

play12:49

access the help documentation and you

play12:51

get all the information in one place

play12:54

i can perform commands like view all

play12:56

requests

play12:57

i get to see all my tickets

play13:00

so right from my team's app i can view

play13:03

all the tickets

play13:04

also if i have more than one instance of

play13:07

service test plus

play13:08

i can just use the command slash select

play13:10

instance and i get access to the

play13:12

instance

play13:13

so apart from these supported bot

play13:15

commands

play13:16

the end users can also initiate a chat

play13:18

with the technician

play13:20

and can end the chat we're now going to

play13:22

take a quick look at how the chat works

play13:24

between microsoft teams and

play13:26

service desk plus

play13:27

[Music]

play13:29

in microsoft teams i execute the command

play13:32

slash chat

play13:33

and this command has now communicated

play13:36

service desk plus and has got me in

play13:37

response

play13:38

now i head to service test plus and the

play13:41

technician can

play13:42

see the chat from linda they can pick up

play13:44

the chat and

play13:45

establish communication with the user

play13:51

now that in microsoft teams the users

play13:54

can view the chat communication from

play13:57

service test plus

play13:58

right from within microsoft teams the

play14:00

end user can further communicate

play14:02

with the technician by saying

play14:08

i need a new software and this

play14:10

communication happens for a while

play14:12

and the technician can say i will

play14:15

initiate

play14:16

[Music]

play14:18

a service request

play14:24

so once done

play14:25

[Music]

play14:28

back at teams the user can say

play14:31

thank you and use the slash command to

play14:34

end chat

play14:35

this way the end user can initiate a

play14:38

chat with the technician using microsoft

play14:40

teams

play14:41

and end the chat back in service desk

play14:43

plus

play14:44

the technician can create a new ticket

play14:46

and as said

play14:47

the technician can create a service

play14:49

ticket choose the template

play14:51

and perform the request creation process

play15:04

[Music]

play15:07

now we have seen how the chat feature

play15:10

within microsoft teams serve as a

play15:12

collaborative platform

play15:14

to communicate with users now right from

play15:17

within microsoft teams

play15:18

we are going to access the request view

play15:21

using this request view

play15:23

we can bring in all the request-based

play15:25

operations from service test plus into

play15:28

one console within the teams

play15:30

now i have couple of my open requests

play15:32

being listed over here

play15:34

and i can go ahead and perform

play15:36

operations

play15:37

such as adding notes or closing a ticket

play15:40

and

play15:40

all these changes will immediately

play15:43

reflect into my

play15:44

service testers application so over here

play15:48

let me refresh this particular request

play15:50

and as you can see

play15:51

the status of this request which i have

play15:54

updated in teams

play15:55

is now reflected into service test plus

play16:00

likewise not just requests status

play16:02

changes or request based operations

play16:05

any conversations adding of notes will

play16:08

also be

play16:09

reflected right into my team's app

play16:13

so i've added a note on service test

play16:15

plus and if i look into the teams app

play16:18

i will have the notes reflected right

play16:21

underneath my

play16:22

ticket we have now understood how

play16:24

service test plus

play16:25

integrates with microsoft teams and how

play16:27

it performs a platform for collaboration

play16:30

as well as a single console where users

play16:33

can chat

play16:34

and also use the request view

Rate This
β˜…
β˜…
β˜…
β˜…
β˜…

5.0 / 5 (0 votes)

Related Tags
Service Test PlusMicrosoft TeamsIntegration GuideIT SupportCollaborationAzure PortalApp StudioBot ConfigurationAPI PermissionsRequest Tab