Create QBR templates for your SuccessBLOCs
Upload your QBR templates to each of your SuccessBLOCs to control messaging and formatting for your team’s QBR presentations. Read More.
Get notified before hitting the limit of customer accounts
Admins will get notified in advance when they are close to hitting the limit of Customer Accounts, so you can act proactively and purchase additional seats. Read More.
Easily reorder lifecycle stages
Totango administrators now have the ability to change the order of lifecycle stages in attribute settings using a simple drag and drop.
Refreshed design of Account Profile widget editors
Explore the enhanced user experience changes to the Account Profile widget.
Enhanced login security measures
We implemented a new security policy to limit the max number of consecutive failed login attempts to prevent brute force attacks.
Creating SuccessPlays using Webhooks is no longer in Beta!
We removed the BETA flag from SuccessPlay Webhooks as this feature is no longer in beta.
[Bug Fix] We resolved an issue where tasks created by SuccessPlay can’t be completed.
[Bug Fix] When copying a campaign that has already ended the new campaign status was set to ‘Ended’ status as well. This issue is now resolved.
[Bug Fix] When multi-select list values are too long on account profile pages, there is no option to see the entire extended value. The issue is now resolved.
[Bug Fix] When an attribute is defined as a metric (in the key info section) it is not positioned where it is supposed to be. This issue is now resolved.
[Bug Fix] Manually assigning a user to a role in an account profile, would display the user’s name in lowercase, resulting in incorrect and duplicate names in key info, segments, tasks, etc. This issue is resolved but does not apply retroactively.
[Bug Fix] Campaigns aren't using the sender signature after users had their emails changed. This issue is now resolved.
[Bug Fix] In SuccessBlocs, the close button in campaigns, segments, and SuccessPlays, is not aligned with the search text box. This issue is now resolved.