B-Brain
Laura Penhaligon

Kadewerk Software / BB-Demo – Training

Callcompleted

Kadewerk Software logo Kadewerk Software · 2025-09-01 10:45

Laura Penhaligon trained Sanne de Wit on saved queries, exports and dashboards. Sanne was positive and found it useful. CSM handover to Marcus Bell was planned for the end of September.

What was said

What this says

Current to 13 Oct 26

Laura Penhaligon trained Sanne de Wit on saved queries, exports and dashboards. Sanne was positive and found it useful. CSM handover to Marcus Bell was planned for the end of September.

What happened: On 1 Sep 2025 Laura walked Sanne through the chat, the search builder and the dashboard builder. They built and saved a query called 'Silent customers with tickets' and exported it.

Customer view: Sanne said the first question she asked returned useful results quickly. She called the saved query really useful and said she felt they had a handle on using it.

Commercial: Sanne is on Starter with 15 users included. Dashboard building is usually an admin task, and Yara controls that permission.

Watch: Laura said Marcus Bell would take over the CSM relationship around the end of September and run the six-monthly check-in. Laura tied the value conversation to the renewal story, so the handover needs to carry that forward.

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

Themes

Current to 9 Oct 26
Theme
Starter onboarding training
Importance
neutral
Sentiment
positive
Voice
champion

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Sanne to build and save her own queries and test the silent-customers list weekly or monthly.
  • Marcus to ask Sanne after a week or two what value she is getting.

Risks

Current to 9 Oct 26
  • Handover from Laura to Marcus around the end of September could lose momentum in the early weeks.
  • Dashboard building depends on Yara as admin, so wider use may stay narrow.

Opportunities

Current to 9 Oct 26
  • The saved silent-customers query gives Sanne a concrete value story ahead of the renewal.

Transcript

  1. Laura Penhaligon
    Laura Penhaligon None
    Hi Sanne. Have you had a chance to play around with the brain since we gave you access?
  2. Sanne de Wit
    Sanne de Wit None
    Yeah, a bit. I asked it a question about customers with low activity and it actually came back with useful results. Surprised me how quick it was.
  3. Laura Penhaligon
    Laura Penhaligon None
    Right? So that's the point. Now let me walk you through what you can do systematically. Let me share my screen and I'll show you how to build a more structured query and then how to save it.
  4. Sanne de Wit
    Sanne de Wit None
    Okay, go for it.
  5. Laura Penhaligon
    Laura Penhaligon None
    So you're looking at the chat interface. You've got three ways to interact: you can ask in plain English like you've been doing, you can use the search builder for more precision, or you can look at the dashboards that are already built in. Let me start with the search builder because that's where you'll get the most control. It's this panel on the left.
  6. Sanne de Wit
    Sanne de Wit None
    I've seen that. Is that where I set filters?
  7. Laura Penhaligon
    Laura Penhaligon None
    Exactly. So let's build your ticket and activity query step by step. First filter, I want customers who are active in HubSpot but inactive in usage. So what fields would you want to look at? You've got created date, contract value, location, what matters?
  8. Sanne de Wit
    Sanne de Wit None
    Probably last login or activity date. And maybe customer size.
  9. Laura Penhaligon
    Laura Penhaligon None
    Good. So I'll click on, here, activity date. And I can set a threshold. Let's say last activity more than thirty days ago. Watch how it updates the result set. You're now looking at seventy-three customers with no usage in the last thirty days. Now I'm going to add a second filter, these customers must have support tickets in that same period. Clicking on Zendesk, ticket created date, last thirty days. Now you're down to, seventeen customers. That's your correlation set.
  10. Sanne de Wit
    Sanne de Wit None
    So those seventeen customers went quiet and also opened a ticket?
  11. Laura Penhaligon
    Laura Penhaligon None
    That's one narrative. Could be they stopped using because they hit a blocker. Could be they opened tickets because they were struggling. But that's the pattern. Once you've got this query, you can save it, call it something, and come back to it every week or month and see if the list is changing.
  12. Sanne de Wit
    Sanne de Wit None
    That's actually really useful.
  13. Laura Penhaligon
    Laura Penhaligon None
    Right. So let me show you how to save this. I'm clicking save, you name it, let's call it 'Silent customers with tickets', and now you can retrieve it any time. And the second thing you can do is export the results. So you've got seventeen customers: you can download that list and share it with your team, feed it into your CRM if you want, whatever. Let me show you that, you click here, it'll download as a CSV.
  14. Sanne de Wit
    Sanne de Wit None
    Okay. And what about dashboards?
  15. Laura Penhaligon
    Laura Penhaligon None
    Good question. So you've got a couple of built-in dashboards in the Starter tier, overview metrics, that sort of thing. But you can also build your own. Let me show you. This is the dashboard builder, I'll create a simple one. So I'll add a card, let's make one that shows ticket volume by customer segment. Click add card, choose Zendesk, ticket count, group by, customer segment from HubSpot. Boom, there's your dashboard card. You can save this, resize it, share it with your team.
  16. Sanne de Wit
    Sanne de Wit None
    Can multiple people build dashboards?
  17. Laura Penhaligon
    Laura Penhaligon None
    You're on Starter, so you've got 15 users included. Anyone on that licence can see the dashboards that are built, but building new ones, that's usually an admin thing. You can grant dashboard edit permissions if you want, but Yara can control that.
  18. Sanne de Wit
    Sanne de Wit None
    Right. Is there a limit on how many dashboards we can build?
  19. Laura Penhaligon
    Laura Penhaligon None
    No hard limit. Just don't go mad, I mean, theoretically you could build a thousand but after about five or six you're probably getting into diminishing returns. Keep them focused on actual questions you need answered.
  20. Sanne de Wit
    Sanne de Wit None
    That makes sense. Anything else I should know?
  21. Laura Penhaligon
    Laura Penhaligon None
    Data refreshes nightly. So if you run a query at 4 p.m., the data in the brain is from last night. It's not real-time but it's fresh. If you've got urgent questions mid-day, you're pulling live data from the sources themselves but it's a bit slower. The overnight refresh is the fast path. Otherwise just experiment. Ask it silly questions, silly questions lead to good insights. And, if you get stuck, let me know or flag it to Marcus once I've handed over.
  22. Sanne de Wit
    Sanne de Wit None
    Will you be handing over soon?
  23. Laura Penhaligon
    Laura Penhaligon None
    Yeah, probably end of September? Once you've had a couple of weeks to settle in and you're comfortable asking queries. Marcus will take over the CSM relationship and he'll do your six-monthly check-in. But if you've got technical issues during that transition, happy to help out.
  24. Sanne de Wit
    Sanne de Wit None
    Great. And this has been useful, honestly. I feel like we've got a handle on how to use it now.
  25. Laura Penhaligon
    Laura Penhaligon None
    Brilliant. Go and explore. Build that query we talked about and see what stories the data tells you. Once you've got a week or two under your belt, Marcus will want to hear how it's going and what value you're getting. That'll be the renewal story down the line.
  26. Sanne de Wit
    Sanne de Wit None
    Thanks, Laura. Really helpful.
  27. Laura Penhaligon
    Laura Penhaligon None
    Cheers. Speak 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