Yusuf Demir

Veldmaat Payments / B-Brain – Onboarding

Callcompleted

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

Joost Verbeek and Sanne Bakker raised a first refresh that missed 07:00 and a Zendesk connector not yet live. Yusuf Demir said the load was a heavy initial pull and would not promise it will not recur until he has more nights of data.

What was said

What this says

Current to 10 Oct 26

Joost Verbeek and Sanne Bakker raised a first refresh that missed 07:00 and a Zendesk connector not yet live. Yusuf Demir said the load was a heavy initial pull and would not promise it will not recur until he has more nights of data.

What happened: Yusuf walked through HubSpot, where companies and contacts loaded well but some deals have no company. Zendesk failed on an authorisation error because the user lacks access to ticket comments.

Customer view: Joost accepted the late refresh as an initial load, but wants assurance it will not recur. He also noted that Zendesk was not live, though agreed for the first weeks.

Commercial: Nothing on price or renewal was raised. The tone is patient but watching delivery against what was agreed.

Watch: Yusuf would not promise future refresh times. Who sees what in the brain is open, and goes to Hannah.

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

Themes

Current to 9 Oct 26
Theme
First refresh and Zendesk delay
Importance
neutral
Sentiment
mixed
Voice
decision-maker

Who was there

B-Brain

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Yusuf sends the deals count and record list by email the same day.
  • Sanne fixes the Zendesk role, then Yusuf re-runs the load and tells Elena first.
  • Yusuf reports the finish time of the next incremental refresh to Joost and Sanne, not only in the ticket.

Risks

Current to 9 Oct 26
  • The first refresh missed 07:00 and Yusuf could not promise it will not recur until he has a few nights of data.
  • The Zendesk connector was not live at this call, and Joost has noted the first-weeks commitment.
  • Access rules between merchant risk and account managers are undecided and depend on a design answer from Hannah.

Opportunities

Current to 9 Oct 26
  • Role-based access across the Exact data and account manager groups shows the brain can fit how Veldmaat's teams work.

Transcript

  1. Yusuf Demir
    Yusuf Demir None
    Morning. Yusuf here. Can you hear me?
  2. Sanne Bakker
    Sanne Bakker None
    Yes. Morning.
  3. Joost Verbeek
    Joost Verbeek None
    Good morning Yusuf. Give me a moment, I am just moving to a quieter room. Okay. Yes, I hear you.
  4. Yusuf Demir
    Yusuf Demir None
    Right. HubSpot connector. Last good load was last night, finished a little before six. Row count is healthy on companies and contacts. Deals I'll come to.
  5. Joost Verbeek
    Joost Verbeek None
    First, were the last actions done? Elena sent a list after the kickoff.
  6. Sanne Bakker
    Sanne Bakker None
    Mine are done. Snowflake details sent. Exact Online administrations listed. Three are live, two are old.
  7. Joost Verbeek
    Joost Verbeek None
    And I confirmed with merchant risk. They use two of the three live ones. I sent that by email on Tuesday.
  8. Yusuf Demir
    Yusuf Demir None
    Got it. I have both. Thanks. That makes the mapping smaller.
  9. Yusuf Demir
    Yusuf Demir None
    So today I wanted to do three things. Walk through what has loaded from HubSpot. Look at the Zendesk credentials, which are not working yet. And talk about the ticket Sanne raised.
  10. Sanne Bakker
    Sanne Bakker None
    Ticket from Monday. Refresh not complete at 07:00. Status page said still running at 07:00. Finished later.
  11. Yusuf Demir
    Yusuf Demir None
    Yes, I have seen it. The source returned a lot more history on the first full pull than I expected. The initial load is heavy. It is a one-off. Nightly changes are small.
  12. Joost Verbeek
    Joost Verbeek None
    So it was an initial load. To be honest, I accept that for the first run. But I want to know it will not happen again.
  13. Yusuf Demir
    Yusuf Demir None
    I can't promise anything about the future until I have a few nights of data. What I can say is tonight's run is incremental only. I will check it and tell you the finish time tomorrow.
  14. Joost Verbeek
    Joost Verbeek None
    Tell me, and Sanne. Not only in the ticket.
  15. Yusuf Demir
    Yusuf Demir None
    Will do. Okay, deals. Row count is lower than I'd expect, and the reason is that some deals have no company attached in HubSpot. They load, but they do not join to a merchant.
  16. Sanne Bakker
    Sanne Bakker None
    Known. Old deals. Created by import. No company.
  17. Joost Verbeek
    Joost Verbeek None
    How many?
  18. Yusuf Demir
    Yusuf Demir None
    I'd rather not give you a number from memory. I'll send the exact count by email today with a list of the records.
  19. Joost Verbeek
    Joost Verbeek None
    Good. Send it. Then Sanne decides whether to clean or ignore.
  20. Sanne Bakker
    Sanne Bakker None
    Ignore if old. I will check the dates.
  21. Yusuf Demir
    Yusuf Demir None
    Fine. Next, Zendesk. I tried the credentials Sanne sent. The source returned an authorisation error. Looks like the API token is valid but the user has no access to the ticket comments.
  22. Sanne Bakker
    Sanne Bakker None
    Agent role is light. Not admin. I will change it.
  23. Yusuf Demir
    Yusuf Demir None
    A read-only role with access to tickets and comments is enough. It does not need to be admin.
  24. Joost Verbeek
    Joost Verbeek None
    Sanne, do it today. Please.
  25. Sanne Bakker
    Sanne Bakker None
    After this call. Ten minutes.
  26. Yusuf Demir
    Yusuf Demir None
    Then I'll re-run the Zendesk load this afternoon, and I'll tell Elena before I do, because she wants to be informed on every run during onboarding.
  27. Joost Verbeek
    Joost Verbeek None
    Good. Elena has the full plan. What was agreed was the Zendesk connector in the first weeks. I note it was not live today.
  28. Yusuf Demir
    Yusuf Demir None
    Understood. It is within the first weeks still. I'll say plainly if that changes.
  29. Sanne Bakker
    Sanne Bakker None
    Also, who can see what in the brain? Merchant risk should see Exact data. Account managers should not see everything.
  30. Yusuf Demir
    Yusuf Demir None
    That is a design question for Hannah. I'll pass it on today so it's in writing. I only build the loads.
  31. Joost Verbeek
    Joost Verbeek None
    Please. I will send the names for each group, but I need Hannah to say what is possible before.
  32. Yusuf Demir
    Yusuf Demir None
    Noted. Summary from my side. One, I send the deals count and list today. Two, Sanne fixes the Zendesk role, I re-run and tell Elena first. Three, I report the finish time of tonight's refresh tomorrow. Four, the access question goes to Hannah.
  33. Joost Verbeek
    Joost Verbeek None
    Correct. I will write it down. Thank you Yusuf.
  34. Yusuf Demir
    Yusuf Demir None
    Thanks, Yusuf. Sorry, thanks all. Speak soon.
  35. Sanne Bakker
    Sanne Bakker None
    Bye.

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