Previous incidents
Inbound Call Handling Issue Following Update – Resolved
Resolved Nov 27 at 09:23am CET
Following a platform update at 07:15 CET, we observed performance slowdowns starting at 08:46 CET.
These slowdowns impacted the handling of inbound calls:
Some calls were not processed.
Callers received a message asking them to call back later.
A full rollback to the previous version was executed at 09:06 CET. Since then, the system has been stable and is under active monitoring.
Failed Post-Call Data Extraction
Resolved Nov 19 at 04:17pm CET
Our R&D team identified that between 15:14 and 15:46 CET, post-call data extraction was unavailable.
Calls were successfully handled, but extracted information was missing.
The issue was caused by a platform update and has been resolved. The system is now fully operational.
We continue to monitor closely to ensure stability.
1 previous update
Some calls are not processed
Resolved Nov 10 at 05:55pm CET
Our R&D team identified that at 13:03 CET today, one backend instance became unresponsive. Less than 13% of calls were affected, resulting in unanswered calls. In most cases, callers retried and their calls were successfully handled.
The issue was resolved at 17:54 CET, and the platform is now fully operational. We continue to monitor the situation closely to ensure ongoing stability.
1 previous update
Post-Call Email Delivery Failure
Resolved Oct 30 at 09:24am CET
Due to an infrastructure issue, post-call emails were not sent the 29 october 2025 between 16:40 and 23:30 CET. Users relying on automated post-call email workflows may have experienced missing communications.
The issue has been identified and resolved. Additional monitoring and safeguards have been implemented to prevent recurrence and ensure prompt detection of similar anomalies.
We apologize for the inconvenience and thank you for your continued trust.
Vivienne TTS Voice Unavailable
Resolved Oct 21 at 11:23am CEST
The issue has been resolved by our service provider, and the voices have been restored on Vivienne
1 previous update
Some calls are not processed and backoffice is unavailable
Resolved Oct 01 at 03:18pm CEST
Our R&D team has identified two contributing factors:
- Since 17:00 CET yesterday, one backend instance has been unresponsive. Due to missing health checks on the load balancer, less than 4% of calls were impacted. Between 14:25 and 14:38 CET today, a release deployment encountered memory saturation which caused service freezing and degraded performance.
Mitigation actions have been effective since 14:38 CET, and the platform is now fully operational. We continue to monitor closely to ensur...
1 previous update