Veldmaat Payments / B-Brain – Training
Callcompleted
Veldmaat Payments: documents · 2026-03-02 12:15
Second training with Femke Jansen. The status mapping fix held for Friday's change, mornings have been clean, but the Zendesk connector misses updates to existing tickets. A fix is planned for test then live.
What was said
What this says
Current to 10 Oct 26Second training with Femke Jansen. The status mapping fix held for Friday's change, mornings have been clean, but the Zendesk connector misses updates to existing tickets. A fix is planned for test then live.
What happened: Yusuf Demir confirmed several clean morning loads and the corrected status mapping. Femke Jansen checked records herself and then learned the timeline view.
Customer view: She liked the timeline of tickets, calls and status, saying she knew the story but not in order. She still uses HubSpot for a merchant on the phone, since the brain is a nightly picture.
Commercial: A colleague wants a login and Femke asked who handles it. Yusuf pointed her to Sanne, the admin, which may be a small user-growth signal against forty licensed users.
Watch: Two tickets solved at the weekend still showed open, so the connector only picks up new tickets. Yusuf planned a sandbox test the next day and live the day after.
Themes
Current to 9 Oct 26Who was there
B-Brain
Them
Follow-up
Next steps
Current to 9 Oct 26- Yusuf Demir to test the connector change in the sandbox load, then take it live if correct, telling Elena first.
- Femke Jansen to ask Sanne, copying Elena, about a login for her colleague.
- Yusuf Demir to send Femke the short steps again.
Risks
Current to 9 Oct 26- The Zendesk connector does not pick up updates to existing tickets, so the brain shows solved tickets as open.
- Femke still relies on HubSpot for live work, which limits trust in the brain.
Opportunities
Current to 9 Oct 26- The timeline of tickets, calls and status is useful to Femke and to her risk colleagues.
- A colleague has asked for a login, which may add users on the forty licensed.
Transcript
Yusuf Demir NoneHello, Femke. Can you hear me? Zendesk connector, last good load this morning, before seven. HubSpot the same. Accounting extract finished on time as well. That's a few mornings in a row now.
Femke Jansen NoneHello. Yes, I hear you. Sanne said the same. Good. Just to be clear, I still have the status issue from last time. A merchant I changed in HubSpot, and the brain showed the old one.- Yusuf Demir NoneYes. I looked at it. The field was reading the previous value because of how the change history is stored. I've re-run it with the corrected mapping and told Elena. The source returned under review, the brain now shows under review. I've checked three records by hand.
- Femke Jansen NoneThree is not many.
- Yusuf Demir NoneNo. So today let's check a few more together, then go on with the next part of training. You choose the merchants.
- Femke Jansen NoneOkay. One I changed on Friday. One I changed this morning. One I did not change. Here. Friday one is right. The one from this morning, still the old status.
- Yusuf Demir NoneThis morning's change is after the last load, so it won't be in until tomorrow. That's the refresh cycle, it's nightly. It's not the mapping.
- Femke Jansen NoneOh. Yes. Of course. Nightly. But then for a merchant on the phone right now, I still use HubSpot.
- Yusuf Demir NoneYes. The brain is the whole picture, the morning picture. HubSpot is the live record. I'd say that to everyone on the team.
- Femke Jansen NoneI'll tell them. Can we do the thing you promised? Asking about history. How long a merchant has been having trouble.
- Yusuf Demir NoneYes. Open a merchant. Ask: show tickets and status changes for this merchant over time. Don't say a date, say 'since they joined'.
- Femke Jansen NoneThere is a timeline. Tickets, calls, status. This is nice. I see they started with delayed payouts, then the refund disputes, then the status change. I knew the story but not in order.
- Yusuf Demir NoneThat's what your risk colleagues will want too. Same timeline, same source.
- Femke Jansen NoneThere's a call in the timeline from the call recorder. Is that ours?
- Yusuf Demir NoneIt's your call recording, via the call recorder connector. Only the summary shows unless you have permission for the full text. I'll check who has that with Sanne.
- Femke Jansen NoneCan you check something else? Zendesk. Two tickets on our side, still marked open, but the merchant told me they are done.
- Yusuf Demir NoneLet me look at the source. Give me a minute.
- Yusuf Demir NoneThe source returned both as solved at the weekend. The brain has them open. So that's the same pattern as the status: it's behind on updates to existing records, not on new ones. I think the connector only picks up new tickets and changes in some fields.
- Femke Jansen NoneSo what is the plan?
- Yusuf Demir NoneI'll change the connector to read updated tickets as well as new ones. I need to test it in the sandbox load first. I'll tell Elena before I run anything on the live data.
- Femke Jansen NoneWhen?
- Yusuf Demir NoneTest tomorrow. If it's right, live the day after. I'll confirm by message.
- Femke Jansen NoneOkay. Meanwhile, can I put the saved views in a folder? I have six of them now.
- Yusuf Demir NoneYes. Drag them. Name them by what you ask, not by merchant.
- Femke Jansen NoneLast thing, and I'm sorry if this is not for you. A colleague asked if she can have a login. We have forty licensed. Who do I ask?
- Yusuf Demir NoneSanne adds users, she's the admin. I don't handle licences. Ask her, and copy Elena.
- Femke Jansen NoneGood. Thank you, Yusuf. Please send me the short steps again. Groeten, Femke.
- Yusuf Demir NoneWill do. Thanks, Yusuf.