Fenmoor Specialty Underwriting / BB-Demo – Escalation
Callcompleted
Fenmoor Specialty Underwriting: documents · 2026-07-22 15:30
Fenmoor escalated after the nightly refresh missed 07:00 on several business days. BB-Demo admitted a shipped change caused it and the connector was misdiagnosed. Customer trust is the issue; a freshness credit is open.
What was said
What this says
Current to 10 Oct 26Fenmoor escalated after the nightly refresh missed 07:00 on several business days. BB-Demo admitted a shipped change caused it and the connector was misdiagnosed. Customer trust is the issue; a freshness credit is open.
What happened: On 22 Jul 2026 Callum Reid and Imogen Hartley heard Daniel Okafor and Kieran Walsh explain that a change to the refresh job stalled it. Kieran admitted he first blamed the CRM connector and asked Fenmoor to re-authorise it.
Customer view: Imogen said the brain exists to answer capacity providers by seven in the morning, and that the slip became a conversation upstairs. Callum described two underwriters pulling figures a day behind, and he will not accept that it is fixed until told.
Commercial: Fenmoor is on Enterprise, where data freshness is credited. Daniel will go through the calculation with Priya Raman and write to Callum and the budget holder; no figure was given.
Watch: Imogen said usage is up and people rely on it now. A repeat miss would hit a growing, valued base, and the completion alert is not yet confirmed as live.
Themes
Current to 9 Oct 26Theme
Stale nightly refresh escalation
Importance
complaint
Sentiment
mixed
Voice
champion
Who was there
BB-Demo
CRMmade from
Them
CRMmade from
Follow-up
Next steps
Current to 9 Oct 26- Daniel Okafor sends the written summary, with Imogen's note as an appendix, by Friday.
- Kieran Walsh sets up and tests the completion alert into the customer Slack channel before calling it live.
- Daniel Okafor confirms the freshness credit with Priya Raman and writes to Fenmoor's budget holder, copying Callum.
Risks
Current to 9 Oct 26- A repeat late refresh would damage trust with a customer that relies on the brain for capacity-provider questions.
- Three high-priority tickets were handled as separate threads and the first diagnosis wrongly pointed at the customer's connector.
- Callum will not treat the problem as fixed until he is told, and verification has no committed date.
Opportunities
Current to 9 Oct 26- Open handling of the failure and a clear written account can strengthen the relationship, as Imogen said.
- Rising question volume well within the Enterprise user allowance shows value the renewal conversation can use.
Transcript
Daniel Okafor NoneHello, everyone, and thank you for making the time at short notice. Let me just check who's joined. I can see Callum and Imogen, and Kieran from our platform team. Is that everyone?
Callum Reid NoneThat's us. Callum here. I've got a hard stop at quarter past four, so let's make it count. What I need is a straight account of what happened with the refresh, and what changes.
Imogen Hartley NoneAfternoon, all. If I may, a word of context before the detail. We have capacity providers who ask us, quite reasonably, how current our underwriting view is. The whole reason we bought the brain was to answer those questions from one place by seven in the morning. So when that slipped, it wasn't just an inconvenience. It was a conversation I had to have upstairs.- Daniel Okafor NoneUnderstood, Imogen, and thank you for putting it that way. Just to close the loop on why we're here: the nightly refresh didn't finish by 07:00 on a run of business days, and the dashboards your team opens first thing were showing the previous picture. That's on us to explain properly, and I wanted Kieran on the call because he's been closest to it.
Kieran Walsh NoneHi, yes. Sorry, just to check, can everyone hear me alright? Good. I'll try not to over-explain. I think the most useful thing is to be honest about the order of events, because I got the first part of it wrong.- Callum Reid NoneGo on.
- Kieran Walsh NoneSo when the first ticket came in, the symptom looked like a sync problem with your CRM connector. Records weren't moving, the connector status looked unhappy, and I treated it as a fault on the Fenmoor side. I asked your team to re-authorise the connection and check the permissions on the service account.
- Callum Reid NoneWhich my people did. Twice. That cost us most of a morning and it made no difference.
- Kieran Walsh NoneYes. I'm really sorry about that. It made no difference because it wasn't the connector. I've raised a ticket for the write-up, but the short version is that a change we had shipped to the refresh job altered how the steps were ordered, and under your volumes the job simply ran long and then stalled before the final stage.
- Imogen Hartley NoneSo the connector was a symptom, not a cause.
- Kieran Walsh NoneExactly that, I think. The connector looked unhappy because it was waiting on a job that never released it. I should have looked at the refresh job before I asked you to touch anything on your side.
- Daniel Okafor NoneAnd I'd add, Callum, Imogen, that when it came across my desk the pattern across several mornings didn't fit a single connector, which is why I asked for this call rather than another ticket thread. Better that you hear it all in one go.
- Callum Reid NoneFine. Let me be specific about the impact, because it's the part that matters to me. Two of my underwriters were preparing a bordereaux query for a syndicate. They pulled numbers that were a day behind. One of them caught it. The other might not have. That's a capacity-provider question waiting to happen.
- Daniel Okafor NoneThat's exactly the risk, and I'm glad you said it plainly. How is the team finding it now? Is the data landing on time at the moment?
- Callum Reid NoneLast couple of mornings it's been there by seven. But I've been burned. Nobody's told me it's fixed, and I'm not going to assume.
- Kieran Walsh NoneThat's fair, and I'm going to be careful with the word. I think we've found the cause, and the change that was causing it has been rolled back. But I won't say it's fixed until it has run through enough nights and I've verified it against the completion times. Right now I'd call it recovering.
- Callum Reid NoneBy when?
- Kieran Walsh NoneSorry, by when will I call it verified? I'd rather not give you a date I can't stand behind. What I can commit to is checking the completion time every business morning, and writing to you if it's ever later than seven.
- Daniel Okafor NoneIf I can step in. Callum, I don't guess dates I don't own, so let me give you the ones I do. You'll have a written summary from me by Friday: what happened, the timeline, what we changed. And the morning confirmation Kieran describes will start tomorrow.
- Callum Reid NoneWritten summary by Friday. Good. Make sure it covers the days my people lost on the connector.
- Daniel Okafor NoneIt will. I'll put that in plainly.
- Imogen Hartley NoneCan I ask a slightly different question? The real question is not only why it stalled. It's why we found out before you did. When my team opened the dashboards and saw yesterday's picture, nothing had told them the refresh was late. Is there any monitoring that says, in effect, this morning's data is not complete?
- Kieran Walsh NoneThat's the gap, honestly. We had an alert on whether the job started, but not on whether it finished by the time you need it. I've raised a ticket to alert on completion against seven in the morning, and I'd like it to reach your team's channel as well, if you're happy with that.
- Imogen Hartley NoneI'd welcome that. Put it into Slack for us. Callum, would your team want the same?
- Callum Reid NoneYes. Same channel. If it's late I want to know before an underwriter opens a dashboard, not after.
- Kieran Walsh NoneOkay. I'll set it up and then test it properly, so you actually see an alert fire, before I tell you it's live.
- Daniel Okafor NoneThank you, Kieran. Now, one thing I want to be clear on, because it touches the contract. You're on Enterprise, and under your order form, data freshness is something we are accountable for, not just availability. The brain was up during those mornings, but being up isn't the same as being current, and for Enterprise that's covered.
- Callum Reid NoneMeaning what, in practice?
- Daniel Okafor NoneMeaning there's a service credit for freshness that I believe applies to the month with the breach. I don't want to quote you a figure off the cuff. Priya Raman owns your order form, and I'll go through the calculation with her and come back to you with the exact position.
- Callum Reid NoneI don't do budget. That's Richard's. Send it to him and copy me.
- Daniel Okafor NoneOf course. I'll copy you.
- Imogen Hartley NoneI'd rather the credit weren't the headline, to be honest. What I care about is trust. I've seen this work: when a vendor is open about a failure, and shows what changed, the relationship gets stronger. When they're vague, it quietly doesn't.
- Daniel Okafor NoneThat's a fair standard and I'd hold us to it.
- Callum Reid NoneLet me come back to the connector thing, because I'm not letting it go yet. Three tickets this last month. All three marked high. If the first one had been read properly, would the other two have existed?
- Kieran Walsh NoneI think, honestly, probably not the second. The third was a follow-up on the same mornings. I've raised a ticket for how we triage a freshness complaint, so the first step is checking our own job before we ask a customer to change anything.
- Daniel Okafor NoneAnd I'd say we should have joined those up for you earlier. Three separate threads was our doing. I should have pulled them into one conversation sooner.
- Imogen Hartley NoneLet me say something that may sound odd on an escalation call. Usage is up. More of my underwriters are asking the brain questions than a few months ago, which tells me the value is real. That's exactly why a stale morning hurts. People rely on it now.
- Daniel Okafor NoneI'm glad you said that, because it's what I see too. Adoption is climbing, well within your hundred and fifty seats, and that's the reason I'd like the reliability side to be dull and boring for the foreseeable future.
- Callum Reid NoneDull is good. Dull I can work with.
- Imogen Hartley NoneKieran, a practical request. Could we have a short note I can pass to our capacity providers if they ask? Factual. What happened, what's different now. No drama.
- Kieran Walsh NoneYes, I can draft that. I'd want Daniel to review it before it goes anywhere, because I'm still fairly new and I'd rather it was right than fast.
- Daniel Okafor NoneI'll review it, and it can be an appendix to the Friday summary so you've one document, Imogen, not two.
- Imogen Hartley NonePerfect. Let's make it count.
- Callum Reid NoneOne more from me. If it happens again, who do I call? I don't want to be raising a ticket and waiting.
- Daniel Okafor NoneMe, directly, and I'll bring in whoever is on call. On Enterprise your priority tickets have the fastest response we offer, but I'd rather you rang me than relied on that.
- Callum Reid NoneRight. Good. That's what I needed.
- Daniel Okafor NoneSo just to close the loop on next steps. Kieran verifies the completion times each morning and writes if it's late. Kieran sets up the completion alert into your Slack channel and tests it before saying it's live. I send the written summary by Friday, with Imogen's note as an appendix. And I'll come back to you and Richard on the freshness credit once I've been through it with Priya. Have I missed anything?
- Imogen Hartley NoneThat's all of it. Thank you, Daniel. Thank you, Kieran. I appreciate you naming the connector point rather than hiding it.
- Kieran Walsh NoneThanks. And, again, sorry about the lost mornings. I'll do better on the triage.
- Callum Reid NoneCallum. Off I go.
- Daniel Okafor NoneBest wishes, everyone. Speak soon.
Callsmade from