Release Notes - Ver 20.279 - October 6, 2024

If you're viewing this article in your inbox, click here to view the full article.

Query customer data from Totango in MS Teams

The Totango bot for Microsoft Teams helps your teams drive customer outcomes through enhanced collaboration. Get the information you need—or even quickly log a touchpoint—through a conversational interface, without leaving MS Teams chat. 

With Totango bot for MS Teams, your teams can: 

  1. Access account information
    The Totango bot can show you key information about a specific account, including recent touchpoints.
  2. Create a touchpoint
    Create touchpoints for follow-ups and strategic actions directly in the MS Teams interface. The touchpoint will be immediately viewable on the account timeline for team members with access to the Totango platform.

To use the Totango bot for MS teams:

  1. Your Totango administrator must connect your Totango account with MS Teams.
  2. Your Totango administrator must define the account set that the bot can access by configuring team settings in Totango.
  3. Your administrator of MS Teams must set installation preferences for the bot, according to the organization needs and policies.
  4. Once the bot is installed, anyone in your MS Teams application can interact with the bot, even if they do not have a Totango user license.

Totango bot is not currently available for EU services.

Read more ➡

Bug fixes

[Bug Fix] There were areas of the UI where users with a Contributor license could update or delete tasks where they were not the assigner. This has been fixed.

[Bug Fix] There were areas of the UI where users with a Contributor license could complete tasks where they were not the assignee. This has been fixed.

[Bug Fix] Issue with loading data preview of new and existing Amazon S3 outbound integration jobs. This issue is now resolved.

[Bug Fix] Resolved an issue in campaigns where CSAT and NPS components did not show the configured text in editor.

[Bug Fix] When trying to add an attribute to the collection from the account profile, the attribute would disappear and not save. After the fix, the attribute is created as expected.

[Bug Fix] The drop-down for the multi-select list attribute type did not display correctly, with no spacing and line breaks(/n) in the SuccessPlay filter. The issue has been resolved.

[Bug Fix] License utilization hierarchy roll-up based on the calculated built-in metric (AVG) populated an incorrect value in percentage. The issue has been resolved.

[Bug Fix] Folders with long structure caused display issues when saving segments from the Report tab in the SuccessBLOC. The issue has been resolved.

[Bug Fix] When overdue tasks are completed, the account returned in the segment when using the overdue filter. The issue has been resolved.

[Bug Fix] In some cases, SuccessFlow was empty for SuccessPlays in reports. This issue has been resolved.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request