What happened
What this says
Current to 11 Oct 26Duplicate call records broken compliance tracking ahead of a regulatory review. BB-Demo traced the duplicates to a call recorder configuration change and escalated for platform fix.
Problem: Duplicate call records on different dates broke call history tracing for complaints team. Regulatory review scheduled one week from ticket creation.
Handling: Bethan identified double indexing in connector logs. Customer confirmed call recorder settings changed Tuesday. Escalated to platform as priority fix given regulatory deadline.
Watch: Critical compliance deadline. Resolution status not shown in final content despite high priority flag.
Details
Updated 9 Oct 26Trail
- created · Femi Olatunji 27 Jan 2026 09:47We've spotted duplicate call records in the brain. The same call is appearing on different dates. This is breaking our complaints team's ability to trace the full call history. We have a regulatory review next week so we need this resolved urgently. Can you investigate?
- public_reply · Bethan Lister 27 Jan 2026 12:45Hi Femi, thanks for flagging this. I can see the duplicates in the logs, looks like the call recorder connector is indexing the same record twice in a sync. Just so I've got this right, is it all calls or just recent ones? And when did you first notice it happening?
- public_reply · Femi Olatunji 28 Jan 2026 15:26It's just started in the last couple of days, affecting calls from the past week. We changed something in our call recorder settings on Tuesday. Could that be related?
- internal_note · Bethan Lister 28 Jan 2026 16:30Connector config change triggered double indexing. Escalate to platform. Regulatory deadline next week, priority fix.
- status_change · 7 Feb 2026 23:59