Elena Novak

Veldmaat Payments / B-Brain – Check In

Callcompleted

Veldmaat Payments: documents logo Veldmaat Payments: documents · 2026-04-07 15:15

Joost 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 was said

What this says

Current to 10 Oct 26

Joost 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.

AI · claude-sonnet-5-5 · 10 Oct 2026

Themes

Current to 9 Oct 26
Theme
Go-live readiness and connectors
Importance
neutral
Sentiment
mixed
Voice
decision-maker

Who 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

  1. Elena Novak
    Elena Novak None
    Good 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.
  2. Joost Verbeek
    Joost Verbeek None
    Afternoon. Yes, I have the agenda. Before that, to be honest, were the actions from the last check-in completed?
  3. Elena Novak
    Elena Novak None
    To 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.
  4. Hannah Lowe
    Hannah Lowe None
    Thanks, 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.
  5. Joost Verbeek
    Joost Verbeek None
    The risky places. And whether the connectors do what was agreed.
  6. Hannah Lowe
    Hannah Lowe None
    Right. 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.
  7. Sanne Bakker
    Sanne Bakker None
    The one was a Thursday. Refresh not complete at 07:00. See ticket from that day. It was twenty minutes late.
  8. Hannah Lowe
    Hannah Lowe None
    Yes. 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.
  9. Joost Verbeek
    Joost Verbeek None
    I 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.
  10. Elena Novak
    Elena Novak None
    As agreed, I will make sure that it is recorded with the reason, in the written actions.
  11. Hannah Lowe
    Hannah Lowe None
    Second 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.
  12. Sanne Bakker
    Sanne Bakker None
    She has. She tells me it is correct now. I checked ten records myself, same result. Not scientific.
  13. Hannah Lowe
    Hannah Lowe None
    It's a good start though. Joost, are there other systems you want connected before go-live? I'd rather know now.
  14. Joost Verbeek
    Joost Verbeek None
    Not 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.
  15. Elena Novak
    Elena Novak None
    Understood. To confirm, no new connectors for go-live.
  16. Elena Novak
    Elena Novak None
    Point 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?
  17. Sanne Bakker
    Sanne Bakker None
    The 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.
  18. Joost Verbeek
    Joost Verbeek None
    It is not blocking go-live. But I want it solved afterwards, not forgotten.
  19. Hannah Lowe
    Hannah Lowe None
    I'll take that. I'll look at the field this week and put what I find in the ticket.
  20. Elena Novak
    Elena Novak None
    Point three. Go-live. We have set it for next Tuesday, a week from today. Joost, you asked for a firm date.
  21. Joost Verbeek
    Joost Verbeek None
    Yes. Next Tuesday. So what is the plan for that morning? Who is watching?
  22. Hannah Lowe
    Hannah Lowe None
    Yusuf 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.
  23. Elena Novak
    Elena Novak None
    I will send it on Monday. It will list the three connectors, the load times, and who to call.
  24. Sanne Bakker
    Sanne Bakker None
    I will check at seven. If it is complete I say so in the channel. If not, also.
  25. Joost Verbeek
    Joost Verbeek None
    Good. Then I will tell the merchant team it is next Tuesday. I will not say it until I have your summary in writing.
  26. Elena Novak
    Elena Novak None
    That 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?
  27. Joost Verbeek
    Joost Verbeek None
    No. Thank you. Met vriendelijke groet, Joost.
  28. Elena Novak
    Elena Novak None
    Thank you all. Kind regards, Elena.

B-Brain is a fictional company; every organisation and person here is invented. Built by site/build_site.py from the site tree, data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Brain is one place to read everything the company knows about its customers: the CRM, calls, emails, support tickets, product usage, invoices, documents, news and HR. Every page is built from those systems and the data is current to Fri 9 Oct 2026.

How to use the site

How to ask

Press Ask Brain in the header. Type a question, or pick one of the examples.

The site itself does not call an AI model; answers in Claude come from the same figures you see here.

What the data covers

DataRecords
Organisations75
People at customers290
B-Brain staff40
Calls784
Email threads1,169
Support tickets449
Documents477
Deals117
Invoices101
Events49
News items56

Data as of Fri 9 Oct 2026. Text marked AI was written by the brain from the records listed in its made-from link; an AI output that cannot cite its evidence is refused and the previous text kept. Where two systems disagree (for example a contract and the CRM), the key facts show both values and mark the difference.

B-Brain is a fictional company: every organisation, person and figure here is invented for this demonstration.

Who to contact

Email support@b-brain.example or talk to your B-Brain account team. Tell us the page address and what looked wrong; a screenshot helps.

Ask B

Ask B

B-Brain · read-only