Callie Brennan

Dunholm Precision / BB-Demo – Training

Callcompleted

Dunholm Precision: documents logo Dunholm Precision: documents · 2025-01-24 11:30

Training call on 24 Jan 2025. Jas Dhillon and Nathan Booth tried chat, search and source checking on live data, and found it useful for call preparation. Nightly refresh timing and a helpdesk access request came up.

What was said

What this says

Current to 11 Oct 26

Training call on 24 Jan 2025. Jas Dhillon and Nathan Booth tried chat, search and source checking on live data, and found it useful for call preparation. Nightly refresh timing and a helpdesk access request came up.

What happened: Callie Brennan trained Jas Dhillon and Nathan Booth on asking questions, search versus chat, and checking sources. Nathan then covered the admin area and the licence count of forty.

Customer view: Jas found the call summary useful and recalled a customer worry about lead time on a housing. He was reassured that the brain says so when it has nothing.

Watch: one order showed as late that Nathan thought was dispatched. Callie put it down to the nightly export, so the answer is yesterday's picture.

Commercial: Jas asked for helpdesk access, a sign of wider use from a heavy day-to-day user. The call does not show whether the helpdesk is already a connected source.

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

Themes

Current to 9 Oct 26
Theme
User training and admin
Importance
neutral
Sentiment
positive
Voice
user

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Nathan Booth to sort helpdesk access for Jas Dhillon.
  • Callie Brennan to send a written note of the questions tried and where to find each button.
  • Callie Brennan to run the next session on pages and saving reusable items.

Risks

Current to 9 Oct 26
  • Answers reflect the last nightly file, so a dispatched order can still show as late.
  • Chat is more likely to go wrong on vague questions, which could dent early trust.

Opportunities

Current to 9 Oct 26
  • Jas Dhillon wants helpdesk access, which could extend use across more sources.
  • Call preparation is a clear daily use case for the sales engineering team.

Transcript

  1. Callie Brennan
    Callie Brennan None
    Morning, both. Can you see my screen? I'll share it in a second. Jas, you're on mute, I think.
  2. Jas Dhillon
    Jas Dhillon None
    Sorry. Morning. Yeah, can see it now. Nathan's just next to me, we're on the same laptop, if that's all right.
  3. Nathan Booth
    Nathan Booth None
    I'll jump in from my own login in a bit. It's just that my screen's being fixed.
  4. Callie Brennan
    Callie Brennan None
    No problem at all. So the plan for this session, about an hour and a bit, is: how to ask the brain a question and read the answer, how search differs from chat, and how to check where an answer came from. Then Nathan, last twenty minutes, the admin side.
  5. Jas Dhillon
    Jas Dhillon None
    Great. What I do all day is get ready for customer calls. So I'd like to see how it helps with that.
  6. Callie Brennan
    Callie Brennan None
    Perfect, let's use that. Pick a customer you spoke to recently. Don't tell me, just type the name into chat.
  7. Jas Dhillon
    Jas Dhillon None
    Right. Okay, I've picked one of the energy customers. Typing it in. What do I ask?
  8. Callie Brennan
    Callie Brennan None
    Ask it as you'd ask a colleague. What are the open orders for this customer, and is anything late?
  9. Jas Dhillon
    Jas Dhillon None
    It's come back. A table of orders, and it says three are past their promised date. Is that right?
  10. Callie Brennan
    Callie Brennan None
    Good question, and the right one to ask. Click the source link underneath the answer. It shows you the rows it used. Does that match what you'd see in the order system?
  11. Nathan Booth
    Nathan Booth None
    It does for the ones I can see. There's one it's listed as late which I thought was dispatched.
  12. Callie Brennan
    Callie Brennan None
    That could be the nightly export timing. The brain only knows what was in the last file. So if something was dispatched this morning, it won't show until the next refresh. That's worth saying to anyone new, honestly.
  13. Jas Dhillon
    Jas Dhillon None
    Right, so it's yesterday's picture.
  14. Callie Brennan
    Callie Brennan None
    Yesterday's picture, yes. Every answer shows when the data was last refreshed, top right. Have a look.
  15. Jas Dhillon
    Jas Dhillon None
    Got it. Okay, can I ask it what the customer said on our last call?
  16. Callie Brennan
    Callie Brennan None
    You can, as long as the call recorder is connected, and yours is, from this week. Try it.
  17. Jas Dhillon
    Jas Dhillon None
    Oh, that's good. It's given me three points and the bit of the transcript each came from. They were worried about the lead time on a particular housing. I'd forgotten that.
  18. Callie Brennan
    Callie Brennan None
    That's the kind of thing it's good for. Now try the same thing in search instead of chat. Search is for finding the thing. Chat is for asking about it.
  19. Nathan Booth
    Nathan Booth None
    What's the practical difference? When would you go to one over the other?
  20. Callie Brennan
    Callie Brennan None
    Search if you know roughly what you're after, a document, a ticket, a call, and you want to open it. Chat if you want a summary across several. Chat also is a bit more likely to go wrong if the question is vague, so be specific. Customer, part, time frame.
  21. Jas Dhillon
    Jas Dhillon None
    Which customer, which part. Ruth would be pleased.
  22. Nathan Booth
    Nathan Booth None
    She says it in every meeting.
  23. Callie Brennan
    Callie Brennan None
    Ha. Well, she's right. Let's try one that crosses sources. Ask: have there been any quality tickets for this customer in the last few months, and were there any related orders?
  24. Jas Dhillon
    Jas Dhillon None
    It's found one ticket and linked it to an order. It's a dimensional issue on a batch. And a call where they mentioned it.
  25. Callie Brennan
    Callie Brennan None
    That's the three systems in one answer, which is the reason you bought it. Take a minute and click through each source and check you agree.
  26. Nathan Booth
    Nathan Booth None
    The ticket's right. The order number's right. The call, I'd need Jas to say.
  27. Jas Dhillon
    Jas Dhillon None
    Yeah, that's the call. Good.
  28. Callie Brennan
    Callie Brennan None
    Brilliant. Now I want you to find something it gets wrong, deliberately. Ask about something that's not in there. A customer you've never dealt with.
  29. Jas Dhillon
    Jas Dhillon None
    It says it can't find anything. Fair enough. I half expected it to make something up.
  30. Callie Brennan
    Callie Brennan None
    It's built to say so when it has nothing. If it ever gives you something confident and wrong, tell me or Nathan, and we'll look at the source.
  31. Nathan Booth
    Nathan Booth None
    Right, admin. Where do I see who's got access?
  32. Callie Brennan
    Callie Brennan None
    Let me stop sharing and then share again from the admin area. Hold on. There. People tab, down the left. You've got the licence count at the top, forty licensed, and the list below.
  33. Nathan Booth
    Nathan Booth None
    So adding someone is just their email and a role.
  34. Callie Brennan
    Callie Brennan None
    Email and role, yes. Role decides which sources they see. I'd start everybody as a standard user and keep admin to the two of you. Then if Jas wants to see the helpdesk, you say yes or no.
  35. Jas Dhillon
    Jas Dhillon None
    I do want to see the helpdesk, as it happens.
  36. Nathan Booth
    Nathan Booth None
    I'll sort it. Leave that with me.
  37. Callie Brennan
    Callie Brennan None
    Last thing. I'll write today's session up as a short note with the questions we tried and where to find each button. Then next session is more on pages and saving things your team will reuse.
  38. Callie Brennan
    Callie Brennan None
    Thanks, both. Good session. Speak on Monday. 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
Organisations150
People at customers573
BB-Demo staff48
Calls1,382
Email threads2,122
Support tickets789
Documents850
Deals217
Invoices187
Events49
News items84

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.

HelpAsk B

Ask B

B-Brain · read-only