B-Brain
Yusuf Demir

Veldmaat Payments / BB-Demo – Onboarding

Callcompleted

Veldmaat Payments logo Veldmaat Payments · 2026-01-22 08:00

Veldmaat Payments raised a refresh that was not complete by 07:00 on Tuesday and was late again on Wednesday. Joost Verbeek asked for it to be recorded. Exact Online is still waiting on the read-only user.

made from

What was said

What this says

Current to 13 Oct 26

Veldmaat Payments raised a refresh that was not complete by 07:00 on Tuesday and was late again on Wednesday. Joost Verbeek asked for it to be recorded. Exact Online is still waiting on the read-only user.

What happened: Yusuf Demir explained that Tuesday's contacts pull hit source errors and finished after seven. The data was correct after a re-run but late. The cause of Wednesday's delay is not yet known.

Customer view: Joost said late is the problem, because the account managers open the brain at eight. He wants the seven o'clock commitment recorded and asked that Tuesday not happen again.

Commercial: This is the first ticket three weeks in, and Joost will use the log at the QBR. He is holding back the account managers until the Zendesk data is checked.

Watch: Exact Online has not started. Joost will ask Elena for the early March date on paper.

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

AImade from

Themes

Current to 9 Oct 26
Theme
Missed nightly refresh
Importance
complaint
Sentiment
negative
Voice
decision-maker
AImade from

Who was there

BB-Demo

CRMmade from

Them

CRMmade from

Follow-up

Next steps

Current to 9 Oct 26
  • Yusuf Demir starts the nightly job earlier and adds page-level retry after testing.
  • Sanne Bakker sends her timestamped log for Wednesday and updates the Zendesk identifiers.
  • Elena Novak confirms the Exact Online date to Joost Verbeek in writing.
AImade from

Risks

Current to 9 Oct 26
  • Two late refreshes in the first weeks against the 07:00 commitment, with the Wednesday cause unknown.
  • Exact Online cannot start until the read-only user is approved, putting the early March date at risk.
  • Zendesk organisations without a merchant identifier will not attach to a merchant until fixed at source.
AImade from

Opportunities

Current to 9 Oct 26
  • A status query in the customer's Snowflake account gives Sanne Bakker a way to confirm each load without counting rows by hand.
AImade from

Transcript

  1. Yusuf Demir
    Yusuf Demir None
    Morning. Yusuf here. Can you hear me? Good. I'll start with the state of play. HubSpot connector, last good load finished at 06:40 this morning. Zendesk connector is built, not yet scheduled.
  2. Sanne Bakker
    Sanne Bakker None
    Morning. Again, I need to say it. Refresh not complete at 07:00 on Tuesday. See ticket from Tuesday. And it was late on Wednesday too.
  3. Joost Verbeek
    Joost Verbeek None
    Hello Yusuf. Before we go on. Were the actions from the kickoff done? I have two on my list.
  4. Yusuf Demir
    Yusuf Demir None
    From my side, yes. Sanne sent the samples, and I've used them to build the mapping for the merchant identifier. The invoice question is with Elena, not me. I don't touch that.
  5. Joost Verbeek
    Joost Verbeek None
    Fine. Elena wrote to me about it already. So. Tuesday.
  6. Yusuf Demir
    Yusuf Demir None
    Tuesday. The source returned errors on the contacts pull. The job retried, then ran out of its window. It finished after seven. I've re-run it, and I told Elena at the time.
  7. Sanne Bakker
    Sanne Bakker None
    You re-ran at what time?
  8. Yusuf Demir
    Yusuf Demir None
    Just after half past seven. Row count matched the source after the re-run. I checked it against the export you sent.
  9. Joost Verbeek
    Joost Verbeek None
    So the data was right, but late.
  10. Yusuf Demir
    Yusuf Demir None
    Right but late. Yes.
  11. Joost Verbeek
    Joost Verbeek None
    To be honest, late is the problem. The account managers open it at eight. So what is the plan?
  12. Yusuf Demir
    Yusuf Demir None
    Two changes. First, the nightly job starts earlier, so there is room for a retry before seven. Second, a failed page is retried on its own, not the whole pull. I'll make the first change today. The second one needs a test, so I'd say a couple of days.
  13. Sanne Bakker
    Sanne Bakker None
    And Wednesday? It was not the same error.
  14. Yusuf Demir
    Yusuf Demir None
    No. Wednesday I don't know yet. The log shows the load started on time and then waited. I don't want to guess without the source side. Do you have the source timings from your end?
  15. Sanne Bakker
    Sanne Bakker None
    I have my own log. I will send it. Timestamps for each morning.
  16. Yusuf Demir
    Yusuf Demir None
    That would help. Thanks.
  17. Joost Verbeek
    Joost Verbeek None
    Let me be direct. We are three weeks in and the first ticket is a missed refresh. What was agreed was a refresh by seven. I want that recorded.
  18. Yusuf Demir
    Yusuf Demir None
    It's recorded. I've put it in the ticket, and Elena has it. I won't argue with it. The commitment is seven.
  19. Joost Verbeek
    Joost Verbeek None
    Good. Then we move on.
  20. Yusuf Demir
    Yusuf Demir None
    Zendesk next. The connector pulls tickets and organisations. The mapping uses the merchant identifier on the organisation. In the sample, a fair number of organisations had that field empty.
  21. Sanne Bakker
    Sanne Bakker None
    Yes. Older merchants. Support never filled it in.
  22. Yusuf Demir
    Yusuf Demir None
    Then those tickets will not attach to a merchant. I'd rather list them than guess a match by name. I can give you the list of organisations without an identifier.
  23. Joost Verbeek
    Joost Verbeek None
    Do that. Sanne will fix them at source. I do not want a name match that is wrong. A wrong merchant on a risk page is worse than an empty one.
  24. Sanne Bakker
    Sanne Bakker None
    Send the list. I can bulk update in Zendesk. I will need a day.
  25. Yusuf Demir
    Yusuf Demir None
    I'll send it this afternoon. After your update I run the Zendesk load and tell you the row count.
  26. Joost Verbeek
    Joost Verbeek None
    Now Exact Online. Where are we?
  27. Yusuf Demir
    Yusuf Demir None
    Not started on my side. I'm waiting for the read-only user. Without it there is nothing to connect to. Sanne, where is that?
  28. Sanne Bakker
    Sanne Bakker None
    Finance approved in principle. They want the list of what the user can see. I have it half written.
  29. Yusuf Demir
    Yusuf Demir None
    I can write that list. It is a short one. Invoices, customers, payments. Nothing else.
  30. Joost Verbeek
    Joost Verbeek None
    And the date is still the Friday in early March?
  31. Yusuf Demir
    Yusuf Demir None
    From the engineering side, yes, if I have the user in the next couple of weeks. I won't say more than that. Elena owns the commitment, and she will confirm in writing.
  32. Joost Verbeek
    Joost Verbeek None
    Fine. Never accept a vague timeline from me, so I will ask Elena for it on paper.
  33. Yusuf Demir
    Yusuf Demir None
    That's fair.
  34. Sanne Bakker
    Sanne Bakker None
    A practical thing. How do I know in the morning that the load was complete? I do not want to count rows by hand.
  35. Yusuf Demir
    Yusuf Demir None
    Each load writes a status line with the start, the end and the row count. It sits in a table in your Snowflake account. I can give you a query that shows the last good load per connector.
  36. Sanne Bakker
    Sanne Bakker None
    Yes. Send it. That replaces half my log.
  37. Joost Verbeek
    Joost Verbeek None
    Keep the log anyway. For the QBR.
  38. Sanne Bakker
    Sanne Bakker None
    I will.
  39. Joost Verbeek
    Joost Verbeek None
    Users. We have forty licensed. At the moment it is me and Sanne, and a few clicks from a colleague. I will not bring in the account managers until the Zendesk side is checked.
  40. Yusuf Demir
    Yusuf Demir None
    Sensible. I'd tell you when the Zendesk data is clean. That's my call to make with the row counts in hand.
  41. Joost Verbeek
    Joost Verbeek None
    Good. So, summary please.
  42. Yusuf Demir
    Yusuf Demir None
    HubSpot job starts earlier from today. Page-level retry in a couple of days, tested first. Sanne sends her log for Wednesday. I send the list of Zendesk organisations without an identifier this afternoon. I write the permission list for the Exact Online user. And I send Sanne the status query. All of that goes to Elena in writing today.
  43. Sanne Bakker
    Sanne Bakker None
    Okay. Nothing to add.
  44. Joost Verbeek
    Joost Verbeek None
    Nothing from me. Thank you, Yusuf. Please do not let Tuesday happen again.
  45. Yusuf Demir
    Yusuf Demir None
    Understood. I'll watch it every morning this week. Thanks, Yusuf.
  46. Sanne Bakker
    Sanne Bakker None
    Bye.
  47. Joost Verbeek
    Joost Verbeek None
    Met vriendelijke groet.
Callsmade from

BB-Demo is a fictional company; every organisation and person here is invented. B-Brain is the tool. 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
Organisations225
People at customers862
BB-Demo staff58
Calls1,995
Email threads3,013
Support tickets1,159
Documents1,218
Deals315
Invoices285
Events49
News items119

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.

BB-Demo is a fictional company: every organisation, person and figure here is invented for this demonstration. B-Brain is the tool that reads its data.

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

Ask B

B-Brain · read-only