What happened
What this says
Current to 14 Oct 26Brittany Hayes reported call recorder connector down, blocking support team access. Olivia Grant diagnosed API key failure, likely from credential rotation, and escalated to tech team pending customer confirmation.
Problem: Call recorder connector authentication failed, likely from API key rotation on the customer side. Olivia found the API key invalid in the logs and escalated. Handling: She asked the customer to confirm what changed on their IT side and then re-authenticate the connector. Watch: The connector is down, blocking the support team's access to call data, creating high operational impact.
Details
Updated 9 Oct 26Trail
- created · Brittany Hayes 17 Sep 2026 13:15Our call recorder isn't loading data at all. This is blocking our support team from accessing call data. Can you help us urgently?
- internal_note · Olivia Grant 17 Sep 2026 14:22Checked logs, connector authentication failed. Customer may have rotated API key. Escalating to tech team. Need to confirm with Brittany what changed on their end.
- public_reply · Olivia Grant 17 Sep 2026 15:46Hi Brittany, I've reviewed the connector logs and found that the API key is no longer valid. This usually happens after a rotation or credential update on the call recorder side. Can you check whether your IT team changed anything recently? Once we know, we can re-authenticate the connector. Thanks, Olivia
- status_change · 26 Sep 2026 23:59