B-Glass
Callie Brennan

Penmaen Software / BG-Demo – Onboarding

Callcompleted

Penmaen Software logo Penmaen Software · 6 Aug 2024 15:15

First onboarding call with Ffion Rees, the admin. Agreed three core sources (helpdesk, CRM, usage data), written access requests, and a Growth rollout starting with Ffion alone. Salesforce access is the likely delay.

What was said

What this says

As at Fri 9 Oct 2026

First onboarding call with Ffion Rees, the admin. Agreed three core sources (helpdesk, CRM, usage data), written access requests, and a Growth rollout starting with Ffion alone. Salesforce access is the likely delay.

What happened: Callie Brennan agreed the connector order and an access checklist with Ffion Rees. Helpdesk and usage data go first, the CRM follows.

Customer view: Ffion wants ticket history, renewal dates and product usage per operator in one place, replacing a spreadsheet she rebuilds every Monday. She says the renewals workload is why they bought.

Commercial: Penmaen is licensed for forty users on Growth. Adoption depends on Ffion trusting the first refresh before customer success managers are invited, so an early credible result matters for the renewal case.

Watch: The Zendesk token was blocked because the owner is on leave, and the Salesforce integration user may take longer. Operator names may not match between helpdesk and account table.

AI · claude-sonnet-5-5 · as at Fri 9 Oct 2026

Themes

As at Fri 9 Oct 2026
Theme
Onboarding kickoff and access
Importance
neutral
Sentiment
positive
Voice
champion

Who was there

BG-Demo

Them

Follow-up

Next steps

As at Fri 9 Oct 2026
  • Ffion Rees emails her data team and IT, copying Callie Brennan, to request access in writing.
  • Callie Brennan sends the setup checklist the same day and compares operator names once she has read access.
  • Callie Brennan and Ffion meet again on Thursday at lunchtime to review the first refresh.

Risks

As at Fri 9 Oct 2026
  • The Salesforce integration user may take longer, delaying renewal data in the brain.
  • Operator names may not match between the helpdesk and the account table, which could undermine trust in early answers.
  • Customer success managers are described as allergic to new tools and may write it off if the first view is half built.

Opportunities

As at Fri 9 Oct 2026
  • Rolling out to the customer success managers on Growth, which includes forty users, would deepen adoption.
  • A first useful question about tickets before renewal gives a clear success test.

Transcript

  1. Callie Brennan
    Callie Brennan
    Hi Ffion, can you hear me alright?
  2. Ffion Rees
    Ffion Rees
    Yes, hi Callie. Sorry, give me a second, my headset has decided to reconnect itself. Right, that's better.
  3. Callie Brennan
    Callie Brennan
    No problem at all. Good afternoon, by the way. How's the week treating you?
  4. Ffion Rees
    Ffion Rees
    Busy. We've got a run of renewals coming up with a few of our leisure operators, so everyone's got their head down. Not complaining, though. It's actually why we bought this.
  5. Callie Brennan
    Callie Brennan
    Which is a nice way into the plan. So here's the next forty-five minutes. First, I want to agree which sources we connect and in what order. Second, what I need from your side is access for each of them, in writing, before we switch on the refresh. Third, we talk about who owns what once it's live. Does that work?
  6. Ffion Rees
    Ffion Rees
    That works. I should say I'm the admin on our side, so most of it lands with me, but I'll need to pull in someone from IT for a couple of the permissions.
  7. Callie Brennan
    Callie Brennan
    That's fine, and it's quite normal. Let's start with what you told Tom you wanted out of it. Remind me, in your own words.
  8. Ffion Rees
    Ffion Rees
    So customer success wants to be able to ask, per operator, what's their ticket history, when do they renew, and are they actually using our product. At the moment that's three different places and a spreadsheet I rebuild every Monday. It's miserable, honestly.
  9. Callie Brennan
    Callie Brennan
    Right. So three sources at the core: the helpdesk, your CRM for renewals, and the product usage data. Is the usage data already sitting in a warehouse, or is it somewhere else?
  10. Ffion Rees
    Ffion Rees
    It's in Snowflake, our data team loads it. Daily, I think. There's a table of events and a table of accounts. I don't know the exact names off the top of my head.
  11. Callie Brennan
    Callie Brennan
    That's helpful, because the brain runs inside your Snowflake account anyway, so that one is the easy one. I'll need someone from your data team to give us read access to those two tables. Could you ask them?
  12. Ffion Rees
    Ffion Rees
    Yes. I'll ask this week. Do you want it as an email or a ticket or what?
  13. Callie Brennan
    Callie Brennan
    Email is perfect. Just copy me and put the table names in it so there's a written record. I don't start any connector without written access, that's my one rule.
  14. Ffion Rees
    Ffion Rees
    Fair enough. Understood.
  15. Callie Brennan
    Callie Brennan
    Now the helpdesk. I saw there was a ticket from you a little while ago about permissions on the Zendesk side. Did that get sorted?
  16. Ffion Rees
    Ffion Rees
    Sort of. That was me trying to create an API token and not having the right role. Our Zendesk owner is on leave, so it's been sitting. I marked it high priority because I was impatient, sorry.
  17. Callie Brennan
    Callie Brennan
    Don't apologise, that's what the ticket's for. So the blocker is somebody with an admin role on Zendesk generating a token, or giving you the role. Is there a deputy?
  18. Ffion Rees
    Ffion Rees
    There's a colleague in IT who might be able to. I'll chase today. Mm, actually I'll walk over, it's quicker.
  19. Callie Brennan
    Callie Brennan
    Brilliant. Then the CRM. Which one are you on?
  20. Ffion Rees
    Ffion Rees
    Salesforce. And before you ask, yes, renewal dates live there, but they're not always up to date. The sales team update them when they remember.
  21. Callie Brennan
    Callie Brennan
    Good to know, and we'll note it. The brain will show what the CRM says, and we can flag where it disagrees with the contract documents later. For now, I need a read-only integration user and a connected app, or if that's too heavy, a report export on a schedule. Which is easier for you?
  22. Ffion Rees
    Ffion Rees
    Integration user, I think. We did one for another tool last year. I'd have to ask who set it up, though.
  23. Callie Brennan
    Callie Brennan
    Okay. Let me put that down. So, checklist. Snowflake read access, from your data team. Zendesk token, from IT. Salesforce integration user, from whoever built the last one. Yes?
  24. Ffion Rees
    Ffion Rees
    Yes. And I'll be honest, the Salesforce one might take longer.
  25. Callie Brennan
    Callie Brennan
    That's all right. We'll sequence it so the helpdesk and the usage data go first. That gets you ticket and usage views per operator, and the renewals follow.
  26. Ffion Rees
    Ffion Rees
    That would already be a big improvement.
  27. Callie Brennan
    Callie Brennan
    Good. Let me share my screen, because I want to show you the mapping sheet. Bear with me. Can you see it?
  28. Ffion Rees
    Ffion Rees
    Yes, I can see a grid with a lot of rows.
  29. Callie Brennan
    Callie Brennan
    That's it. Left column is the field in your source, middle is where it lands in the brain, right is a note. The thing I want you to think about is the word operator. In your helpdesk, how do you know which ticket belongs to which leisure operator?
  30. Ffion Rees
    Ffion Rees
    Hmm. There's an organisation field on the requester. It's mostly right. Some of the older tickets are under the individual's email instead, so it depends who raised it.
  31. Callie Brennan
    Callie Brennan
    Right, that's a classic. So the join between a ticket and an operator is the thing to get right. Does the account table in Snowflake have the operator name, and is it spelled the same way as in the helpdesk?
  32. Ffion Rees
    Ffion Rees
    Not sure. I can check. Probably not exactly the same. Someone will have put a full stop or a Ltd in.
  33. Callie Brennan
    Callie Brennan
    Exactly the sort of thing. I won't say it's fine until I've checked it. So that's an action for me too, once I have read access. I'll compare the names and send you a list of the ones that don't match.
  34. Ffion Rees
    Ffion Rees
    Oh, that would be great. I'd rather see that than find out three weeks in.
  35. Callie Brennan
    Callie Brennan
    Same. Now users. You're licensed for forty, on Growth. Who do you want in first?
  36. Ffion Rees
    Ffion Rees
    Initially just me, honestly, and then the customer success managers once I trust it. I don't want them seeing something half built and deciding it's rubbish.
  37. Callie Brennan
    Callie Brennan
    Sensible. I'd keep it to you until the first refresh has landed and we've both looked at it. Then we invite the managers in one go with a short walkthrough. I can do that session.
  38. Ffion Rees
    Ffion Rees
    Yes please. They're a bit allergic to new tools.
  39. Callie Brennan
    Callie Brennan
    Ha. Then we'll make the first question they ask something they care about. Something like which operators had the most tickets before their renewal. That's your kind of question, isn't it?
  40. Ffion Rees
    Ffion Rees
    That's exactly it. That and who's gone quiet.
  41. Callie Brennan
    Callie Brennan
    Good, I'll write that down as the test for whether the setup's working. Right, so, who sends what. You email your data team and IT, copy me. I send you the setup checklist today, and a name comparison once I have access. We speak again next week to look at the first refresh. Does Thursday suit?
  42. Ffion Rees
    Ffion Rees
    Thursday's fine. Lunchtime is better for me than the afternoon.
  43. Callie Brennan
    Callie Brennan
    Lunchtime it is. Anything else you want to raise before I let you go?
  44. Ffion Rees
    Ffion Rees
    No, I think that's it. Thanks, this has been really clear.
  45. Callie Brennan
    Callie Brennan
    Lovely. Speak Thursday. Thanks, Ffion, bye for now.
  46. Ffion Rees
    Ffion Rees
    Bye, Callie.

BG-Demo is a fictional company; every organisation and person here is invented. B-Glass is the tool. Data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Glass 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 B (the speech bubble) in the header, or open the Ask B page. Type a question, or pick one of the suggestions.

What the data covers

DataRecords
Organisations225
People at customers862
BG-Demo staff records (in post and leavers)58
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 AI 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.

BG-Demo is a fictional company: every organisation, person and figure here is invented for this demonstration. B-Glass is the tool that reads its data.

Who to contact

Email info@b-glass.uk or talk to your B-Glass account team. Tell us the page address and what looked wrong; a screenshot helps.

Help

Ask B

B-Glass · read-only