B-Brain
Laura Penhaligon

Merriott Lyle Distribution / BB-Demo – Onboarding

Callcompleted

Merriott Lyle Distribution logo Merriott Lyle Distribution · 2025-04-02 11:30

Onboarding call on 2 Apr 2025. Tariq Saleem raised a high-priority ticket: the nightly load finished after branches opened twice. Laura Penhaligon agreed that is a miss against 07:00 and set out a three-wave connector plan.

What was said

What this says

Current to 13 Oct 26

Onboarding call on 2 Apr 2025. Tariq Saleem raised a high-priority ticket: the nightly load finished after branches opened twice. Laura Penhaligon agreed that is a miss against 07:00 and set out a three-wave connector plan.

What happened: Laura Penhaligon walked Deepa Chauhan and Tariq Saleem through connector order and owners. Tariq raised the high-priority ticket on the nightly branch load, which twice finished after branches opened.

Customer view: Deepa wants every number traceable and will be asked about the load at the account-data review. She asked for the cause in writing and was calm but exacting.

Commercial: Laura confirmed the order form at £116k a year, Enterprise, two hundred licensed users, with a term from 28 Feb 2025 to 27 Feb 2026. Deepa left money questions to Lewis, the account owner, and declined on-site training for now.

Watch: Freshness is credited on Enterprise, and Laura called the late load a miss against 07:00. The evidence does not show the cause or the outcome of the ticket.

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

Themes

Current to 9 Oct 26
Theme
Onboarding and late refresh
Importance
neutral
Sentiment
mixed
Voice
champion

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Laura Penhaligon to find the refresh slack and write to Deepa and Tariq about the ticket by the end of next week.
  • Laura to line up security review support and send written answers for the IT identity contact for single sign-on.
  • Tariq and Deepa to send names for credit control, the accounting system and identity.

Risks

Current to 9 Oct 26
  • The nightly refresh finished late twice, a freshness miss against 07:00 on an Enterprise subscription.
  • One wrong account in front of a regional director would damage trust in the account view.
  • The cause depends on the timing of the branch system extract, which Tariq's team cannot move themselves.

Opportunities

Current to 9 Oct 26
  • Only a pilot group of about a dozen is live against two hundred licensed users, so there is wide room for adoption.
  • Credit control wants invoices and disputes together, which makes the accounting system a natural early connector.
  • An on-site training day for the branches remains available as an add-on if Deepa changes her mind.

Transcript

  1. Laura Penhaligon
    Laura Penhaligon None
    Hello? Can you both hear me all right? I've got you on screen but my headset has been temperamental this morning.
  2. Deepa Chauhan
    Deepa Chauhan None
    Loud and clear, Laura. Morning. Tariq's just coming in now, I can see him in the lobby.
  3. Tariq Saleem
    Tariq Saleem None
    Morning, both. Sorry, I was finishing a load check and lost track of the time.
  4. Laura Penhaligon
    Laura Penhaligon None
    No problem at all, we've only just started. How's the week treating you?
  5. Deepa Chauhan
    Deepa Chauhan None
    Busy. The regional directors are all asking for numbers at once and every one of them thinks theirs is the urgent one. But it's the useful sort of busy, so I won't complain.
  6. Tariq Saleem
    Tariq Saleem None
    Same. Half the branch network seems to have decided this is the week to change their opening hours, so the CRM has been lively.
  7. Laura Penhaligon
    Laura Penhaligon None
    Ha, that sounds about right. Well, shall we get going? Deepa, you said in your note that there was one thing you needed from today.
  8. Deepa Chauhan
    Deepa Chauhan None
    Yes. Before we finish I want an agreed order for the connectors, with a named owner against each one, so the branch managers and credit control know what arrives when. If I leave with that, I'm happy.
  9. Laura Penhaligon
    Laura Penhaligon None
    That's very doable. It's more or less what I wanted to walk through anyway. Tariq, I think you usually start with the tickets?
  10. Tariq Saleem
    Tariq Saleem None
    I do, yes. We've got three open at the moment. Two are how-to questions from the pilot group, nothing worrying. One is marked high priority, and that's the one I'd like to talk about.
  11. Laura Penhaligon
    Laura Penhaligon None
    Go on.
  12. Tariq Saleem
    Tariq Saleem None
    It's the nightly load from the branch system. Twice last week it finished after the point where the branches open, so the account view was a day behind for the first hour or so. I've been through the load log and I can see where it slowed down, but I'm not going to guess at why until I've seen the source side.
  13. Deepa Chauhan
    Deepa Chauhan None
    Which branches saw it?
  14. Tariq Saleem
    Tariq Saleem None
    Not all of them. The reports I have are from a handful in the north. And it's not the branches' doing in any case, it's the timing of the extract, so let's not make it about them.
  15. Laura Penhaligon
    Laura Penhaligon None
    Understood. I've seen the ticket and our support team has it. What I can say is that the nightly refresh is meant to be complete by 07:00 on business days, so what you're describing is a miss against that, and I'd rather we treat it as a real item for this onboarding and not just something sitting in a queue.
  16. Tariq Saleem
    Tariq Saleem None
    That's all I wanted.
  17. Deepa Chauhan
    Deepa Chauhan None
    And can we make sure that when we know the cause, it comes to me in writing as well? I'll be asked about it at the account-data review.
  18. Laura Penhaligon
    Laura Penhaligon None
    Of course. I'll copy you both, and I'll ask Daniel to look at it too, since he's your customer success manager and he'll want to know.
  19. Deepa Chauhan
    Deepa Chauhan None
    Lovely. Thank you.
  20. Laura Penhaligon
    Laura Penhaligon None
    Right, let me share my screen. Give me a second. Can you see the plan?
  21. Tariq Saleem
    Tariq Saleem None
    Yes. Bit small but readable.
  22. Laura Penhaligon
    Laura Penhaligon None
    I'll zoom in. Better? So this is how I'd sequence it. You're on Enterprise, which gives you room for plenty of connectors, so the constraint isn't the number, it's the order, and who on your side looks after each one.
  23. Laura Penhaligon
    Laura Penhaligon None
    First wave, the CRM and the branch system together, because the whole point is the account view, and that only works if the two agree on who the account is. Second wave, the helpdesk and the call recorder. Third wave, the mailboxes and the accounting system, with documents from the shared drive last.
  24. Deepa Chauhan
    Deepa Chauhan None
    Let's stay on the first one for a moment. Which account, which branch? Our trade accounts sit under a head office record in the CRM, but the branch system holds them per branch, and sometimes twice.
  25. Tariq Saleem
    Tariq Saleem None
    That's a mapping question, and it's the one I care most about. A fair number of accounts have more than one branch code against a single CRM account. I keep a matching table by hand, and I'd like to bring that in as the starting point rather than have the brain guess.
  26. Laura Penhaligon
    Laura Penhaligon None
    Good, I'd much rather use yours. We load the matching table, run the brain's own matching against it, and hand you the differences as a list. You decide which side wins on each one. Nothing gets merged without you seeing it first.
  27. Tariq Saleem
    Tariq Saleem None
    And Deepa gets the list at the same time. I don't change a mapping without telling her.
  28. Deepa Chauhan
    Deepa Chauhan None
    Thank you. That matters, because the key-account managers will notice immediately if a customer they know turns into two, or two turn into one.
  29. Laura Penhaligon
    Laura Penhaligon None
    Exactly. So owner for the first wave: Tariq does the work, Deepa signs off the matching. Does that feel right?
  30. Deepa Chauhan
    Deepa Chauhan None
    Yes. Tariq does the work, I sign off, and nothing is final until the list has been through me.
  31. Tariq Saleem
    Tariq Saleem None
    One practical thing. The branch system extract runs overnight and my team can't move that window ourselves. If the refresh needs the extract earlier, I need to know soon so I can ask the people who own it.
  32. Laura Penhaligon
    Laura Penhaligon None
    That ties straight into your ticket, actually. I'll find out from our side how much slack the refresh has, and then we can ask the owners for a realistic change rather than a wish. I'll have that for you by the end of next week.
  33. Tariq Saleem
    Tariq Saleem None
    Good. Then we'll know what we're asking for.
  34. Deepa Chauhan
    Deepa Chauhan None
    Can I ask about the second wave? Credit control are the ones who'll care most, because they want to see the disputes next to the invoice, and what was said about them on the calls.
  35. Laura Penhaligon
    Laura Penhaligon None
    Then I'd move the accounting system up into the second wave, with the helpdesk, so invoices and disputes are together early. The call recorder can follow in the third wave. Is that the right way round for them?
  36. Deepa Chauhan
    Deepa Chauhan None
    Yes. And let's get credit control in the room. I'd like them to see invoices and disputes together before anyone outside the pilot sees it.
  37. Laura Penhaligon
    Laura Penhaligon None
    I like that. Who should we have? I'd want someone who actually chases the accounts, not only the manager.
  38. Deepa Chauhan
    Deepa Chauhan None
    I'll bring a team leader and someone from the disputes desk. I'll send you their names, and the owner of the accounting system, who sits in finance.
  39. Tariq Saleem
    Tariq Saleem None
    The accounting system admin is a colleague in finance, I'll introduce you. They'll only need read access, so it should be quick.
  40. Laura Penhaligon
    Laura Penhaligon None
    Read access is all we need. And everything runs inside your own Snowflake account, so the data isn't leaving your environment, which helps when finance ask.
  41. Deepa Chauhan
    Deepa Chauhan None
    Good. That will be their first question.
  42. Laura Penhaligon
    Laura Penhaligon None
    Next, sign-in. Enterprise includes single sign-on and automated user provisioning. Tariq, who looks after identity on your side?
  43. Tariq Saleem
    Tariq Saleem None
    A colleague in IT. I can set up a call. They'll want the security paperwork first, they're careful about anything that touches sign-in.
  44. Laura Penhaligon
    Laura Penhaligon None
    Understood. I'll make sure the security review support is lined up so they have what they need before that call, and I'll get the written answers over to you by the end of the week.
  45. Deepa Chauhan
    Deepa Chauhan None
    On users. We have two hundred licensed, but at the moment it's a pilot group of about a dozen. I don't want to open it to everyone until the account view is right.
  46. Laura Penhaligon
    Laura Penhaligon None
    That's sensible. I'd go in stages: the pilot group, then the key-account managers, then branch managers region by region. People lose trust quickly if they open it early and see one wrong number.
  47. Deepa Chauhan
    Deepa Chauhan None
    Exactly that. One wrong account in front of a regional director and I'll be explaining it for a month. Show me where that number comes from, every time.
  48. Laura Penhaligon
    Laura Penhaligon None
    That's built in. Every answer carries its sources, so a branch manager can click through to the order, the call or the invoice behind it.
  49. Tariq Saleem
    Tariq Saleem None
    That helps me too. If a number looks off I want to trace it back to the load, not argue about it.
  50. Deepa Chauhan
    Deepa Chauhan None
    Can we confirm the commercial side, so I'm not guessing? Enterprise, two hundred users, and what's the annual figure on the order form? I'd like to quote it correctly at the review.
  51. Laura Penhaligon
    Laura Penhaligon None
    The order form is £116,500 a year, Enterprise, two hundred licensed users, and the invoices match it. The term started on 28 Feb 2025 and runs to 27 Feb 2026. Anything beyond that, Lewis, your account owner, can go through with you.
  52. Deepa Chauhan
    Deepa Chauhan None
    Perfect. I'll leave anything about money with Lewis.
  53. Tariq Saleem
    Tariq Saleem None
    Before we finish, can I check the training? The branch managers won't read a manual. Is there something short for them?
  54. Laura Penhaligon
    Laura Penhaligon None
    There's walkthrough training for each wave, and I can run it for the pilot group first. If you want a full day on site for the branches, that's an add-on, and Lewis would need to scope it with you.
  55. Deepa Chauhan
    Deepa Chauhan None
    Let's keep to the walkthroughs for now. I don't want to promise the regions anything I can't show them.
  56. Laura Penhaligon
    Laura Penhaligon None
    Let me recap, then. First wave, the CRM and the branch system, with Tariq owning it and Deepa signing off the matching list. Second wave, the helpdesk and the accounting system, with credit control in the room. Third wave, the call recorder and the mailboxes. Sign-in once IT have the security paperwork. And I find out about the refresh slack and write to you both about the ticket by the end of next week.
  57. Tariq Saleem
    Tariq Saleem None
    That matches my notes. I'll send names for the accounting and identity people tomorrow.
  58. Deepa Chauhan
    Deepa Chauhan None
    And I'll send the credit control names. Thank you, Laura, this is the clearest it's been.
  59. Laura Penhaligon
    Laura Penhaligon None
    Good. I'll send the plan and my notes this afternoon. Speak soon.
  60. Tariq Saleem
    Tariq Saleem None
    Cheers, both.
  61. Deepa Chauhan
    Deepa Chauhan None
    Thanks, 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