What happened
What this says
Current to 11 Oct 26Elliot Kirkby reported team usage had stopped over two months. Bethan Lister arranged call to diagnose root cause. Ticket solved 22 Sep 2026.
Problem: Operations Director reported sharp drop in team usage over recent months. No technical failure mentioned; request framed as a commercial value conversation.
Handling: Assigned to Bethan Lister. First response at 19:11 on 2026-09-07 (136 minutes after report) with diagnostic framework: stale data, missing features, or broken functionality. Call arranged for early the following week.
Watch: Usage cliff without complaint may signal either a single blocker or organisational change. High churn risk if root cause is value mismatch rather than fixable problem.
Details
Updated 9 Oct 26Trail
- public_reply · Elliot Kirkby 7 Sep 2026 13:18Can we find time for a call this week? Need to discuss what's happened with team adoption and see if there's something we can do.
- created · Elliot Kirkby 7 Sep 2026 16:55We need to talk about usage. The team has basically stopped using the brain over the past couple of months. I'd like to understand what's gone wrong and see if there's a quick fix.
- public_reply · Bethan Lister 7 Sep 2026 19:11Hi Elliot, Thanks for getting in touch. That's a conversation worth having. Usage changes often come down to a specific pain point: a missing feature, data that isn't fresh enough, or something that broke. Are you available for a call early next week so we can dig into this together? Thanks, Bethan
- status_change · 26 Sep 2026 23:59