Teams
Last updated
Last updated
Tous droits réservés @ 2023 dydu.
To create a bot on Teams that will be connected to your dydu bot, follow these steps:
Azure Portal: Create a configuration and set up the connection between this configuration and dydu. The operations to be performed in this section are:
Create a resource group
Create an Azure bot
Configure Microsoft credentials
Connect the resource group to the Azure bot
dydu BMS Channels Menu: Configure your dydu bot, choose the consultation space and language
Create a Teams configuration
Download the bot application
Teams: Publish your configuration
Publish the bot in Teams
Sign in to the Azure Portal.
Select "Resource Groups"
In the Resource Groups page, click Create button
Fill the following values:
Subscription: Select your Azure subscription
Resource group: Enter a new resource group name.
Region: Select an Azure location
Click on Review + create button
Select Create. It takes a few seconds to create a resource group.
The resource group list is refreshed
Then, return to the home page.
Select Bot services
Click on Create
Look for Azure Bot in the Bot Services list.
Click on Load more at the bottom of the page if Azure Bot is not displayed on first page.
Then, click on Azure Bot.
Click on Create.
Fill the required information:
Bot Descriptor: The name of your Teams bot. It can be modified later via Azure. The bot descriptor can only contain the following characters: a-z, A-Z, 0-9, -, and _, must start with a letter or number, and must be between 4 and 42 characters long.
Subscription: Choose Azure CSP
Resource Groups: Select the resource group you created earlier
Application Type: Select "Multi-tenant"
Then, click on Review + Create button.
Wait a few seconds. Then you can see this page:
Click on Create button.
Click on Go to resource button
Click on configuration in the left menu
Here you can find your Microsoft App ID:
Click on Manage to create the Microsoft App password in Certificates
Click on New client secret
Fill in the required information:
Description: a description of the client
Expiration date: select “24 months”
Click on the Add button
Important: Copy the value of the client secret and save this value since later you will not be able to see.
Go back to the home page and open your created bot.
Click on Channels in the left menu and click on the Microsoft Teams icon.
Accept the Terms of Use and click on Save.
Click on Configuration in the left menu to configure the connector endpoint and fill in the Messaging endpoint field. Check the Enable streaming endpoint box. You can find the endpoint on the first configuration page of Teams under Channels.
Example for a SaaS server - app1:
Click on Apply.
Connect to the BMS.
Then go to Integration > Channels.
Clic on “Create”.
Select "Microsoft Teams"
Give it a name, click on the Teams icon to select it, and then click on "Create."
Choose the consultation space and the language that your Teams chatbot will use.
Click on "Next".
Enter the Microsoft App ID and the clientSecret that you previously copied from MS Azure and fill in the various elements of your bot's presentation in Teams.
Bot descriptions
These are the descriptions displayed for your bot within Teams.
These fields are mandatory.
The short description must not exceed 80 characters and must not be repeated in the full description.
The full description must not exceed 4000 characters.
Bot names
This is the name displayed to designate your bot within Teams.
The "short name" field is mandatory and must not exceed 30 characters.
The "long name" field is not mandatory, you can use it if the chosen name exceeds 30 characters. It must not exceed 100 characters.
Bot avatar
Your bot in Teams must have two icons:
the main avatar of the bot and
it must respect a dimension of 32*32 pixels and can be in colour
the icon of the application (which appears in the sidebar of Teams
it must respect a dimension of 192 x 192 pixels and must be transparent
The accepted format for these icons is PNG.
Name of the bot's author
This is the name of the bot creator. This is a required field that must not exceed 30 characters.
These are the urls :
Website
Privacy policy
Terms of use
The urls are required.
They are displayed in the "About" tab within your bot Teams
Enable knowledge triggering on negative feedback
Trigger knowledge in case of one or more misunderstandings.
Display the technical welcome in the conversation:
Allows displaying the #teamswelcome# which must be configured in the BMS and will trigger at the beginning of the conversation.
During the third and final step "Download":
Click on the "Download" button. Save the ZIP file and click on "Finish".
Note: If the required fields are not filled out, you will not be able to download the ZIP configuration file for your bot application.
Click on "Finish".
Go on Teams.
Click on Apps at the bottom left corner of your screen.
Click on Manage your applications at the bottom left of your screen.
Click on the Submit an application to your organisation button
This will take you to the page listing the different applications you have submitted to your organisation. Click again on Submit an application.
Select the ZIP configuration you saved before.
Your application is now listed under pending requests.
Once approved by your administrator, you can find your application in the app catalog designed for your organization. You may need to restart Teams to see the application appear in the catalog. To open your organization's app catalog, click on "Designed for your organization" at the top of the list in the left menu.
Click on the application you created.
Then click on the "Add" button.
You can start the dialog with your bot.
The following tables show the supported and unsupported features for a dydu bot under MS Teams.
Supported = The functionality is available and works as part of a dydu bot in MS Teams
Unsupported = The functionality cannot be implemented for a dydu bot in MS Teams
Formatting the response
Feature | Support | Comment |
---|---|---|
"Heading" tag | Supported | |
Bold | Supported | |
Italic | Supported | |
Underline | Supported | |
Text color | Supported | |
Text background color | Supported | |
Text alignment | Supported | |
Indentation | Supported | |
Ordered list | Supported | Bullets are not displayed but the list hierarchy is respected and displayed |
Non ordered list | Supported | Scheduling numbers/letters are not displayed but the list hierarchy is respected and displayed |
Link to an external URL | Supported | |
Link to knowledge (reword) | Supported | |
Display a table | Supported | |
Split bubble | Supported | |
Images / File from the gallery | Supported | |
Smiley | Supported | |
Using mathematical expressions | Unsupported | |
Display a side panel | Supported |
Features available for response
Feature | Support | Comment |
---|---|---|
Step actions | Supported | |
Alternative answers | Supported | |
Use a variable in an answer | Supported | |
Automatically redirected to an external URL | Unsupported | |
Automatically redirected to a knowledge | Supported | |
Display a template | Unsupported | |
Use a GUI action | Unsupported | |
Make an automatic switch of consultation space | Unsupported | 1 bot Teams = 1 language, 1 consultation space |
Modify the value of a variable before action | Supported | |
Modify the value of a variable after action | Supported | |
Requesting user satisfaction | Unsupported |
General sentences
Feature | Support | Comment |
---|---|---|
Response to misunderstood sentences | Supported | |
Too many misunderstood sentences | Supported | |
Answer to long sentences | Unsupported | |
Answer to empty sentences | Supported | |
Click on the links | Unsupported | |
Links open in new windows | Unsupported | |
Response to unpublished knowledge | Supported | |
Default response when action is empty | Supported | |
The answer is available in the default language | Unsupported | |
The answer is not defined for this consultation space | Supported | |
The answer is available from another consultation space | Unsupported | |
Refocusing sentence | Supported | |
Internal error response | Supported | |
Introduction of rewording | Supported | The rewords are displayed listed AND in buttons. Only buttons are clickable. Buttons contain the title of the knowledge. |
General suggestion for reformulations | Supported | The text defined in the general suggestion must be the same as the title of the knowledge to which this general suggestion redirects. |
Knowledges type
Feature | Support |
---|---|
Simple knowledge | Supported |
Decision tree | Supported |
Complementary answer | Supported |
Internaut activity | Unsupported |
Slot filling | Supported |
Other
Feature | Support |
---|---|
Capture user intent | Supported |
Use a context condition | Supported |
Metabot | Supported |
Using a WS | Supported |
SAML | Supported |
Features specific to the dydu chatbox
Feature | Support | Comment |
---|---|---|
Welcome sentence | Supported | |
Information banner | Unsupported | |
Top knowledge | Unsupported | |
Autosuggestion | Unsupported | |
Disclaimer GDPR | Unsupported | Managed in the privacy policy and the TOS of the Teams application. To be defined by the customer when configuring their Teams bot application. |
Onboarding | Unsupported | |
GDPR recovery request | Unsupported | |
GDPR deletion request | Unsupported | |
Allow the end-user to change the language | Unsupported | 1 bot Teams = 1 language, 1 consultation space |
Allow the end user to change the consultation space | Unsupported | 1 bot Teams = 1 language, 1 consultation space |