What was said
What this says
As at Fri 9 Oct 2026Liam Sedgwick reported the orders page a day behind. The cause was the customer's IT moving the export time for a server change without telling him. Hamza Akhtar will adjust the connector schedule and confirm the time in writing.
What happened: Liam said the orders looked a day behind and that Melanie had asked him about it. The connector run history showed runs finishing later than expected, which Hamza traced to the source rather than B-Viz.
Customer view: IT had moved the export time the previous week and had not told the team, which Liam called annoying. Usage is light so far: a few managers have looked and they are asking the same questions Liam would.
Commercial: This is an onboarding connector sync and freshness issue, not a complaint about value. Melanie is keen on the retailer questions, which is early interest worth building on.
Watch: The fix depends on IT holding the export time. Hamza will send the exact time in writing and close the ticket once the next run is up to date.
Themes
As at Fri 9 Oct 2026Who was there
BG-Demo
Them
Follow-up
Next steps
As at Fri 9 Oct 2026- Hamza Akhtar to adjust the connector schedule and send Liam the exact export time in writing.
- Liam Sedgwick to ask IT to hold the export time.
- Hamza Akhtar to close the ticket once the next run shows up to date.
Risks
As at Fri 9 Oct 2026- The customer's IT changed the export time without telling the team, so the lag could recur.
- Manager usage is still light, so value is not yet visible to the business.
Opportunities
As at Fri 9 Oct 2026- Melanie's interest in the retailer questions can anchor wider use once the data is reliably current.
Transcript
- Hamza AkhtarHi Liam, afternoon. Thanks for coming back to me. I know you've been busy.
- Liam SedgwickAfternoon, yes. Sorry, I've been fighting with the export all morning. It's better now, I think.
- Hamza AkhtarTell me what you're seeing. You mentioned the ticket we logged?
- Liam SedgwickYes. The orders look a day behind on the page. Melanie asked me about it this morning, and I didn't know what to tell her.
- Hamza AkhtarOkay. That's the right ticket. Let's check the timing first, before we assume it's the data. Can you share the connector run history?
- Liam SedgwickSharing it now. It shows the runs finishing, just later than I'd expect.
- Hamza AkhtarRight. So the connector is loading, but the export is landing later than it used to. That usually points at the source, not at us.
- Liam SedgwickPossibly something changed on our side. I'd have to ask IT, I'm not sure what they touched.
- Hamza AkhtarPlease do. I'd like to know if the export time moved, because that's the likeliest cause. I'll also check our schedule to see if anything changed on our end.
- Liam SedgwickOkay. I'll ask this afternoon and let you know what they say.
- Hamza AkhtarWhile we wait, let's look at the answers the team is getting. Are the managers using it yet?
- Liam SedgwickA few of them have had a look. Nothing heavy yet. They're asking the same questions I'd ask.
- Hamza AkhtarThat's a good sign at this stage. Once the questions get more specific, we'll see the value more clearly.
- Liam SedgwickLet's hope. Melanie's keen on the retailer questions.
- Liam SedgwickIT replied. They moved the export time last week for a server change. They didn't tell us, which is annoying.
- Hamza AkhtarThat explains the lag, then. I'll adjust the connector schedule to match, and the page should catch up on the next run.
- Liam SedgwickGood. Can you tell me what the schedule should be? I'll ask IT to hold it there.
- Hamza AkhtarI'll send you the exact time in writing, so IT has it in black and white and nothing gets moved again.
- Hamza AkhtarOkay, I'll close the ticket once the next run shows up to date. Let's pick up the test results on the next call.
- Liam SedgwickSounds good. Thanks for sorting that out so quickly.
- Hamza AkhtarNo problem. Speak soon, Liam.
- Liam SedgwickBye, Hamza.