Yusuf Demir

Veldmaat Payments / B-Brain – Onboarding

Callcompleted

Veldmaat Payments: documents logo Veldmaat Payments: documents · 2026-02-12 12:00

Sanne reported a second refresh miss in one week, with part of the HubSpot data stale. Users are being told to wait, and she wants a written yes or no on whether Growth credits these misses.

What was said

What this says

Current to 11 Oct 26

Sanne reported a second refresh miss in one week, with part of the HubSpot data stale. Users are being told to wait, and she wants a written yes or no on whether Growth credits these misses.

What happened: Sanne raised two tickets for refreshes not complete at 07:00. Yusuf confirmed Zendesk loaded late and some HubSpot data was still the previous day's.

Customer view: Account managers asked her whether the numbers were right and she could not say. She told users to wait, which she called not good.

Commercial: Sanne asked whether the misses are credited on Growth, and Yusuf passed the question to the account owner. Growth credits cover availability only unless the executed order form says otherwise, and the evidence does not show those terms.

Watch: A new HubSpot property added the week before may explain the slow export, but Yusuf called it one data point, not an answer.

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

Themes

Current to 9 Oct 26
Theme
Repeat refresh misses, stale data
Importance
complaint
Sentiment
negative
Voice
user

Who was there

B-Brain

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Yusuf writes up the HubSpot slowness with before and after export sizes by end of day tomorrow.
  • Yusuf sets up a morning status line for Sanne saying complete by 07:00 or not, and why.
  • The account owner answers the credit question in writing today, with what the order form says.

Risks

Current to 9 Oct 26
  • A second miss in one week meets the customer's own twice-is-a-problem test and may become a formal complaint.
  • Adoption is stalling because users are told to wait while the data is late.
  • The credit question is unanswered, and Growth credits cover availability only unless the order form says otherwise.

Opportunities

Current to 9 Oct 26
  • A reliable morning status line could rebuild trust and let users return to the brain.

Transcript

  1. Sanne Bakker
    Sanne Bakker None
    Hello. Refresh not complete at 07:00. Again. Twice this week. Two tickets. See ticket from Monday and from this morning.
  2. Yusuf Demir
    Yusuf Demir None
    Hello Sanne. I've got both open. HubSpot connector, last good load was the night before last. Zendesk loaded, but late. This morning's one is still not fully through on my side.
  3. Sanne Bakker
    Sanne Bakker None
    Not fully through. What does that mean. Is the data there or not.
  4. Yusuf Demir
    Yusuf Demir None
    Partly. Zendesk is in. HubSpot returned late, and the load is still working through it. So the brain is up, answering, but some of the HubSpot side is yesterday's.
  5. Sanne Bakker
    Sanne Bakker None
    So stale. Say stale.
  6. Yusuf Demir
    Yusuf Demir None
    Stale on one source, yes. I'd rather say that than dress it up.
  7. Sanne Bakker
    Sanne Bakker None
    Account managers asked me at nine. They asked if the numbers were right. I said I did not know. I do not like to say that.
  8. Yusuf Demir
    Yusuf Demir None
    I understand. That's the part I don't want you carrying. Look, what I know. The source returned slowly on both nights. I've re-run both and told Elena. What I don't yet know is why it's slow on those nights and not the others.
  9. Sanne Bakker
    Sanne Bakker None
    Is it on our side. Did we change something in HubSpot. We did add a property last week.
  10. Yusuf Demir
    Yusuf Demir None
    Possibly. It could be that. A new property can make the export heavier. I'm not going to say it is until I've got the source in hand and can compare. Can you tell me the day you added it, and which object?
  11. Sanne Bakker
    Sanne Bakker None
    Wednesday last week. On companies. A risk rating field, from the merchant team. They fill it by hand.
  12. Yusuf Demir
    Yusuf Demir None
    Right. That's useful. The first late night was the Monday after. That fits, but it's one data point, not an answer. I'll compare the export size before and after, and I'll write it up.
  13. Sanne Bakker
    Sanne Bakker None
    When. You write it up when.
  14. Yusuf Demir
    Yusuf Demir None
    Tomorrow, by the end of the day. I won't say sooner, because I'd have to guess, and I'd rather give you a finding than a guess.
  15. Sanne Bakker
    Sanne Bakker None
    Tomorrow. I write it in my log. Okay.
  16. Sanne Bakker
    Sanne Bakker None
    Next. Service. We are on Growth. Are these misses credited. I need to know what to tell Joost.
  17. Yusuf Demir
    Yusuf Demir None
    That's with Elena, not me. I don't do the commercial side, and I'd be guessing at what the contract says. I'll flag it so she comes back to you in writing today.
  18. Sanne Bakker
    Sanne Bakker None
    Fine. But I want an answer. Not a, we will see.
  19. Yusuf Demir
    Yusuf Demir None
    Understood. I'll say in the note that you want a yes or a no, and what the order form says.
  20. Sanne Bakker
    Sanne Bakker None
    Exact Online. Is it also late now. Because of this.
  21. Yusuf Demir
    Yusuf Demir None
    No. It's separate. I've been waiting on access, and I've got it now, read-only, since Tuesday. I started the first pull yesterday. Row count came back, I'll check it against your sample.
  22. Sanne Bakker
    Sanne Bakker None
    Sample had duplicates. Two records for some merchants. I told Hannah. You saw that.
  23. Yusuf Demir
    Yusuf Demir None
    I saw it. That's the mapping problem, and it's expected. I'll handle it in the mapping, not by deleting anything at the source.
  24. Sanne Bakker
    Sanne Bakker None
    Good. Do not delete anything.
  25. Yusuf Demir
    Yusuf Demir None
    I won't. I never touch the source.
  26. Sanne Bakker
    Sanne Bakker None
    Another thing. Users. Only a few people use it. Because the data was late, I told them wait. That is not good.
  27. Yusuf Demir
    Yusuf Demir None
    No, and I'd say the same. But there's no sense in them waiting for a perfect version. The data is right most mornings. What I can give you is a status line each morning, saying either complete by 07:00, or not and why. Then you're not the one explaining it.
  28. Sanne Bakker
    Sanne Bakker None
    A status line. Yes. That helps. Send to me and to Joost.
  29. Yusuf Demir
    Yusuf Demir None
    I'll set it up and tell Elena I've done it. She'll want to know.
  30. Sanne Bakker
    Sanne Bakker None
    Summary. Say it.
  31. Yusuf Demir
    Yusuf Demir None
    One, I write up the HubSpot slowness tomorrow, with the before and after on the new property. Two, I set up the morning status line to you and Joost. Three, I flag the credit question to Elena, and she answers in writing. Four, Exact Online first pull is done, mapping next, and I'll tell Elena before any re-run.
  32. Sanne Bakker
    Sanne Bakker None
    Okay. That is correct. I will log it.
  33. Yusuf Demir
    Yusuf Demir None
    Thanks, Yusuf.
  34. Sanne Bakker
    Sanne Bakker None
    Sanne.

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