January Bug Fixes
- Improved stability for Conversation Intelligence related Insight reporting.
- Company Context in Weflow's ASK AI was stored, but not visible.
- Searching in transcripts did not render results.
45 updates shipped in 2026317 all time
Showing January 2026 and earlier · Back to latest
The feature lets you define a custom team hierarchy inside Weflow that overrides the Salesforce role hierarchy.
What it enables
--
How it works
This lets you mirror your operational org structure inside Weflow without depending on Salesforce’s hierarchy.
Instead of giving an entire team access to all recordings or trying to give access through complicated hierarcy systems, Weflow also let's you give access to all recordings of a team to specific individual users:
✅ Improved handling of HTML content in specific message types on GMail.
✅ Improved multi-logging behavior when multi-logging to tasks is enabled in sharing settings on SFDC (specifically for logging to the task object).
✅ Improved reliability of dynamic teams when refreshing subscription to email and meeting inbox on Google Workspace.
✅ Resolved error where the "Responsiveness" report was not shown to all users automatically.
✅ Improved handling of scheduled email messages via GMail. When more than 10 emails were scheduled at the exact same time, a conflict with logging could occur in some specific cases.
✅ Improved sorting in insight reports.
The keyword tracker in Weflow now automatically translates keywords in to all available languages. The tracker is overall more strict when it comes to identifying keywords mentioned.
In the "Contact Creation" settings of an Activity Capture configuration, admins can now define a participant threshold for emails and meetings where Weflow should not create new contacts.
Example: If you have training events with 20+ participants, you may not want to create new contacts automatically. With this setting, you can fine tune the contact creation rules within Weflow.
As of version 2.91, Weflow will only create a contact if there is no currently non-converted lead with the same email.
The new interactivity reports give you a deep dive into:
You can read more about all calculations and details here: help.getweflow.com/en/articles/12606897-interactions-views
Custom Rules in the Activity Capture configurations now also block the creation of new contacts.
Example: In the example above, no contact would be created if the parent account matches the one of these values i.e. Investor and/or Reseller.
In some specific scenarios, when creating a new contact, the Chrome Extension and Outlook Add-In had the ability to override the underlying business logic of creating new contacts.
This issue has been fully resolved by adding additional checks that prevent new contact creation if not permitted by the Activity Capture configuration.