Delayed or missing post-call summaries and transcripts
minor- Started
- Jul 31, 11:43 AM EDT
- Resolved
- Jul 31, 3:00 PM EDT
- Duration
- 3h 17m
Cresta's updates (3)
- investigating · Jul 31, 11:43 AM EDT
We are investigating an issue affecting some Cresta Voice customers where post-call summaries, notes, call reasons, and call outcomes may be delayed or unavailable after a call ends. Live transcripts may also be delayed or incomplete for some conversations. This may increase agent after-call work (ACW) time while post-call processing completes. Our engineering team is actively investigating and working to restore normal processing. The scope of impact and any recovery options are still being assessed. We will provide the next update within 60 minutes, or sooner if we have material progress. If your team is experiencing this issue, please contact Cresta Support through the Director Support widget or at support@cresta.ai. Including conversation or call IDs and approximate call times will help us validate impact and recovery.
- investigating · Jul 31, 12:32 PM EDT
We continue to investigate an issue affecting post-call processing for some Cresta Voice customers. Live transcription appears to be recovering, but post-call summaries and related post-call outputs may still be delayed. We do not have further updates at this time and will share confirmed progress as soon as it is available.
- resolved · Jul 31, 3:00 PM EDT
We have resolved an issue that caused some customers to experience delayed or missing post-call summaries and increased after-call work. The issue affected Fireworks AI infrastructure used by our post-call summarization service. We worked with Fireworks to restore the affected service, and summary generation has returned to normal. We are continuing to backfill summaries for conversations affected during the incident. No customer action is required. We apologize for the disruption and appreciate your patience while we worked to restore service.
What our checks recorded
We checked Cresta 40 times from Cresta's start time to its resolution, once every five minutes. Every one of them reached Cresta's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 193 ms, against 194 ms over the 24 hours before. Cresta posted the incident at Jul 31, 11:43 AM EDT.
Updates are Cresta's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗