B-Brain
Laura Penhaligon

Kaltenbrunn Medizintechnik / BB-Demo – Onboarding

Callcompleted

Kaltenbrunn Medizintechnik logo Kaltenbrunn Medizintechnik · 2026-06-23 09:45

Onboarding call on 23 Jun 2026. CRM and helpdesk are loading, the device data is still behind, and a duplicate-ticket fix awaits checking. Christina Möller set a training order and a first test question.

What was said

What this says

Current to 13 Oct 26

Onboarding call on 23 Jun 2026. CRM and helpdesk are loading, the device data is still behind, and a duplicate-ticket fix awaits checking. Christina Möller set a training order and a first test question.

What happened: Laura reported the CRM and helpdesk connectors loading and the service database still behind, because IT gave access only at the end of the previous week. A duplicate-ticket defect from renamed statuses was addressed and is to be checked by Kai.

Customer view: Christina pressed for confirmation rather than assurance and wants fixes verified. She named a first test question on service visits that comes from complaints, which takes her team half a day today.

Commercial: The Enterprise order form promises the installed base, so the device load is the value gate. Christina wants training for team leads first, then key accounts, then engineers, across 150 licences.

Watch: The device load estimate is Laura's, not a promise, and single sign-on is not yet confirmed as switched on. Two security follow-up questions are still to come.

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

Themes

Current to 9 Oct 26
Theme
Onboarding connectors and training
Importance
neutral
Sentiment
neutral
Voice
decision-maker

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Laura Penhaligon confirms the device load status on Thursday and prepares the team lead session.
  • Kai Petersen checks the duplicate tickets tomorrow and tests single sign-on today.
  • Christina Möller sends the minutes and two security questions, and Laura turns them round quickly.

Risks

Current to 9 Oct 26
  • The device data, which the customer cares about most, is not yet loaded and its timing is only an estimate.
  • Single sign-on is not yet confirmed as switched on.
  • The duplicate-ticket fix is unverified until Kai counts the duplicates.

Opportunities

Current to 9 Oct 26
  • A closed-case hospital test lets the brain prove its answers against the complaint file.
  • A phased training plan across 150 licences can build wide adoption.

Transcript

  1. Christina Möller
    Christina Möller None
    Good morning, Laura. Am I first?
  2. Laura Penhaligon
    Laura Penhaligon None
    Morning Christina, you are, I've only just got my headset on. Can you hear me?
  3. Christina Möller
    Christina Möller None
    Yes, clear. The rain in Hamburg is very loud today, so if the sound drops it is the window.
  4. Laura Penhaligon
    Laura Penhaligon None
    Ha, understood. It's grey here too. Hello Kai.
  5. Kai Petersen
    Kai Petersen None
    Hello, hello. Sorry, I was fixing a ticket. Is it okay if I stay on after my screen share? I may get pulled away.
  6. Christina Möller
    Christina Möller None
    It is fine. Agenda is short today, I sent it yesterday. One, status of the connectors. Two, the ticket Kai raised. Three, the hospital test. Four, who is trained and when. Then the minutes.
  7. Laura Penhaligon
    Laura Penhaligon None
    Good. Connectors, then. The CRM and the helpdesk are both loading now, and records are coming through every night. The service database is the one that's behind, because IT only gave us access at the end of last week.
  8. Christina Möller
    Christina Möller None
    Which means, in plain words, what can we ask today?
  9. Laura Penhaligon
    Laura Penhaligon None
    Today you can ask about accounts, contracts and tickets for any hospital. You can't yet ask which exact devices are installed where, because that sits in the service database, and the first load of that is still running.
  10. Kai Petersen
    Kai Petersen None
    Which is the part we care most about, of course.
  11. Laura Penhaligon
    Laura Penhaligon None
    It is, yes. Sorry, I'd rather say it straight. I'd expect it to be loaded in a couple of days, and I'll tell you when it is rather than you finding out.
  12. Christina Möller
    Christina Möller None
    What is the source of that estimate? Is it a guess?
  13. Laura Penhaligon
    Laura Penhaligon None
    Fair question. It's based on how long the same kind of load took for the helpdesk, scaled by the size of your device tables. So an estimate, not a promise. I'll confirm on Thursday where it stands.
  14. Christina Möller
    Christina Möller None
    Good. Thursday, I note it.
  15. Laura Penhaligon
    Laura Penhaligon None
    Kai, your ticket. I saw it come in as high priority. Do you want to talk us through it?
  16. Kai Petersen
    Kai Petersen None
    Yes. After the first helpdesk load, some tickets showed up twice. Same ticket number in two rows, with slightly different status. I thought it might be that we changed a status name last month, so the connector sees an old and a new version.
  17. Laura Penhaligon
    Laura Penhaligon None
    That's a good thought and I think it's right. We looked at it yesterday. When a status gets renamed the connector treated the renamed ones as new rows. Our engineers have changed how it matches, on the ticket identifier, not the status. It should be fixed on the next nightly run.
  18. Christina Möller
    Christina Möller None
    Should. I would like to know that it is fixed, not that it should be. Kai, can you check tomorrow?
  19. Kai Petersen
    Kai Petersen None
    Yes, I can. I'll count the duplicates before and after and write it in the ticket.
  20. Laura Penhaligon
    Laura Penhaligon None
    That would be ideal, thank you. If it hasn't gone, put it on the same ticket and it comes straight to me.
  21. Christina Möller
    Christina Möller None
    Now point three. The hospital test. Kai, did you choose?
  22. Kai Petersen
    Kai Petersen None
    I made a short list of three. My suggestion is the university hospital in the north, because it has lots of contracts, several device types, and also a couple of old complaints that are closed. So we know what the right answer is.
  23. Christina Möller
    Christina Möller None
    Yes. That is a good choice, because we can check each answer against the complaint file.
  24. Laura Penhaligon
    Laura Penhaligon None
    I like that, you already hold the answers. So once the devices are in, we sit down together, and you ask the brain what you would normally dig for by hand. Which question would you ask first?
  25. Christina Möller
    Christina Möller None
    Which devices at this hospital had a service visit in the last year, and which of those visits came from a complaint? That takes my team half a day today.
  26. Laura Penhaligon
    Laura Penhaligon None
    Right. That's a perfect first question, because it joins the tickets, the contract and the devices. If it answers that with the source rows, we're in business.
  27. Kai Petersen
    Kai Petersen None
    And if it gets it wrong?
  28. Laura Penhaligon
    Laura Penhaligon None
    Then we find out why, which is exactly the point of doing it on a closed case. Usually it's a field that means two things in two systems, and we fix the mapping.
  29. Christina Möller
    Christina Möller None
    Good. Point four, training. We have licences for one hundred and fifty people, but I do not want everyone at once. I want the team leads trained first, then the key accounts, then the engineers.
  30. Laura Penhaligon
    Laura Penhaligon None
    That order makes sense. I'd suggest a walkthrough session for the team leads next week, once the devices are loaded, and then shorter sessions for the others. How do your engineers use their time? Are they reachable in blocks?
  31. Christina Möller
    Christina Möller None
    Early morning, before they drive. That is when they read the history of the site. So maybe short sessions at that time, with the question: what do I need to know before I arrive.
  32. Laura Penhaligon
    Laura Penhaligon None
    Lovely, I'll build the session around exactly that sentence. Single sign-on, by the way: IT sent the details and I think we're nearly there. I'll confirm at the end of the week that it's switched on.
  33. Kai Petersen
    Kai Petersen None
    They told me it is working for a test account already. I haven't tried it myself.
  34. Christina Möller
    Christina Möller None
    Then Kai tries it today and writes to us. Please.
  35. Kai Petersen
    Kai Petersen None
    Will do.
  36. Laura Penhaligon
    Laura Penhaligon None
    One more from me. The security answers I promised last time, did they reach you?
  37. Christina Möller
    Christina Möller None
    Yes, they arrived. Our security team has two follow-up questions, I will send them with the minutes. The access list was clear.
  38. Laura Penhaligon
    Laura Penhaligon None
    Good, send them over and I'll turn them round quickly.
  39. Christina Möller
    Christina Möller None
    Then let us agree the next steps. Laura confirms the device load on Thursday and prepares the team lead session. Kai checks the duplicates tomorrow and the single sign-on test today. I send the minutes and the security questions. Correct?
  40. Laura Penhaligon
    Laura Penhaligon None
    Correct. And nothing else on my side.
  41. Kai Petersen
    Kai Petersen None
    Nothing from me. Thanks both.
  42. Christina Möller
    Christina Möller None
    Thank you, Laura, Kai. Bis bald.
  43. Laura Penhaligon
    Laura Penhaligon None
    Speak soon, bye.

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