What was said
What this says
As at Fri 9 Oct 2026Demo on a sample of Haverkamp's data. The works council chair Lars Wübbena asked whether the audit log could be used to monitor staff. Pseudonymising users in the log is unconfirmed. A decision date of 12 May 2026 stays the reference.
What happened: Theo Gallagher demoed the brain on a sample of Haverkamp data from the CRM, two shared mailboxes and the helpdesk. Lars Wübbena, the Works Council Chair, asked whether it could show which key-account manager answered slowly.
Customer view: Lars set a firm rule that no tool may monitor employee performance or behaviour. He asked for a German document covering connected data, roles, retention and log contents, plus a statement that HR data is out of scope.
Commercial: Single sign-on was shown as part of the Enterprise tier. Stefan Meyerhoff will speak with the budget holder and IT, and the council only sees the document when it is ready.
Watch: Theo could not confirm that the user column can be pseudonymised and must check with the platform team. Stefan wants firm dates, and Matteo Ricci has not yet promised a date for the translation.
Themes
As at Fri 9 Oct 2026Who was there
BG-Demo
Them
Follow-up
Next steps
As at Fri 9 Oct 2026- Theo Gallagher to send a control-by-control description and the answer on log pseudonymisation.
- Matteo Ricci to send a written summary with timing and arrange the German translation.
- Stefan Meyerhoff to speak with the budget holder and IT before the works council reviews the document.
Risks
As at Fri 9 Oct 2026- The works council could block adoption if the question log is seen as a way to monitor staff.
- Pseudonymising users in the log is unconfirmed and waits on the platform team.
- Stefan wants firm dates and none have yet been committed for the document or translation.
Opportunities
As at Fri 9 Oct 2026- Enterprise tier fit through single sign-on and role-based access for key-account managers.
- Stefan sees value in surfacing renewal dates beside complaint trends that he currently sees too late.
Transcript
- Matteo RicciGood afternoon, everyone. Stefan, hello, and Lars, welcome. Can you both hear us?
- Lars WübbenaGood afternoon. Yes, I hear you. I am in the meeting room next to the dispatch hall, so if you hear a truck, it is not me.
- Stefan MeyerhoffHello Matteo, hello Theo. Thank you for coming back to us. I have an agenda, if I may. First the demo with our own data. Second, questions from Lars. Third, what we do next, step by step.
- Matteo RicciPerfect, that is our agenda too. Just so everyone is aligned, the working date for a decision is still 12 May 2026, and today is about letting you see the brain and judge it for yourselves. Theo will drive, and I will keep us on time. Theo, please.
- Theo GallagherThanks, Matteo. Before I share my screen, three things so you know exactly what you are looking at. One, this is a sample of your data that Stefan's colleagues in the data team prepared, not a live connection. Two, the sources shown are the CRM, a set of mailboxes with agreed addresses only, and the helpdesk. Three, nothing here is a finished configuration. It is a demonstration.
- Lars WübbenaThank you. That is useful. Which mailboxes?
- Theo GallagherShared account mailboxes for two brand clients, nothing personal. I will show you in a moment where that is set, so you can see it is a choice made by your side.
- Stefan MeyerhoffGood. Please start with a brand. Pick the one with the most trouble, that is more honest.
- Theo GallagherRight. I will ask in plain language. Give me the history of this brand client over the last year, with open complaints and the renewal date. And there. Let me read what came back, rather than just scroll.
- Theo GallagherIt gives a short summary, then three open complaints from the helpdesk, a note that volume has dropped over two quarters, and the renewal date from the CRM. Each statement has a source link. Stefan, if I click this one, you see the original ticket.
- Stefan MeyerhoffMm. So this is the five minutes I told you about. A manager returning from holiday sees this. What does the client see? The client gets an answer with the facts.
- Matteo RicciAnd that last point matters, Stefan. The renewal date and the volume trend sit side by side. Today you said that is the signal you see too late.
- Stefan MeyerhoffYes. Theo, can you ask it which brands renew soonest and have unresolved complaints?
- Theo GallagherYes. One moment. It returns a short list, ordered by renewal date, with the complaints beside each. I want to be careful here: it ranks brand accounts, not people. It reads what is in the data, and where the data is thin, it says so. See this line, it states it found no call recordings for this client, so the picture is incomplete.
- Lars WübbenaMay I ask a question now? This is the point for me. If it ranks accounts, can it also tell you which key-account manager answered slowly, or who asked the most questions?
- Theo GallagherThat is the right question, and I will answer in order. First, the brain records the questions asked, in an audit log, because we need that for security. Second, who can read that log is a setting. By default it is administrators only. Third, we can evidence that. I can show you the setting and the log view now, if you like.
- Lars WübbenaPlease. Yes.
- Theo GallagherHere. This is the administrator view. You see the questions, the time, and the user. Your administrators decide who has this role. If the works council agreement says the log may only be used for security incidents, that is a policy you set, and the access role follows it.
- Lars WübbenaAnd can the user column be left out? Only the question, no name?
- Theo GallagherI do not want to overstate this. I know the log view can be restricted by role. Whether the user can be pseudonymised in the log itself, I need to check with our platform team before I say yes. I will not answer that from memory.
- Matteo RicciLet me add: I would rather you heard it from us that this is open, than assumed it was solved. We will confirm in writing, with the platform team's answer.
- Lars WübbenaGood. That is honest. I prefer that. Our rule is simple. No tool may be used to monitor performance or behaviour of employees. If it can be misused, we need to know how it is prevented, not only that it is forbidden.
- Stefan MeyerhoffAnd this is why I asked for Lars today. We must involve the works council, and not only at the end. Lars, what would you need from BG-Demo to take this forward?
- Lars WübbenaA document. What is connected, which categories of data, who has which role, how long things are kept, and what the log contains. In German, if possible. Then my colleagues and I can read it properly. And a statement that HR data is not in scope.
- Theo GallagherI can prepare that as a control-by-control description with a reference for each item. Connectors are chosen by the customer, so excluding HR data is a matter of not connecting it. I will mark clearly which items are confirmed and which are waiting on the platform team. A translation I would need to ask Matteo about.
- Matteo RicciWe can arrange the translation. I will confirm the timing when I have the draft, and I will not promise a date before our team has agreed it.
- Stefan MeyerhoffFine. But I need dates in the end, Matteo. Not vague.
- Matteo RicciUnderstood, and you will get them. Theo, can we show one more thing? Stefan asked at the first call about renewals, and sign-on.
- Theo GallagherYes. Single sign-on is part of the Enterprise tier, so access follows your existing identity setup and leavers lose access when their account is closed. I will show the role screen. Here, the roles are administrator, builder and reader. A key-account manager is a reader by default.
- Lars WübbenaGood. That is clearer than I expected. I still want to read the document before I say anything to my colleagues.
- Stefan MeyerhoffOf course. So, to summarise, step by step. Theo sends the description and the answer on the log. Matteo sends a written summary and the timing. I speak with the budget holder and with IT, and Lars brings it to the council when the document is ready.
- Matteo RicciThat is exactly right. And the decision date of 12 May 2026 stays the reference, though we will not rush the council. Thank you both. This was a good, direct conversation.
- Lars WübbenaThank you. Goodbye.
- Stefan MeyerhoffThanks everyone. Beste Grüße, and speak soon.