Laura Penhaligon

Clonvara Insurance Services / BB-Demo – Onboarding

Callcompleted

Clonvara Insurance Services: documents logo Clonvara Insurance Services: documents · 2025-11-18 11:45

Connection now passes after a key format fix. The first CRM load ran and the customer chose the underwriting system code as the broker key. A notes field access rule remains open, and organisation counts match but coded ones are a few short.

What was said

What this says

Current to 11 Oct 26

Connection now passes after a key format fix. The first CRM load ran and the customer chose the underwriting system code as the broker key. A notes field access rule remains open, and organisation counts match but coded ones are a few short.

What happened: With the allow list added and the key format fixed, Laura Penhaligon ran the first CRM load. Organisations and contacts finished, while activities were still running.

Customer view: Siobhán Dunne worries about brokers entered three ways and said she would lose faith loudly if one broker split into three. She decided the underwriting system code is the key and asked for it to be written down.

Commercial: Trust in broker answers is the early value test for the brain. The unresolved notes field rule is a data governance point that could hold back wider use.

Watch: Coded records are a handful short in the brain against Aoife Tuohy's export, and some brokers show no last contact. Laura owes a timestamp check.

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

Themes

Current to 9 Oct 26
Theme
CRM load, broker data quality
Importance
neutral
Sentiment
positive
Voice
decision-maker

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Laura to check timestamps on the missing coded records and report back.
  • Laura to bring options for a notes field access model next time.
  • Aoife to join the next call as helpdesk admin for the claims tickets connector.

Risks

Current to 9 Oct 26
  • Broker names are entered inconsistently, so a split broker could erode confidence early.
  • The CRM notes field holds personal remarks and has no access rule yet.
  • Coded broker counts differ slightly from the customer's export and are unexplained.

Opportunities

Current to 9 Oct 26
  • Joining CRM records to the underwriting code and flagging mismatches gives a visible early win on data quality.

Transcript

  1. Laura Penhaligon
    Laura Penhaligon None
    Morning, Aoife, morning, Siobhán. Can you both hear me? I've got a bit of an echo on my side.
  2. Siobhán Dunne
    Siobhán Dunne None
    Morning, Laura, I can hear you grand. No echo here.
  3. Aoife Tuohy
    Aoife Tuohy None
    Morning. Fine here too. Sorry, the sales ops person couldn't make it, she's tied up till later. I'll try to get her on another day.
  4. Laura Penhaligon
    Laura Penhaligon None
    No bother, it's not a problem as long as the connection is authorised somehow. Did the allow list get sorted?
  5. Aoife Tuohy
    Aoife Tuohy None
    It did, infrastructure added it on Friday. And that's the thing I wanted to flag. I raised a ticket with your support the same day because the first connection test failed, and the answer came back quickly, so that's fine, it's more that I wanted you to know.
  6. Laura Penhaligon
    Laura Penhaligon None
    I did see it. It was the key being the wrong format, wasn't it? An easy one, the key had been wrapped across lines when it went through the password manager.
  7. Aoife Tuohy
    Aoife Tuohy None
    Exactly that. Fixed, and the test passes now.
  8. Siobhán Dunne
    Siobhán Dunne None
    Grand, so we're connected. What does that actually mean today, Laura? Can I ask it something?
  9. Laura Penhaligon
    Laura Penhaligon None
    Not yet, honestly. It means the brain can reach your account and the first connector can load. What I'd like to do on this call is run the CRM load, then look at what came in before we call it good. Let me share my screen.
  10. Laura Penhaligon
    Laura Penhaligon None
    Okay. It's loading broker organisations first. You'll see the record count climbing here. It'll take a few minutes, so tell me in the meantime if there's anything that worries you.
  11. Siobhán Dunne
    Siobhán Dunne None
    The names, as I said. Brokers get entered three different ways. Full legal name, trading name, and a nickname the sales team made up.
  12. Laura Penhaligon
    Laura Penhaligon None
    That's why I want to look at it before anyone asks a question. If the brain answers 'which brokers are quiet' and splits one broker into three, you'll lose faith fast.
  13. Siobhán Dunne
    Siobhán Dunne None
    I would, and I'd say so loudly, to be fair.
  14. Aoife Tuohy
    Aoife Tuohy None
    Is there a broker reference in the CRM? Not the name, a code. The underwriting system uses one, and I think the CRM has it in a custom field.
  15. Siobhán Dunne
    Siobhán Dunne None
    It does, but it isn't always filled in. Maybe most of them. What's the source of truth, though? The CRM or the underwriting system? Because they've drifted.
  16. Laura Penhaligon
    Laura Penhaligon None
    That's your decision rather than mine, but my suggestion would be the underwriting system's code, because it's the one that has to be right to pay a broker. The brain can then join the CRM records to that code and flag the ones that don't match.
  17. Siobhán Dunne
    Siobhán Dunne None
    I like that. Right, underwriting system code is the key. Write it down so nobody argues in six months.
  18. Laura Penhaligon
    Laura Penhaligon None
    Written down. I'll put it in the shared notes with today's date, so there's a record of who decided.
  19. Aoife Tuohy
    Aoife Tuohy None
    Load's finished by the look of it. Is that the whole thing?
  20. Laura Penhaligon
    Laura Penhaligon None
    That's organisations and contacts. Activities are still running, it does those more slowly. Let me show you a sample. Here are a handful of brokers, with the code, last contact and the owner in your team.
  21. Siobhán Dunne
    Siobhán Dunne None
    Some of those have no last contact. Is that a gap in the load or a gap in the CRM?
  22. Laura Penhaligon
    Laura Penhaligon None
    Good question, and I'd want to check rather than guess. Activities haven't finished, so it may fill in. If it doesn't, it's the CRM.
  23. Aoife Tuohy
    Aoife Tuohy None
    I can run a query on my side and compare counts if that helps. I've got the CRM export from last month somewhere.
  24. Laura Penhaligon
    Laura Penhaligon None
    Please do. Count of broker organisations, and count with a code filled in. I'll do the same in the brain and we'll compare numbers.
  25. Aoife Tuohy
    Aoife Tuohy None
    Okay, I've got mine. It looks like they match on organisations. The coded ones are a bit different, though, a handful short in the brain.
  26. Laura Penhaligon
    Laura Penhaligon None
    Right. That might be records added since your export, and the load is more recent. I'll check the timestamps on those and come back to you.
  27. Siobhán Dunne
    Siobhán Dunne None
    While you do that, can I raise something small? Who'll be able to see the notes field on a broker? Underwriters write some personal things in there. I'd like the brain to respect whatever the CRM already does.
  28. Laura Penhaligon
    Laura Penhaligon None
    Today I'd say it mirrors what the connection user can read, so the brain would see all of it. What you need is a rule on who can ask about it. I'd rather we design that in the access model than assume. Can we leave it on the list and I'll bring options next time?
  29. Siobhán Dunne
    Siobhán Dunne None
    Yes. Leave it on the list. I'd just not want anyone to use the brain on that field until we've agreed.
  30. Laura Penhaligon
    Laura Penhaligon None
    Agreed. Only the two of you have access at the moment, so it's safe.
  31. Aoife Tuohy
    Aoife Tuohy None
    Next step for me is the helpdesk, yes? For the claims tickets.
  32. Laura Penhaligon
    Laura Penhaligon None
    Yes, that's next time. Can you get the helpdesk admin on the call? Same as the CRM, ten minutes.
  33. Aoife Tuohy
    Aoife Tuohy None
    That one's me, actually, so no problem.
  34. Siobhán Dunne
    Siobhán Dunne None
    Thanks a million, Laura. Same time next week.
  35. Laura Penhaligon
    Laura Penhaligon None
    Same time. Thanks both. Speak soon.

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
Organisations75
People at customers290
BB-Demo staff40
Calls784
Email threads1,169
Support tickets449
Documents477
Deals117
Invoices101
Events49
News items56

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.

Ask B

Ask B

B-Brain · read-only