Callie Brennan

Pentreath Cold Chain / BB-Demo – Onboarding

Callcompleted

Pentreath Cold Chain: documents logo Pentreath Cold Chain: documents · 2024-01-24 16:15

On the 24 Jan 2024 onboarding call Callie Brennan and the customer agreed four connectors under Growth, a client and depot name mapping, and phased user access before the first refresh.

What was said

What this says

Current to 11 Oct 26

On the 24 Jan 2024 onboarding call Callie Brennan and the customer agreed four connectors under Growth, a client and depot name mapping, and phased user access before the first refresh.

What happened: Kerensa Trelease described the pain: an excursion took three people and four screens to piece together. Callie Brennan tied that to what the customer bought and agreed four connectors: helpdesk, CRM, SharePoint and a scheduled export from the transport system.

Customer view: Kerensa wants ticket, order and contract terms in one place. She was clear that a wrong depot is worse than none.

Commercial: Finance have asked about invoices beside the client view, a possible later connector. Licences for fifty people will be switched on in waves once the data is trustworthy.

Watch: Dan Hosken is the only admin and wants a second person. Older helpdesk tickets carry free-text client names that need mapping.

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

Themes

Current to 9 Oct 26
Theme
Connector scope and name mapping
Importance
neutral
Sentiment
neutral
Voice
champion

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Dan Hosken to send the access email and the distinct client names list by Friday.
  • Callie Brennan to draft the mapping sheet, run a sample refresh early next week and send the checklist note.
  • Kerensa Trelease to choose a second person to learn the admin screen.

Risks

Current to 9 Oct 26
  • Free-text client names and mismatched depot codes could give wrong answers, which Kerensa said would be worse than none.
  • Dan Hosken is the only admin, so absence would leave nobody who can run the brain.
  • The order data depends on a scheduled export whose column names must stay stable.

Opportunities

Current to 9 Oct 26
  • An invoices connector for finance would deepen use within the connector headroom of Growth.
  • Phased activation of the fifty licences can widen use once the first refresh is trusted.

Transcript

  1. Callie Brennan
    Callie Brennan None
    Hello, hello. Can you hear me all right? I've got a slightly crackly headset today so shout if I sound like I'm underwater.
  2. Kerensa Trelease
    Kerensa Trelease None
    Loud and clear. Afternoon, Callie. Dan's just getting his camera sorted, he's on the other laptop.
  3. Dan Hosken
    Dan Hosken None
    Here, sorry. Afternoon. The meeting link wanted me to update something first. Classic.
  4. Callie Brennan
    Callie Brennan None
    No problem at all. Right, so the plan for the next hour is this. First, we agree the list of sources we connect. Second, I tell you what I need from your side before we switch on the refresh. Third, we talk about how your client names line up across systems, because that's where these things usually wobble. Then next steps and who sends what.
  5. Kerensa Trelease
    Kerensa Trelease None
    Sounds right. Can I start with the thing that actually matters to my account managers, though?
  6. Callie Brennan
    Callie Brennan None
    Please do.
  7. Kerensa Trelease
    Kerensa Trelease None
    We had an excursion last week on a pharma load out of Avonmouth. Client heard from us before they saw it, which is how it should be, but it took three people and four screens to piece together. Ticket, order, the contract terms on what counts as a breach. That's what I want in one place. Facts before feelings.
  8. Callie Brennan
    Callie Brennan None
    That maps cleanly onto what you bought. Excursion tickets, orders and contract reviews, all hanging off the client. So the three sources I'd expect are the helpdesk, the CRM and wherever your order data lives. Dan, is that the full list or is there a fourth?
  9. Dan Hosken
    Dan Hosken None
    Mostly that. The orders sit in our transport management system, which isn't one of the standard ones, so I'd need to give you a scheduled export. Contract reviews are just documents in a shared drive, folder per client.
  10. Callie Brennan
    Callie Brennan None
    Okay, a scheduled export is fine. What I need from your side is the export dropped somewhere we can both see, with the column names stable. If the columns move around every week the refresh will complain, and rightly.
  11. Dan Hosken
    Dan Hosken None
    They shouldn't move. I own the export job, so I can promise they won't without telling you.
  12. Callie Brennan
    Callie Brennan None
    Lovely, I'll hold you to that. And the shared drive. Is it Microsoft 365 or Google Workspace?
  13. Dan Hosken
    Dan Hosken None
    Microsoft 365, SharePoint underneath. The client folders are in one document library, which helps.
  14. Callie Brennan
    Callie Brennan None
    That's a good start. One library, one connector. So that's helpdesk, CRM, SharePoint and the export. Four connectors, comfortably inside what Growth gives you, and there's room if you want to add something later.
  15. Kerensa Trelease
    Kerensa Trelease None
    We might. Finance have been asking about invoices next to the client view, but let's get this lot working first.
  16. Callie Brennan
    Callie Brennan None
    Sensible. Crawl, then walk. Now, access. I don't start a connector without written access, so before we switch anything on I need an email from Dan with each credential or service account named, and what permissions it holds. Read-only is all I want.
  17. Dan Hosken
    Dan Hosken None
    Understood. I'll set up a dedicated read-only user on each rather than using mine. Cleaner if I ever move roles.
  18. Callie Brennan
    Callie Brennan None
    That's exactly what I'd have suggested. Credentials arriving before the kickoff makes my life much easier, and honestly yours too.
  19. Kerensa Trelease
    Kerensa Trelease None
    Dan, you're the admin on our side for this, yes? Not me. I'll be asking questions, not touching settings.
  20. Dan Hosken
    Dan Hosken None
    Yes, I'm the admin. Though I'd like a second person who knows how it works, in case I'm off.
  21. Callie Brennan
    Callie Brennan None
    Good instinct. I'd say pick one account manager who's curious and we walk them through the admin screen on the next call. My aim is that you can run this alone and don't need me.
  22. Kerensa Trelease
    Kerensa Trelease None
    Mm. I'll think about who. Probably someone from the pharma side, they're the ones who live in the excursion tickets.
  23. Callie Brennan
    Callie Brennan None
    Right, naming. This is the bit I flagged. In the helpdesk, how does a ticket say which client it's about?
  24. Dan Hosken
    Dan Hosken None
    Ah. So. There's a company field, but it's free text for some of the older tickets. People type the client's trading name, or the legal name, or just initials. The newer ones use a dropdown.
  25. Kerensa Trelease
    Kerensa Trelease None
    That's my fault, we tidied it up last spring and never went back. Sorry.
  26. Callie Brennan
    Callie Brennan None
    Not a fault, it's normal. What I'd like is a small mapping sheet. Left column, whatever appears in the helpdesk. Right column, the name as it's held in the CRM. I'll build the first draft from what we find and Dan, you correct it.
  27. Dan Hosken
    Dan Hosken None
    How many variants are we talking? I can pull a distinct list of that field now if it helps.
  28. Callie Brennan
    Callie Brennan None
    Yes please, that would save a week. Send the distinct list and I'll match what I can by name and flag the rest.
  29. Kerensa Trelease
    Kerensa Trelease None
    What about the depots? We've got Avonmouth and the two satellites. A load can start at one and finish at another.
  30. Callie Brennan
    Callie Brennan None
    Does the order export say which depot, or is that only in the tickets?
  31. Dan Hosken
    Dan Hosken None
    Both, but they're not the same code. The export uses a short depot code, the tickets spell the name out. Different again for one of the satellites, bless it.
  32. Callie Brennan
    Callie Brennan None
    Then the mapping sheet gets a second tab for depots. Three rows, easy. I'd rather do that than guess, I won't say a mapping is fine until I've checked it against real rows.
  33. Kerensa Trelease
    Kerensa Trelease None
    Good. Because if the brain tells an account manager the wrong depot for an excursion, that's worse than telling them nothing.
  34. Callie Brennan
    Callie Brennan None
    Agreed, completely. Okay, timing. Once I have the access email and the two lists, I'd run a first refresh on a sample, look at it with Dan, and only then do the full load. So not this week.
  35. Dan Hosken
    Dan Hosken None
    I can get the access email to you by Friday. The lists too, they're quick.
  36. Callie Brennan
    Callie Brennan None
    Brilliant. Then I'll aim for the sample refresh early next week, and we book the next call for when it's landed.
  37. Kerensa Trelease
    Kerensa Trelease None
    One question before we go. The fifty seats. Do I need to decide who gets one now?
  38. Callie Brennan
    Callie Brennan None
    Not yet. Licences exist for fifty people but I'd turn them on in waves once the data's trustworthy. Nobody wants a first impression built on half-mapped names.
  39. Kerensa Trelease
    Kerensa Trelease None
    Fair. Waves it is. I'll tell the team to hang on.
  40. Callie Brennan
    Callie Brennan None
    I'll send a short note after this with the checklist, a date against each step, and the sheet template. Anything you want to add before we stop?
  41. Dan Hosken
    Dan Hosken None
    No, I think I've got my list. Access email, distinct client names, export location.
  42. Kerensa Trelease
    Kerensa Trelease None
    Nothing from me. Thanks, Callie.
  43. Callie Brennan
    Callie Brennan None
    Lovely. Thanks both, speak soon. Thanks, Callie.

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