B-Brain
Laura Penhaligon

Thackwray Logistics / BB-Demo – Onboarding

Callcompleted

Thackwray Logistics logo Thackwray Logistics · 2025-05-08 11:45

Kelly Swainston wants returns problems spotted before brands raise them. The call agreed connector order, a freshness check on orders, Josh Pearce as admin, and a returns-accuracy gate before client managers get access.

What was said

What this says

Current to 13 Oct 26

Kelly Swainston wants returns problems spotted before brands raise them. The call agreed connector order, a freshness check on orders, Josh Pearce as admin, and a returns-accuracy gate before client managers get access.

What happened: Laura Penhaligon opened the onboarding by agreeing sources and owners. Returns tickets connect first, then orders, then service review notes.

Customer view: Kelly wants to walk into brand reviews knowing what the brand saw. She said "If the data is stale I need to know it's stale."

Commercial: The customer is on Growth with forty seats. Only Kelly and Josh start, and client managers follow once a returns question comes back right with the source shown.

Watch: The nightly export occasionally overruns after a big promotion week. The older helpdesk queues were merged and retagged, so history is messy, and the credentials depend on an IT colleague approving the service account.

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

Themes

Current to 9 Oct 26
Theme
Onboarding scope and sources
Importance
neutral
Sentiment
positive
Voice
champion

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Josh Pearce to send the retagging note and the credentials through the agreed secure route.
  • Laura Penhaligon to send the access list and the folder naming suggestion after the call.
  • Laura Penhaligon to set a freshness check on the orders source with Josh as first to be told.

Risks

Current to 9 Oct 26
  • The nightly orders export sometimes overruns after promotion weeks, so the brain could answer on stale data.
  • Service account approval depends on an IT colleague, which could delay connecting sources.
  • Merged helpdesk queues make pre-retagging history unreliable until it is mapped.

Opportunities

Current to 9 Oct 26
  • Forty Growth seats leave headroom as client managers are added after the returns gate is met.
  • A returns question answered correctly with its source shown would prove value to a wider group of client managers.

Transcript

  1. Laura Penhaligon
    Laura Penhaligon None
    Hello, can you both hear me alright?
  2. Kelly Swainston
    Kelly Swainston None
    Loud and clear. Hi Laura. Josh, are you on?
  3. Josh Pearce
    Josh Pearce None
    Yeah, sorry, just unmuting. Hi both.
  4. Laura Penhaligon
    Laura Penhaligon None
    No problem at all. Is the weather any better up your way? It's properly grey down here.
  5. Kelly Swainston
    Kelly Swainston None
    Raining on the M18, as usual. I'll be brisk if that's alright, I've got a service review to prepare for this afternoon and I want to walk in knowing exactly what the brand saw. That's really what I'm after from all of this.
  6. Laura Penhaligon
    Laura Penhaligon None
    That's a good place to start, actually. So today is about getting the sources connected and agreeing who owns what. Orders, returns tickets and the service review notes, all in one place for each brand. Does that match what you had in mind?
  7. Kelly Swainston
    Kelly Swainston None
    Exactly that. Returns first, then orders. If a brand is about to raise a returns problem I want to have spotted it before they do.
  8. Laura Penhaligon
    Laura Penhaligon None
    Right. Then let's order the connectors that way. Josh, you're the admin, so you'll be the one holding the keys. Can you talk me through where the returns tickets live at the moment?
  9. Josh Pearce
    Josh Pearce None
    They're in the helpdesk. Each brand has its own queue, more or less, though a couple of the older ones got merged when we changed how we tag things. So the history is a bit messy before last year.
  10. Laura Penhaligon
    Laura Penhaligon None
    That's fine, it's very common. We'll bring it all in and flag the tagging change so nobody reads a jump as a real trend. Who could tell us what changed and when?
  11. Josh Pearce
    Josh Pearce None
    Me, mostly. I did the retagging. I can write it up.
  12. Kelly Swainston
    Kelly Swainston None
    Please do. Short, though. Half a page.
  13. Josh Pearce
    Josh Pearce None
    Half a page. Yeah.
  14. Laura Penhaligon
    Laura Penhaligon None
    Lovely. Next, orders. Where does that data sit, is it straight from the warehouse system or does it go through something else first?
  15. Josh Pearce
    Josh Pearce None
    It goes through a nightly export into a reporting database. Nobody queries the warehouse system directly, because the two sites would fall over. So we'd point the brain at the export, not the live system.
  16. Laura Penhaligon
    Laura Penhaligon None
    That's the sensible way to do it. And the export lands before the morning shift?
  17. Josh Pearce
    Josh Pearce None
    It should do. Mostly it's done well before six. Occasionally it overruns after a big promotion week, and then someone has to nudge it.
  18. Kelly Swainston
    Kelly Swainston None
    Which is exactly the thing I don't want to find out about at the review. If the data is stale I need to know it's stale.
  19. Laura Penhaligon
    Laura Penhaligon None
    Understood. The refresh in your own Snowflake account is meant to be complete by seven on working days, so we'll put a freshness check on the orders source specifically and make Josh the first person told if it slips. Is that sensible?
  20. Josh Pearce
    Josh Pearce None
    Yeah. That's fine by me.
  21. Laura Penhaligon
    Laura Penhaligon None
    Good. Then the service review notes. Where are those kept, Kelly?
  22. Kelly Swainston
    Kelly Swainston None
    Shared drive, one folder per brand, one document per month. Some of the client managers are tidy about it and some are, let's say, creative.
  23. Laura Penhaligon
    Laura Penhaligon None
    Ha. That's all right, the brain doesn't mind creative, it just reads what's there. Would it help if I sent a simple naming suggestion for the folders? Not to enforce, just to make search nicer.
  24. Kelly Swainston
    Kelly Swainston None
    Send it. I'll take it to the client managers on Monday. Let's take the facts to the review, and the facts are only any good if people write them down the same way.
  25. Laura Penhaligon
    Laura Penhaligon None
    Perfect. Now, users. You've got forty seats on Growth, and I know you won't fill them on day one. Who goes in first?
  26. Kelly Swainston
    Kelly Swainston None
    Me and Josh to begin with, so we can kick it about. Then the client managers in a group, once I'm sure it answers a returns question properly. I don't want them trying it, getting a daft answer and never coming back.
  27. Laura Penhaligon
    Laura Penhaligon None
    That's a wise order. So the target before you open it up is that a returns question for one brand comes back right, with the source shown. Shall we agree that as the gate?
  28. Kelly Swainston
    Kelly Swainston None
    Yes. Josh, you'd be the one testing it with me.
  29. Josh Pearce
    Josh Pearce None
    Fine. I'll pick two or three brands where I already know the answers.
  30. Laura Penhaligon
    Laura Penhaligon None
    That's the best way, honestly. Known answers first. I'll send the access list after this call so you can see what we need from you, and Josh, if you can get the credentials to me through the secure route we agreed rather than email, that'd be great.
  31. Josh Pearce
    Josh Pearce None
    Will do. Probably end of the week, I've got to ask our IT colleague to approve the service account.
  32. Kelly Swainston
    Kelly Swainston None
    Chase him if he's slow. I'd rather have it connected next week than perfect in a month.
  33. Laura Penhaligon
    Laura Penhaligon None
    Agreed, and we can always tighten afterwards. Anything else either of you wanted to raise before you go?
  34. Kelly Swainston
    Kelly Swainston None
    No, that's all I needed. Thanks, both. I've got a review to write.
  35. Josh Pearce
    Josh Pearce None
    Nothing from me.
  36. Laura Penhaligon
    Laura Penhaligon None
    Brilliant. So Josh sends the retagging note and the credentials, I send the access list and the folder naming suggestion. Speak soon, and good luck with the review, Kelly.
  37. Kelly Swainston
    Kelly Swainston None
    Thanks, Laura. 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