B-Brain
Laura Penhaligon

Kenmure Business Telecom / BB-Demo – Onboarding

Callcompleted

Kenmure Business Telecom logo Kenmure Business Telecom · 2025-10-27 16:45

First onboarding call with Alan Rennie, the customer's admin. Connector order agreed as CRM, billing, helpdesk, provisioning. Owners for provisioning and identity are unknown, and his director has not yet agreed the rollout order.

What was said

What this says

Current to 13 Oct 26

First onboarding call with Alan Rennie, the customer's admin. Connector order agreed as CRM, billing, helpdesk, provisioning. Owners for provisioning and identity are unknown, and his director has not yet agreed the rollout order.

What happened: Laura Penhaligon set out the three aims for the session. Alan Rennie explained that he matches billing data to fault records by hand and that this is the work the brain should take off him.

Customer view: Alan is unsure where he fits and does not own provisioning or identity. He wants rollout decisions to go past the director who signed the order form, so she does not find out afterwards.

Commercial: The order form licenses 150 users and includes single sign-on under Enterprise. The reference to a licence for a hundred and fifty users suggests the Enterprise tier is in play.

Watch: The helpdesk may be reviewed and swapped out. Provisioning staff are nervous about supplier meetings, so adoption depends on finding a connection owner there.

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

Themes

Current to 9 Oct 26
Theme
Onboarding and connector order
Importance
neutral
Sentiment
neutral
Voice
user

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Laura Penhaligon to email Alan Rennie the action list and copy in Marcus, the customer success manager.
  • Alan Rennie to send billing table names and ask the provisioning lead to join the next call.
  • Laura Penhaligon to draft a short rollout order for Alan to take to his director.

Risks

Current to 9 Oct 26
  • The helpdesk tool may be reviewed and replaced, which could break a connector after it is built.
  • Nobody has yet been found to own provisioning or identity at the customer.
  • The director who signed the order form has not yet agreed the rollout order.

Opportunities

Current to 9 Oct 26
  • Removing the manual matching of billing data to fault records gives a clear value case for the brain.
  • Single sign-on under Enterprise is wanted by IT and can be set up before wider rollout.

Transcript

  1. Laura Penhaligon
    Laura Penhaligon None
    Hello, Alan, can you hear me alright?
  2. Alan Rennie
    Alan Rennie None
    Yeah, I can hear you. Can you hear me? This headset is a bit temperamental, so tell me if I go all tinny.
  3. Laura Penhaligon
    Laura Penhaligon None
    Loud and clear. Good afternoon, just about. Thanks for making time at this end of the day.
  4. Alan Rennie
    Alan Rennie None
    No bother. It's been a long one, to be honest. Billing runs have been rattling through all week and I've been staring at spreadsheets since eight. Glasgow's doing its usual thing outside as well, so I'm not missing much.
  5. Laura Penhaligon
    Laura Penhaligon None
    Rain, I take it. It's grey down here too, so we're even. Right, shall I tell you what I had in mind for the call, and you stop me if it's not what you need?
  6. Alan Rennie
    Alan Rennie None
    Please, yeah. I'll be honest, I'm still getting my head around where I fit in all this. I got told I'd be the admin and that was about it.
  7. Laura Penhaligon
    Laura Penhaligon None
    That's fine, that's quite common actually. So this is the first proper onboarding session. What I want to get to by the end is three things. Which systems we connect first, who at Kenmure owns each one, and what has to happen on your side before we can switch anything on. Does that sound sensible?
  8. Alan Rennie
    Alan Rennie None
    Sounds sensible. Mind you, I might need to go and ask people about the ownership bit. I know the billing side and the data side. I don't know who looks after provisioning, not properly.
  9. Laura Penhaligon
    Laura Penhaligon None
    Mm, that's the bit most people don't know on day one, so don't worry. Let's start with why you bought it, because it tells me where to begin. From what I've seen, the idea is that account management, provisioning and the service desk can see each business customer's circuits, faults and bills in one place.
  10. Alan Rennie
    Alan Rennie None
    Yes, that's it exactly. At the moment if a customer rings up about a bill and they've also got a fault open, three different people look at three different screens and nobody's got the whole picture. I spend a good chunk of my week pulling bill data out and matching it up by hand against fault records. Which is, you know, not what I was hired for.
  11. Laura Penhaligon
    Laura Penhaligon None
    Right, and that matching is exactly what the brain is meant to take off you. So the billing data is probably our natural first connector, since you know it best. Can you tell me, in your own words, where billing lives and how it gets refreshed?
  12. Alan Rennie
    Alan Rennie None
    So the billing system produces the invoice data and there's an export that lands overnight into our warehouse. I don't touch the system itself, I work off the export. Is that the same thing for you or do you need the system directly?
  13. Laura Penhaligon
    Laura Penhaligon None
    Good question. Because we run inside your own Snowflake account, if the export already lands there then we can often read from it and not go near the billing system at all. That's usually the gentler option for your IT people. I'd want to look at the actual tables, though, before I promise anything.
  14. Alan Rennie
    Alan Rennie None
    Okay. Yeah, I can show you the tables. Not now, I'd want to tidy them up first, they're a bit of a jumble. Actually, no, that's silly, you'll see them in the end. I'll send you the names.
  15. Laura Penhaligon
    Laura Penhaligon None
    Names are plenty to start with. Second one. Provisioning. What do you use to track a circuit from order to live?
  16. Alan Rennie
    Alan Rennie None
    That's the bit I don't own. There's a provisioning team, it's mostly a couple of engineers and a coordinator, and they've got their own tool. I only see the output when it comes through to billing. I'd have to ask.
  17. Laura Penhaligon
    Laura Penhaligon None
    Fine. Can you ask whoever leads that team to join the next call, or at least name someone we can email? The person who can say yes to a connection is who I need, not necessarily the most senior.
  18. Alan Rennie
    Alan Rennie None
    I'll ask this week. I think it'll be easier if I say it's quick. People here get nervous if there's a meeting with a supplier.
  19. Laura Penhaligon
    Laura Penhaligon None
    Ha, tell them it's twenty minutes and I'll bring the questions. Third. The service desk. What do they log faults in?
  20. Alan Rennie
    Alan Rennie None
    It's a helpdesk tool. Tickets, basically. Each fault is a ticket against the customer, and the engineers update it as they go. That one I know reasonably, because I get asked for reports out of it quite a lot.
  21. Laura Penhaligon
    Laura Penhaligon None
    Good, that's a well-trodden route for us. So if I write it down, billing export first, helpdesk second, provisioning third once we've found its owner. And your CRM, do the account managers keep notes and contacts in there?
  22. Alan Rennie
    Alan Rennie None
    They do, in theory. In practice some of them keep a lot in their heads and in email. But yes, the customer list lives in the CRM, that's the master list. I'd say that should probably be earlier, actually, because everything hangs off the customer record.
  23. Laura Penhaligon
    Laura Penhaligon None
    That's a fair point and I think you're right. If the customer record is the spine then it goes first, and billing hangs off it. Let me rework the order. CRM, then billing, then helpdesk, then provisioning. I'll put that in the plan and you can tell me if I've got it backwards.
  24. Alan Rennie
    Alan Rennie None
    That works. What do I need to do on my side, then? Because I'm not the one with the keys to the CRM. I'm just the one who'll be asked why it's not working.
  25. Laura Penhaligon
    Laura Penhaligon None
    Which is the correct way round, honestly. What I'd send you is a short checklist per system. Who owns it, what read-only access we need, and whether anything about it is changing in the next few months, a migration or a new tool, anything like that. That last one matters more than people think.
  26. Alan Rennie
    Alan Rennie None
    Changing. Hmm. I think the helpdesk is due a review at some point, but I don't know if that's this year. I'll find out. I don't want you to connect to it and then someone swaps it out.
  27. Laura Penhaligon
    Laura Penhaligon None
    Exactly that. Better to know now. Now, on the people side. You've got the licence for a hundred and fifty users, as per the order form, so 150 people could in principle be logging in. Do you have a view on who gets it first?
  28. Alan Rennie
    Alan Rennie None
    I don't think we'd do all of them at once. That'd be chaos. I'd say account management first, because they're the ones asking me for things all the time, then the service desk, then provisioning when they're happy. But that's me guessing. It's not my decision.
  29. Laura Penhaligon
    Laura Penhaligon None
    That's a sensible guess and it matches how most telecoms customers roll out. Who does make the decision? Is it Tom's contact on your side, or someone else?
  30. Alan Rennie
    Alan Rennie None
    It'd be our director who signed it, really. I'll need to check whether she wants a say in the rollout. I'd rather not have her find out afterwards that we've picked the order.
  31. Laura Penhaligon
    Laura Penhaligon None
    Quite right. Let's not decide it today, then. I'll draft a rollout order and you can take it to her. Something she can say yes or no to in a minute, not a long document.
  32. Alan Rennie
    Alan Rennie None
    Yeah, please. Short is good.
  33. Laura Penhaligon
    Laura Penhaligon None
    One more thing before we run out of time. Single sign-on. Enterprise includes it, so we'd normally set that up before wider rollout, so people don't each have separate passwords. Who looks after identity at Kenmure?
  34. Alan Rennie
    Alan Rennie None
    That'll be IT. A colleague in IT looks after all of that. I can put you in touch. I'd say they'll be happy about it, actually, they hate password resets.
  35. Laura Penhaligon
    Laura Penhaligon None
    Everyone hates password resets. Lovely. So, to recap. You'll send me the billing table names, you'll ask the provisioning lead to join a short call, you'll check whether the helpdesk is changing, you'll take the rollout order to your director, and you'll introduce me to IT for sign-on. Have I missed anything?
  36. Alan Rennie
    Alan Rennie None
    I think that's all of it. Seems like a lot written down like that, but it's all small things. Can you send that list to me in an email? Otherwise I'll lose half of it by tomorrow.
  37. Laura Penhaligon
    Laura Penhaligon None
    Will do, tonight or first thing tomorrow. I'll copy in Marcus, who's your customer success manager and will pick things up once you're live, so he knows what we've agreed. Same time next Monday for the next session, if that works?
  38. Alan Rennie
    Alan Rennie None
    Same time is fine. I'll try and have the provisioning person on by then, no promises.
  39. Laura Penhaligon
    Laura Penhaligon None
    No promises needed. Thanks, Alan, that was really useful. Speak next week.
  40. Alan Rennie
    Alan Rennie None
    Cheers, Laura. Speak then. 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