Salesloft incident

MS Teams Bot: Some meetings not being processed by Conversation Intelligence

Minor Resolved View vendor source →

Salesloft experienced a minor incident on November 12, 2025, lasting —. The incident has been resolved; the full update timeline is below.

Started
Nov 12, 2025, 04:22 PM UTC
Resolved
Nov 12, 2025, 04:22 PM UTC
Duration
Detected by Pingoru
Nov 12, 2025, 04:22 PM UTC

Update timeline

  1. monitoring Nov 12, 2025, 04:22 PM UTC

    Nov 12, 11:22 EST Resolved - This incident has been resolved. Nov 11, 16:54 EST Monitoring - A fix was deployed to production around 4:00 PM Eastern, and new meetings are now recording and processing correctly. We’ve also added enhanced error reporting to help us detect and resolve similar issues more quickly in the future. Our team identified an issue that caused the Conversation Intelligence bot to join meetings but fail to capture audio, resulting in missed recordings. Please note that, due to the nature of the recording process, previously affected meetings cannot be recovered or reprocessed. We apologize for the disruption this may have caused. We are currently monitoring to ensure the issue has been fully resolved. Nov 11, 12:20 EST Investigating - We are currently investigating an issue where the Conversation Intelligence bot for Microsoft Teams successfully joins scheduled meetings, but the recording does not process as expected afterward. Impacted users may see an error message similar to: “Recording skipped: Recording has no audible words to be transcribed.” The issue appears to affect a subset of customers and meetings at this time. Our engineering team is actively investigating the root cause. We will provide an update as soon as we have more information.