What was said
What this says
Current to 10 Oct 26Joost Verbeek accepts the three connectors are on track for go-live a week after the call, but wants the one late refresh recorded as a miss with its reason. He will not brief his merchant team until he has the written summary.
What happened: Elena Novak and Hannah Lowe reviewed the three agreed connectors (HubSpot, Zendesk and the accounting system), two open tickets and a firm go-live date. Since the schedule change the refresh has completed before 07:00 on every business morning except one.
Customer view: Joost accepts the miss was a source outage but still counts it against the agreement. He expects the three connectors in his order form, working, and nothing more for go-live.
Commercial: He is open to more connectors after go-live, which is a possible extension of the connector set. The missing merchant field is wanted by merchant risk, not account managers.
Watch: Joost will not tell the merchant team the date until the written summary arrives on Monday. A second late refresh at go-live would land on a customer who is keeping score.
Themes
Current to 9 Oct 26Who was there
B-Brain
Them
Follow-up
Next steps
Current to 9 Oct 26- Hannah Lowe to write the connector summary, including the Thursday miss with its reason.
- Elena Novak to send the go-live summary listing the three connectors, load times and contacts on Monday.
- Hannah Lowe to look at the missing merchant field this week and record what she finds in the ticket.
Risks
Current to 9 Oct 26- One refresh finished twenty minutes after 07:00 because of a source outage, and Joost wants it logged as a miss against the agreement.
- A second connector sync ticket, a missing merchant field, is still open and merchant risk wants it solved after go-live.
- Joost will not brief his merchant team until he has the written go-live summary.
Opportunities
Current to 9 Oct 26- Joost is open to connecting further systems after go-live.
Transcript
- Elena Novak NoneGood afternoon, everyone. Thank you for joining. As I wrote in the agenda, there are three points. One, the connector review. Two, the open tickets. Three, the go-live date. Hannah is with us for the connectors.
- Joost Verbeek NoneAfternoon. Yes, I have the agenda. Before that, to be honest, were the actions from the last check-in completed?
- Elena Novak NoneTo confirm, two of the three are complete. The Zendesk update change is live. The status mapping is corrected. The third, the written connector summary, Hannah will present now.
- Hannah Lowe NoneThanks, Elena. What do you most need to know from me? Because I can go through all of it, or only the places that are risky.
- Joost Verbeek NoneThe risky places. And whether the connectors do what was agreed.
- Hannah Lowe NoneRight. The short answer is yes for the three that were agreed: HubSpot, Zendesk and the accounting system. The longer answer is that they do it with one condition. The accounting system extract depends on the source batch finishing, and we changed it to wait for that. Since the change it has completed before 07:00 on every business morning except one.
- Sanne Bakker NoneThe one was a Thursday. Refresh not complete at 07:00. See ticket from that day. It was twenty minutes late.
- Hannah Lowe NoneYes. And to be precise, that was a source outage, not our schedule. I've put the source's own timestamp in the ticket. I'll put that in writing in the summary.
- Joost Verbeek NoneI accept that it was the source. But it is still a miss against the agreement. I want it recorded as a miss with the reason.
- Elena Novak NoneAs agreed, I will make sure that it is recorded with the reason, in the written actions.
- Hannah Lowe NoneSecond point on connectors. Tickets and status changes now flow as updates, so a ticket solved at the weekend shows solved on Monday. Femke has been checking that.
- Sanne Bakker NoneShe has. She tells me it is correct now. I checked ten records myself, same result. Not scientific.
- Hannah Lowe NoneIt's a good start though. Joost, are there other systems you want connected before go-live? I'd rather know now.
- Joost Verbeek NoneNot before go-live. After, perhaps. Our order form lists three connectors for this stage, so I expect these three, working. That is what I signed.
- Elena Novak NoneUnderstood. To confirm, no new connectors for go-live.
- Elena Novak NonePoint two, tickets. There are two open. Both are connector sync, both raised by Sanne. One is the Thursday we just discussed. The other is waiting on a source field. Sanne, can you say the status?
- Sanne Bakker NoneThe second one is a missing field in the merchant record. Not urgent. Merchant risk wants it, not the account managers. I have not decided it is blocking.
- Joost Verbeek NoneIt is not blocking go-live. But I want it solved afterwards, not forgotten.
- Hannah Lowe NoneI'll take that. I'll look at the field this week and put what I find in the ticket.
- Elena Novak NonePoint three. Go-live. We have set it for next Tuesday, a week from today. Joost, you asked for a firm date.
- Joost Verbeek NoneYes. Next Tuesday. So what is the plan for that morning? Who is watching?
- Hannah Lowe NoneYusuf will watch the load that morning. I'll be on the call with Sanne at half past seven if the refresh is late, and Elena will have the written summary to you the day before.
- Elena Novak NoneI will send it on Monday. It will list the three connectors, the load times, and who to call.
- Sanne Bakker NoneI will check at seven. If it is complete I say so in the channel. If not, also.
- Joost Verbeek NoneGood. Then I will tell the merchant team it is next Tuesday. I will not say it until I have your summary in writing.
- Elena Novak NoneThat is fair. So, to confirm actions. One, Hannah: the connector summary, including the Thursday miss. Two, Hannah: the missing field. Three, Elena: the go-live summary on Monday. Four, Sanne: the morning check. Anything to add?
- Joost Verbeek NoneNo. Thank you. Met vriendelijke groet, Joost.
- Elena Novak NoneThank you all. Kind regards, Elena.