B-Brain
Yusuf Demir

Veldmaat Payments / BB-Demo – Training

Callcompleted

Veldmaat Payments logo Veldmaat Payments · 2026-03-02 12:15

Yusuf Demir trained Femke Jansen on the merchant view, chat and pinned searches. She said few colleagues use the brain and that two late overnight refreshes are hurting trust. The cause is not yet confirmed.

What was said

What this says

Current to 13 Oct 26

Yusuf Demir trained Femke Jansen on the merchant view, chat and pinned searches. She said few colleagues use the brain and that two late overnight refreshes are hurting trust. The cause is not yet confirmed.

What happened: Yusuf trained Femke on the freshness stamp, chat with sources, saved searches and summary pages. She plans to send a page to a colleague as a test and bring two colleagues to the next session.

Customer view: Femke said only a few people open the brain, though there are forty licences. Twice the refresh finished after 07:00, and she said Sanne Bakker keeps a log and is not happy.

Commercial: Adoption is thin against the licences held, and late refreshes weaken the case for value at renewal. Yusuf did not confirm a cause and would not promise a fix time, so the nightly refresh commitment stays open.

Watch: Yusuf offered a note after each miss and will raise it with Elena Novak, who owns the conversation. The evidence does not show whether that note was agreed.

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

Themes

Current to 9 Oct 26
Theme
Training and late refresh
Importance
complaint
Sentiment
mixed
Voice
user

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Yusuf Demir to send a one-page note on the stamp, sources and pinned searches.
  • Yusuf Demir to raise the post-miss note with Elena Novak the same day.
  • Yusuf Demir to send row counts after the refresh the next day.

Risks

Current to 9 Oct 26
  • Two overnight refreshes finished after 07:00 and the cause is not confirmed.
  • Few colleagues use the brain against forty licences, which weakens the value case.
  • Sanne Bakker is logging misses and is described as unhappy.

Opportunities

Current to 9 Oct 26
  • Femke will bring two colleagues to the next session and share a summary page with merchant risk.
  • Pinned searches and summary pages give account managers and risk one shared picture.

Transcript

  1. Yusuf Demir
    Yusuf Demir None
    Hi Femke, can you hear me alright?
  2. Femke Jansen
    Femke Jansen None
    Yes, hi Yusuf. I hear you. Sorry, one second, I have a merchant chat still open. Okay. Done.
  3. Yusuf Demir
    Yusuf Demir None
    No problem. Let me share my screen. Can you see the merchant view?
  4. Femke Jansen
    Femke Jansen None
    Yes. A bit small.
  5. Yusuf Demir
    Yusuf Demir None
    I'll make it bigger. Right. Before we start, the status. HubSpot connector, last good load was 07:00 today. Zendesk finished a few minutes earlier. Row count is in line with yesterday.
  6. Femke Jansen
    Femke Jansen None
    Okay. Good. Just to be clear, that is today. Because twice last week it was not complete when I sat down.
  7. Yusuf Demir
    Yusuf Demir None
    Yes, I've seen both tickets from Sanne. I'd like to come back to those at the end, if that's alright, and then we can talk about what to do in the meantime. First the training. Elena said you wanted the merchant view and how to ask questions properly.
  8. Femke Jansen
    Femke Jansen None
    Yes please. Honestly, it is only a few of us who open it. We have forty licences and most of my colleagues are still in HubSpot all day. They ask me, can you check, is it the same as HubSpot?
  9. Yusuf Demir
    Yusuf Demir None
    Fair question. So let's start there. Open any merchant. Go on, pick one you know.
  10. Femke Jansen
    Femke Jansen None
    Okay. I take one I spoke to this morning. A webshop, they had a payout question.
  11. Yusuf Demir
    Yusuf Demir None
    Good. Top right of the page there's a freshness stamp. It shows the last good load for each source. If it says today 07:00, you're looking at HubSpot and Zendesk as they were at 07:00.
  12. Femke Jansen
    Femke Jansen None
    So if my colleague changes a contact at nine, I do not see it.
  13. Yusuf Demir
    Yusuf Demir None
    Not until the next nightly refresh. That's by design. The source returned its data overnight and the brain indexes that.
  14. Femke Jansen
    Femke Jansen None
    Mm. Okay. That I can explain. What I cannot explain is when the stamp says yesterday.
  15. Yusuf Demir
    Yusuf Demir None
    And that's worth being straight about. If the stamp says yesterday, the refresh hadn't finished, and you shouldn't give a merchant an answer from that page without checking HubSpot first. I'd rather you did that than trust it.
  16. Femke Jansen
    Femke Jansen None
    Okay. Please say it once more, I will write it down for my colleagues.
  17. Yusuf Demir
    Yusuf Demir None
    Check the stamp first. Today, it's good. Yesterday, treat the page as a hint and confirm in the source.
  18. Femke Jansen
    Femke Jansen None
    Good. Thank you.
  19. Yusuf Demir
    Yusuf Demir None
    Next, the chat. Click the panel on the right. Ask it something you'd normally open three tabs for.
  20. Femke Jansen
    Femke Jansen None
    Hmm. Let me think. Which merchants have an open ticket and a recent change of contact owner?
  21. Yusuf Demir
    Yusuf Demir None
    Go on, type it just like that. Plain words are fine.
  22. Femke Jansen
    Femke Jansen None
    It is thinking. Oh. It gives me a short list. Three merchants, I think. With a sentence for each.
  23. Yusuf Demir
    Yusuf Demir None
    Look at the line under each answer. Those are the sources. Click one.
  24. Femke Jansen
    Femke Jansen None
    It opens the ticket in Zendesk. And the HubSpot record next to it. Oh, that is nice. That saves me the tabs.
  25. Yusuf Demir
    Yusuf Demir None
    That's the main habit I'd suggest. Don't take the sentence, take the sources. If the sources look right, the answer is right.
  26. Femke Jansen
    Femke Jansen None
    And if it looks wrong? Can you check, then?
  27. Yusuf Demir
    Yusuf Demir None
    Yes. Tell me the merchant and what you expected to see. I don't say data is wrong without the source in hand, so a link helps a lot. Then I look at what the source returned.
  28. Femke Jansen
    Femke Jansen None
    Okay. I like that. Short and clear.
  29. Yusuf Demir
    Yusuf Demir None
    Now saved searches. Take the question you just asked, and pin it. Top of the chat, the pin icon. Then it sits on your start page.
  30. Femke Jansen
    Femke Jansen None
    Pinned. And can I do the same for a ticket priority? I want all high priority tickets for my merchants in the morning.
  31. Yusuf Demir
    Yusuf Demir None
    Yes. Ask for your merchants by name or by portfolio, add high priority, and pin that too. You'll see it first thing, as long as the refresh has finished.
  32. Femke Jansen
    Femke Jansen None
    Yes. That is the as long as. This merchant is waiting, and I open the page at eight and it says yesterday. Then I look stupid in front of the merchant.
  33. Yusuf Demir
    Yusuf Demir None
    Understood. So, the two misses. Both times the overnight run finished after 07:00. I've re-run it each time and told Elena. I'm still looking at why it finishes late on those days. I don't have the cause confirmed, and I won't guess.
  34. Femke Jansen
    Femke Jansen None
    Okay. Sanne keeps a log. She says again, again. She is not happy, and honestly I understand her.
  35. Yusuf Demir
    Yusuf Demir None
    Fair. Her tickets are good, they have timestamps, which makes my job easier. What I can do is send a note after each miss, to you, Sanne and Elena, with the time of the last good load and the row count. So you know before you open the page.
  36. Femke Jansen
    Femke Jansen None
    That would help. A message before eight, yes? Please.
  37. Yusuf Demir
    Yusuf Demir None
    I'll raise it with Elena today, as she owns that conversation with you. I won't promise a time that I can't keep.
  38. Femke Jansen
    Femke Jansen None
    Okay. That is honest.
  39. Yusuf Demir
    Yusuf Demir None
    One more feature while we have time. Pages. Pick a merchant and ask the brain to build a summary page: recent tickets, contact owner, last change. You can share the link with merchant risk.
  40. Femke Jansen
    Femke Jansen None
    Okay, I try. Oh. It builds the page. That is fast. And merchant risk sees the same thing?
  41. Yusuf Demir
    Yusuf Demir None
    Same page, same stamp. That's the point of it. Account managers and risk looking at one picture.
  42. Femke Jansen
    Femke Jansen None
    Good. Then I send this to my colleague today, as a test.
  43. Yusuf Demir
    Yusuf Demir None
    Right. Anything else you want to try while I'm sharing?
  44. Femke Jansen
    Femke Jansen None
    No, I think that is enough for me. I will ask two colleagues to join the next session. Then it is not only me.
  45. Yusuf Demir
    Yusuf Demir None
    Good. I'll send you a short written note after this: how to read the stamp, how to open the sources, how to pin a search. Elena will have it too.
  46. Femke Jansen
    Femke Jansen None
    Thank you, Yusuf. Please keep it short. Then they read it.
  47. Yusuf Demir
    Yusuf Demir None
    One page. And tomorrow I'll send the row counts after the refresh. Thanks, Femke.
  48. Femke Jansen
    Femke Jansen None
    Groeten, Femke. I mean, bye, Yusuf. Talk soon.

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