B-Glass
Yusuf Demir

Veldmaat Payments / BG-Demo – Onboarding

Callcompleted

Veldmaat Payments logo Veldmaat Payments · 6 Feb 2026 09:45

On the 6 Feb 2026 onboarding call, Joost Verbeek pressed on repeated late Zendesk refreshes and said the invoice is fifty thousand pounds against forty-five thousand on the order form. Few people use the brain because they distrust stale data.

What was said

What this says

As at Fri 9 Oct 2026

On the 6 Feb 2026 onboarding call, Joost Verbeek pressed on repeated late Zendesk refreshes and said the invoice is fifty thousand pounds against forty-five thousand on the order form. Few people use the brain because they distrust stale data.

What happened: Yusuf Demir's onboarding call with Joost Verbeek and Sanne Bakker opened on the Zendesk refresh missing 07:00 on three mornings. Yusuf had a batching fix tested on a copy and promised to take it live that night, subject to the CSM's yes.

Customer view: Joost called the explanation a description, not a plan, and asked for five business days in a row. He said the account managers wait and he cannot yet vouch for the data.

Commercial: Joost asked for it on record that the invoice is fifty thousand pounds and the order form he signed says forty-five thousand. He wants a written answer; the call does not show who is right or why. Forty licensed users with only a handful active is an adoption gap, not headroom.

Watch: Joost said he would hold BG-Demo to five clean mornings, and the stale-data worry is what keeps the account managers away.

AI · claude-sonnet-5-5 · as at Fri 9 Oct 2026

Themes

As at Fri 9 Oct 2026
Theme
stale data and invoice mismatch
Importance
complaint
Sentiment
mixed
Voice
decision-maker

Who was there

BG-Demo

Them

Follow-up

Next steps

As at Fri 9 Oct 2026
  • Yusuf Demir confirms the live Zendesk batching change to Joost and Sanne by mid-afternoon on the day of the call.
  • Tom and Elena answer the invoice question in writing with Joost copied.
  • Sanne Bakker sends the list of known bad merchant identifiers the same day.

Risks

As at Fri 9 Oct 2026
  • Repeated late Zendesk refreshes against the agreed 07:00 commitment keep account managers away from the brain.
  • The invoice is fifty thousand pounds against forty-five thousand on the signed order form, and Joost wants a written answer.
  • Only a handful of the forty licensed users are active, which weakens the case for renewal.

Opportunities

As at Fri 9 Oct 2026
  • Five clean mornings would let Joost's team tell account managers the data is reliable and widen usage.

Transcript

  1. Sanne Bakker
    Sanne Bakker
    Hello. Can you hear me? I have a bit of an echo.
  2. Yusuf Demir
    Yusuf Demir
    Yes, clear here. Morning, Sanne. Joost's just joining, I can see him in the lobby.
  3. Joost Verbeek
    Joost Verbeek
    Good morning. Sorry, the previous meeting ran over. Are we all here?
  4. Yusuf Demir
    Yusuf Demir
    We are. Thanks for making the time, both of you.
  5. Joost Verbeek
    Joost Verbeek
    So. Before anything else. Were the actions from last time done? I have three written down.
  6. Yusuf Demir
    Yusuf Demir
    Two of three. I'll start with the connector status, then we can go through the list. HubSpot connector, last good load was 06:40 this morning. Row count is up on yesterday, which is what we want.
  7. Sanne Bakker
    Sanne Bakker
    And Zendesk? Refresh not complete at 07:00 again. Monday, Wednesday, and Thursday last week. I have the timestamps in my log.
  8. Yusuf Demir
    Yusuf Demir
    Yes. Zendesk is the one that's open. The source returned a timeout on the large ticket export, so the load stops part way and the nightly job reports it late rather than failed. That's my side to fix.
  9. Joost Verbeek
    Joost Verbeek
    To be honest, that is not a good answer yet. It is a description. What was agreed was a refresh finished by 07:00, every business day. So what is the plan?
  10. Yusuf Demir
    Yusuf Demir
    Fair. The plan is to split the export into smaller batches and start the Zendesk pull earlier in the night, so it doesn't compete with the accounting system load. I've tested the batching on a copy. I haven't put it live.
  11. Sanne Bakker
    Sanne Bakker
    Why not live?
  12. Yusuf Demir
    Yusuf Demir
    Because I want you to see the row counts first, and I want Elena to know before I change the schedule. I don't re-run or reschedule without telling the CSM.
  13. Sanne Bakker
    Sanne Bakker
    Okay. That is reasonable. But again, two tickets are open and both are high priority. I do not want a third.
  14. Yusuf Demir
    Yusuf Demir
    Understood. I've seen both. One is the timeout, the other is the same thing from a different night. I'll link them.
  15. Joost Verbeek
    Joost Verbeek
    Good. Link them. Now, the third action. The accounting system connector. Was the merchant identifier mapping finished?
  16. Yusuf Demir
    Yusuf Demir
    That's the one that's not done. Most merchants match across HubSpot and the accounting system. A group of them don't, because the identifier is stored with a prefix in one and without in the other. I can map it, but I'd want Sanne to confirm which side is the master.
  17. Sanne Bakker
    Sanne Bakker
    The accounting system is the master. HubSpot was typed by hand by account managers, so there are mistakes. I will send you a list of the known bad ones.
  18. Yusuf Demir
    Yusuf Demir
    That helps a lot. If you send it today I can have the mapping in the next load.
  19. Sanne Bakker
    Sanne Bakker
    Today. Yes.
  20. Joost Verbeek
    Joost Verbeek
    Let me say why this matters. The merchant risk team looks at one merchant and wants one picture. If the picture is stale at nine in the morning they go back to the old spreadsheets. And then the brain is not used.
  21. Yusuf Demir
    Yusuf Demir
    Mm. How many people are actually logging in at the moment? I can see it's low, but I don't know who's meant to be on.
  22. Joost Verbeek
    Joost Verbeek
    A handful. You are licensed for forty. We have a few people trying it, mostly in my team. The account managers wait. They ask me if the data is right, and I cannot say yes with a straight face, yet.
  23. Sanne Bakker
    Sanne Bakker
    And I am the one who has to explain stale data to them. I do not want to do this every week.
  24. Yusuf Demir
    Yusuf Demir
    Right. Then the target for me is simple. Zendesk finishing before 07:00 for five business days in a row, with row counts you can check. After that you can tell them it's reliable and not just hope.
  25. Joost Verbeek
    Joost Verbeek
    Five days in a row. Write it down. I will hold you to it.
  26. Yusuf Demir
    Yusuf Demir
    Noted. It's in the follow-up note.
  27. Yusuf Demir
    Yusuf Demir
    Sanne, while we're on, can you share your screen? I'd like to look at the failing export settings together, so I'm not guessing which custom fields you pull.
  28. Sanne Bakker
    Sanne Bakker
    One moment. Sharing now. You see the view?
  29. Yusuf Demir
    Yusuf Demir
    Yes. Scroll down a bit. There. That field, the dispute reason. Is that free text?
  30. Sanne Bakker
    Sanne Bakker
    Free text. Long. Agents paste whole emails in it sometimes.
  31. Yusuf Demir
    Yusuf Demir
    That would explain it. That one field makes the batch heavy. I can truncate it for the index and keep the full text in the source. Would that hurt the risk team?
  32. Sanne Bakker
    Sanne Bakker
    Not if the first part is kept. The reason code is at the top. I will check with them but I think it is fine.
  33. Joost Verbeek
    Joost Verbeek
    Yusuf, one other thing, and I want it recorded in the notes. The invoice we received is for fifty thousand pounds. The order form I signed says forty-five thousand. What was agreed was forty-five. Can someone explain that?
  34. Yusuf Demir
    Yusuf Demir
    I can't, honestly. Pricing isn't something I handle, and I don't want to guess. That's for Tom and Elena. I'll pass it to them today, exactly as you've said it.
  35. Joost Verbeek
    Joost Verbeek
    Please. Forty-five on the order form, fifty on the invoice. I am not angry. But it must be corrected, and I want an answer in writing.
  36. Yusuf Demir
    Yusuf Demir
    Understood. I'll copy you on the message so you can see it went.
  37. Joost Verbeek
    Joost Verbeek
    Good. Thank you.
  38. Yusuf Demir
    Yusuf Demir
    Okay, I've pushed the batching to the test environment and I'm running the Zendesk pull now. It'll take a few minutes. Anything else while we wait?
  39. Sanne Bakker
    Sanne Bakker
    Yes. Who gets notified when it fails? Last time nobody told me. I found out at 07:00 from the empty dashboard.
  40. Yusuf Demir
    Yusuf Demir
    Fair point. At the moment the alert goes to our side only. I'll add you as a recipient, so you hear it from us before you see it.
  41. Sanne Bakker
    Sanne Bakker
    Good. Use my work address.
  42. Yusuf Demir
    Yusuf Demir
    Right. Test pull finished. Row count is complete against the source, no timeout, and it finished well inside the window. That's on the copy. Live is the next step.
  43. Joost Verbeek
    Joost Verbeek
    So when is live?
  44. Yusuf Demir
    Yusuf Demir
    Tonight's load, if Elena's happy. I'll speak to her straight after this call.
  45. Joost Verbeek
    Joost Verbeek
    Tonight. Not this week. Tonight.
  46. Yusuf Demir
    Yusuf Demir
    Tonight, subject to her yes. I'll confirm to you both by mid-afternoon.
  47. Sanne Bakker
    Sanne Bakker
    And I check 07:00 tomorrow and tell you what I see. Plainly.
  48. Yusuf Demir
    Yusuf Demir
    Plainly is what I want.
  49. Joost Verbeek
    Joost Verbeek
    Let me summarise so it is correct. Yusuf sends the confirmation by mid-afternoon. Sanne sends the list of bad merchant identifiers today. The pricing question goes to Tom and Elena, in writing, with me copied. And we want five clean mornings.
  50. Yusuf Demir
    Yusuf Demir
    That's all four. I'll put them in the notes with names against them.
  51. Joost Verbeek
    Joost Verbeek
    Good. We speak again next week, same slot?
  52. Yusuf Demir
    Yusuf Demir
    I'll ask Elena to send the invite.
  53. Sanne Bakker
    Sanne Bakker
    Okay. I send the list now. Bye.
  54. Yusuf Demir
    Yusuf Demir
    Thanks, both. Speak soon.

BG-Demo is a fictional company; every organisation and person here is invented. B-Glass is the tool. Data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Glass 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 B (the speech bubble) in the header, or open the Ask B page. Type a question, or pick one of the suggestions.

What the data covers

DataRecords
Organisations225
People at customers862
BG-Demo staff records (in post and leavers)58
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 AI 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.

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

Who to contact

Email info@b-glass.uk or talk to your B-Glass account team. Tell us the page address and what looked wrong; a screenshot helps.

Help

Ask B

B-Glass · read-only