Hollie Grieve

Quarrington Care Network / BB-Demo – Onboarding

Callcompleted

Quarrington Care Network: documents logo Quarrington Care Network: documents · 2026-05-07 14:45

Onboarding call fixed what the brain may see: referral, CRM, liaison calls and contracts, with patient ticket fields excluded. Trent Nakamura found CRM referral counts above his report, so liaisons see nothing until numbers tie.

What was said

What this says

Current to 11 Oct 26

Onboarding call fixed what the brain may see: referral, CRM, liaison calls and contracts, with patient ticket fields excluded. Trent Nakamura found CRM referral counts above his report, so liaisons see nothing until numbers tie.

What happened: Marisol Vega stated the scope and Ollie Pearson agreed it. Patient fields on intake tickets are excluded by allow-list, and referral stages from the admissions system are held back as a change request.

Customer view: Trent said the CRM referral extract does not tie to his report. Danielle Okonkwo accepted that liaisons wait for checked numbers.

Commercial: Hollie Grieve confirmed Growth at forty users and £50,000 a year, and Danielle agreed. Trent said forty is tight, but Danielle is not committing anything further and said it is not her call alone.

Watch: The reconciliation and Marisol's written review gate the first liaison view.

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

Themes

Current to 9 Oct 26
Theme
Data scope and reconciliation
Importance
neutral
Sentiment
positive
Voice
champion

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Ollie Pearson to send the scope document with the allow-list today and a sample load early next week.
  • Trent to send the admissions and helpdesk field lists tomorrow and the reconciliation list by the end of next week.
  • Danielle Okonkwo to check contract exhibits by Friday and set up the liaison session for next week.

Risks

Current to 9 Oct 26
  • The first liaison view waits on Trent Nakamura's reconciliation of CRM and report referral counts.
  • Marisol Vega will not sign on the call alone, so connectors stay off until her written review.
  • A read-only audit view for Marisol is unconfirmed and could become a sticking point.

Opportunities

Current to 9 Oct 26
  • Trent says forty users is tight if liaisons, leadership and some patient services staff all join.
  • Retiring repeated one-off referral report requests gives a measurable value case.

Transcript

  1. Hollie Grieve
    Hollie Grieve None
    Hi everyone. Can you hear me alright? I can see Danielle and Trent, so we're just waiting on Marisol and Ollie, I think.
  2. Trent Nakamura
    Trent Nakamura None
    Hear you fine. Hi Hollie.
  3. Ollie Pearson
    Ollie Pearson None
    Afternoon all. Sorry, I'm here. My headset decided to update itself at the worst moment. Can you hear me?
  4. Danielle Okonkwo
    Danielle Okonkwo None
    Loud and clear, Ollie. Hey, everybody. Okay, before we start, quick win from the field. One of our liaisons in Wisconsin sat down with a physician group this week and they've agreed to send us their discharge referrals first. She'd been chasing that for months. So the liaisons are fired up, and that's why I want this to land properly.
  5. Hollie Grieve
    Hollie Grieve None
    That's brilliant, well done to her. Is Marisol on her way, do we know?
  6. Marisol Vega
    Marisol Vega None
    I'm here, I was on mute. Good afternoon. Before we begin, I would like to confirm what data is in scope for this session, because that is what I have been asked to sign off. Is any PHI in scope?
  7. Hollie Grieve
    Hollie Grieve None
    That's exactly the right place to start, and honestly it's the whole point of today. So the plan for the next forty minutes or so is this. Ollie walks through each source we intend to connect, and where it matters, field by field. Marisol, you tell us what stays in and what stays out. Trent, you're the admin, so you're the one living with whatever we agree. Danielle, you're here for the business need. Sound fair?
  8. Danielle Okonkwo
    Danielle Okonkwo None
    Fair. Short version from me. Liaisons need one view per referrer. Referral volumes, the calls with the hospital, what's in the contract. That's it. I don't need anything clinical in there. Nothing.
  9. Marisol Vega
    Marisol Vega None
    Thank you, Danielle. I would like that stated plainly in the record, because it is minimum necessary in practice. Ollie, please go through the sources.
  10. Ollie Pearson
    Ollie Pearson None
    Sure. Let me share my screen. Give me a second. Right, can you see the list?
  11. Danielle Okonkwo
    Danielle Okonkwo None
    Yep, I see it.
  12. Trent Nakamura
    Trent Nakamura None
    Same here.
  13. Ollie Pearson
    Ollie Pearson None
    So, four areas. Referral data first: the referrer, the facility, the dates, the referral source and the status. Then the CRM, so the organisation records, the contacts and the notes the liaisons write. Then call data, which is the recordings and transcripts from the call recorder. And contract data, the agreements with each referring hospital and physician group. Those are the four we scoped at the start.
  14. Marisol Vega
    Marisol Vega None
    And the helpdesk? I saw intake tickets in the draft.
  15. Ollie Pearson
    Ollie Pearson None
    Yes, and this is the one I wanted to flag. Patient services use the helpdesk for intake, so the tickets are linked to referrers, which is why they were included. But the tickets can carry patient fields, in the body and in some custom fields.
  16. Marisol Vega
    Marisol Vega None
    Which fields, specifically? I need names, not categories.
  17. Trent Nakamura
    Trent Nakamura None
    I pulled the field list this morning. So, bullet points. Patient name. Date of birth. Member ID. The diagnosis note. And there's a free-text box that people paste things into, which I can't vouch for.
  18. Marisol Vega
    Marisol Vega None
    The free-text box is the problem. I never accept 'we don't store that' without evidence, and a free-text box is precisely where people store what they were told not to.
  19. Danielle Okonkwo
    Danielle Okonkwo None
    Yeah, I've seen what gets pasted in there. Let's not go near it.
  20. Ollie Pearson
    Ollie Pearson None
    Agreed. So my proposal is we exclude the patient fields on intake tickets entirely, including the free-text box, at the connector. Only the ticket metadata comes through: the referrer it's linked to, the category, the status, the dates. The excluded columns are never pulled, so they never reach the index.
  21. Marisol Vega
    Marisol Vega None
    Never pulled, or pulled and then hidden? Those are different controls, and I will want to know which one I am signing.
  22. Ollie Pearson
    Ollie Pearson None
    Never pulled. The connector works from an allow-list of fields. Anything not on the list isn't requested in the first place. I'll write it down so you can check it, and we can show you a sample load afterwards so you're not just taking my word for it.
  23. Marisol Vega
    Marisol Vega None
    Please do. I want the allow-list in writing, and I want that document to be the record. Document the control.
  24. Hollie Grieve
    Hollie Grieve None
    So we'll put it in the scope document. Ollie drafts, I review, and Marisol signs off before the helpdesk connector is switched on. Nothing goes live on that source until she has.
  25. Marisol Vega
    Marisol Vega None
    That is acceptable.
  26. Trent Nakamura
    Trent Nakamura None
    Can I ask something on the allow-list? If the helpdesk admin adds a new custom field next month, does it just flow through?
  27. Ollie Pearson
    Ollie Pearson None
    No, and that's the benefit of an allow-list. A new field isn't on it, so it doesn't come through until somebody adds it deliberately. And adding it would be a change to the scope, which goes through Marisol.
  28. Marisol Vega
    Marisol Vega None
    Which is the answer I wanted. Scope creep must be challenged, and that makes it visible. Now, let me ask about the other sources. Does the call data include any recordings of patient calls?
  29. Danielle Okonkwo
    Danielle Okonkwo None
    No. These are liaison calls with referrers. Hospital case managers, physician offices. The patient-facing calls aren't in that recorder at all.
  30. Marisol Vega
    Marisol Vega None
    I believe you, Danielle, but a liaison on a call with a case manager may well mention a patient by name. That is the realistic risk.
  31. Danielle Okonkwo
    Danielle Okonkwo None
    Okay, fair. That does happen. Somebody says a first name, a room number. I can't promise it never does.
  32. Trent Nakamura
    Trent Nakamura None
    Which is a training point as much as a data point, honestly. We can brief the liaisons.
  33. Ollie Pearson
    Ollie Pearson None
    There are two things we can do there. One, we only connect the calls from the liaison team, not every recording in the account. Two, the transcripts are searchable but they aren't edited by us, so the control is really the selection of whose calls come in. I'd suggest we scope it to the liaison team's calls and leave it there.
  34. Marisol Vega
    Marisol Vega None
    Then I would like that written precisely: the calls of the referral relations liaisons only. Not the patient services team, not the wider recorder.
  35. Hollie Grieve
    Hollie Grieve None
    Noted. Ollie, can you capture that in the same document?
  36. Ollie Pearson
    Ollie Pearson None
    Yep, adding it now. Liaison calls only.
  37. Ollie Pearson
    Ollie Pearson None
    Sorry, bear with me, I'm just typing it up while you talk. Go on, carry on.
  38. Danielle Okonkwo
    Danielle Okonkwo None
    While Ollie types. Marisol, I know you won't love this question, but is the contract data okay? Those are agreements with the referring hospitals. It's all business terms.
  39. Marisol Vega
    Marisol Vega None
    Contracts between Quarrington and referring organisations are not my concern, provided they do not attach patient information. Do any of them attach patient lists or case examples?
  40. Danielle Okonkwo
    Danielle Okonkwo None
    Not that I know of. I'd say a couple of the older ones might have an exhibit with sample cases. I'd have to check.
  41. Marisol Vega
    Marisol Vega None
    Then that is an open item. Danielle, please check before the contract connector is enabled. If an exhibit contains cases, we exclude the exhibits.
  42. Danielle Okonkwo
    Danielle Okonkwo None
    I need this by Friday, so I'll get my team on it today. I'll have the answer for you well before then.
  43. Hollie Grieve
    Hollie Grieve None
    Lovely. And just so we're all clear, that's Danielle's action, with Marisol as the approver.
  44. Marisol Vega
    Marisol Vega None
    Correct. Now, so that I have it exactly right, let me state the scope as I understand it, and you will correct me. In scope are referral data, CRM data, call data limited to the liaison team, and contract data subject to the exhibit check. Patient fields on intake tickets are excluded, including the free-text box. Anything outside that list requires a written change to the scope, and it comes to me. Is that accurate?
  45. Ollie Pearson
    Ollie Pearson None
    That's exactly it. I'll put your wording into the document so it matches.
  46. Danielle Okonkwo
    Danielle Okonkwo None
    Works for me. Clear and simple.
  47. Trent Nakamura
    Trent Nakamura None
    Yep, good for the admin side too. It's the first time anyone has written down what the brain can and can't see here, so that's useful in itself.
  48. Hollie Grieve
    Hollie Grieve None
    Great. Then I'll say that's the main thing done, and we've got a fair bit of time left, so let's use it. Trent, I think you had something.
  49. Trent Nakamura
    Trent Nakamura None
    I do, and I should have led with it. Okay. When I looked at the referral extract against my own report, it doesn't tie to my numbers. The referral count by hospital for last quarter in the CRM is higher than what my report shows, for a handful of the bigger referrers. Not wildly, but enough that I noticed.
  50. Danielle Okonkwo
    Danielle Okonkwo None
    Higher in the CRM, so the liaisons are logging more than the report counts?
  51. Trent Nakamura
    Trent Nakamura None
    Possibly. Or the CRM has duplicates, or my report only counts referrals that reached admission. I don't know yet, and I don't want to guess. Which source wins? That's the question.
  52. Ollie Pearson
    Ollie Pearson None
    That's a good one to raise now rather than after go-live. The brain doesn't pick a winner on its own. It shows what each source says, and it can tell you where they disagree. But somebody at Quarrington has to decide what a referral is, and which system is the record for it.
  53. Trent Nakamura
    Trent Nakamura None
    Right. So I'll reconcile it. I'll take the quarter, line up the CRM against the admissions report by referrer, and list every mismatch. Then we can see whether it's duplicates, definitions or timing.
  54. Marisol Vega
    Marisol Vega None
    Trent, one point on that. Is any PHI in scope for the reconciliation extract itself?
  55. Trent Nakamura
    Trent Nakamura None
    No. It's at referrer level. Counts by hospital or physician group and by month. No patient rows. If I ever need to go down to individual referrals I'll do it inside our own environment and not send it anywhere.
  56. Marisol Vega
    Marisol Vega None
    Thank you. I would like that recorded as well.
  57. Danielle Okonkwo
    Danielle Okonkwo None
    Okay, but let me be the business voice for a second. What's the referral trend? Because that's what the leadership team asks me every single week, and right now it takes the team days to answer, and then we argue about which number is right.
  58. Hollie Grieve
    Hollie Grieve None
    And that's precisely the problem we want to take away. Once Trent's reconciliation is done and you've agreed the definition, the liaisons and the leadership team ask the brain and everyone gets the same answer. Until then I'd be careful about quoting anything out of it.
  59. Trent Nakamura
    Trent Nakamura None
    Agreed. I don't want to overstate what the data shows yet. For now I'd treat the CRM as showing activity, and my report as showing referrals that converted. Two different things, and we've been calling them both referrals.
  60. Danielle Okonkwo
    Danielle Okonkwo None
    Huh. Okay. That's actually a useful way to say it. Let's loop in the liaisons on the definition, because they're the ones who log it.
  61. Hollie Grieve
    Hollie Grieve None
    Good idea. Maybe we do a short session with a few of them, and Trent brings the list of mismatches so they can say what really happened on each one.
  62. Danielle Okonkwo
    Danielle Okonkwo None
    Yes. Next week, let's do it next week. I'll set it up.
  63. Ollie Pearson
    Ollie Pearson None
    Sorry, I've just gone through the scope draft again and I want to check one thing with Trent. On the referral data, which table are the referrals in? Is it the admissions system or the CRM?
  64. Trent Nakamura
    Trent Nakamura None
    Both, annoyingly. The referral record starts in the CRM when the liaison logs it, then the admissions system holds the later stages. They join on a referral reference. That reference is also what my report is built on.
  65. Ollie Pearson
    Ollie Pearson None
    Okay, that helps. So for the first connection I'd suggest we bring in the CRM side and the admissions side for referrals, and keep the join on that reference. Then your reconciliation and the brain are looking at the same keys.
  66. Trent Nakamura
    Trent Nakamura None
    I like that. It means I'm not rebuilding a second version of it.
  67. Marisol Vega
    Marisol Vega None
    Is the admissions system a new source? It was not on the original list I reviewed.
  68. Ollie Pearson
    Ollie Pearson None
    Good catch, and no, I shouldn't have said it so casually. It's not in the scope. What's in the scope is the referral data, and that's what I'm describing. If the admissions stage fields live in a different system then you're right, that's a change.
  69. Marisol Vega
    Marisol Vega None
    Then I would ask that we do not widen the list in the middle of a call. Trent, please confirm which system holds the referral stages and what fields would be needed. We will treat it as a change request.
  70. Trent Nakamura
    Trent Nakamura None
    Fair enough. I'll put it in writing. And I'll tell you now, it's only status and dates, no patient identifiers, but you'll want to see the field list, so you'll get the field list.
  71. Marisol Vega
    Marisol Vega None
    That is what I want.
  72. Hollie Grieve
    Hollie Grieve None
    Right, so that's a good example of the process working. Ollie, can you note it as an open change request, not part of the first load?
  73. Ollie Pearson
    Ollie Pearson None
    Done. First load is the four areas as Marisol stated them. Referral stages from the admissions system are held back pending her review.
  74. Hollie Grieve
    Hollie Grieve None
    Okay. Let me move us to people, because we've talked a lot about data and not much about who's going to use it. Danielle, who are the first users?
  75. Danielle Okonkwo
    Danielle Okonkwo None
    The liaisons first. They cover hospitals and physician groups across Illinois, Indiana and Wisconsin, and they're the ones who'll walk into a meeting with one view of the referrer. Then my leadership team, who just want answers fast. And then the patient services team, but only for the referral side, not the intake stuff.
  76. Hollie Grieve
    Hollie Grieve None
    That fits. Just so we're all on the same numbers, you're on Growth, so that's forty licensed users, and the order form is £50,000 a year.
  77. Danielle Okonkwo
    Danielle Okonkwo None
    Yes, forty seats, fifty thousand a year. That's what I took to leadership. Good, I just wanted to hear it said so I'm quoting it right.
  78. Trent Nakamura
    Trent Nakamura None
    Forty's tight if we go with every liaison and the leadership team and a few from patient services. I'll count heads. If it's more than that we'll know early.
  79. Hollie Grieve
    Hollie Grieve None
    No problem at all. Let's see real usage first. If you get close to the limit, come back to me and we'll talk about it. No pressure from my side.
  80. Danielle Okonkwo
    Danielle Okonkwo None
    Right. I'm not committing anything further today anyway. That's not my call alone.
  81. Hollie Grieve
    Hollie Grieve None
    Understood, and not asking.
  82. Marisol Vega
    Marisol Vega None
    Hollie, may I raise access and audit? I am content to discuss users, but I will not discuss commercial matters.
  83. Hollie Grieve
    Hollie Grieve None
    Of course, please. That's why I stopped there.
  84. Marisol Vega
    Marisol Vega None
    Thank you. I will need to be able to show an auditor who asked the brain what, and when. I need an audit trail. And I need that to be reviewable by me, read-only, without having to ask Trent to export it each time.
  85. Ollie Pearson
    Ollie Pearson None
    So the usage history is available to admins, so Trent can see it. Whether we can give you a read-only view directly is something I want to confirm rather than promise. I'll check what the options are and come back to you in writing.
  86. Marisol Vega
    Marisol Vega None
    That is the right answer. I would rather wait for an accurate one.
  87. Trent Nakamura
    Trent Nakamura None
    From my side, I'd like to see the same thing. If someone asks a strange question I want to know who it was before I get a call about it.
  88. Hollie Grieve
    Hollie Grieve None
    Fair. Ollie, that's on your list too.
  89. Marisol Vega
    Marisol Vega None
    And one more. The business associate agreement. It is in place, and I want it kept current. If the scope changes in any way, I will expect to see the agreement reviewed against the change, not afterwards.
  90. Hollie Grieve
    Hollie Grieve None
    Understood. Any change to scope triggers a review of the agreement before anything is switched on. I'll make sure that's written into how we run this.
  91. Marisol Vega
    Marisol Vega None
    Thank you.
  92. Danielle Okonkwo
    Danielle Okonkwo None
    Can I ask a practical one? When do the liaisons actually get to see anything? Because I've told them it's coming and they keep asking me.
  93. Ollie Pearson
    Ollie Pearson None
    So the order is: the scope document gets signed off, then the connectors are switched on one at a time, starting with the referral and CRM data, then the calls, then contracts once the exhibit check is done, and the helpdesk last, when Marisol's approved the allow-list. The liaisons would see the first pages once the CRM and referral data have loaded and Trent's checked they match.
  94. Danielle Okonkwo
    Danielle Okonkwo None
    So they won't see it until Trent's happy with the numbers.
  95. Trent Nakamura
    Trent Nakamura None
    That's my preference, yes. If the first thing a liaison sees doesn't tie to the report they've used for years, they stop trusting it and we never get that back.
  96. Danielle Okonkwo
    Danielle Okonkwo None
    Okay. I hate waiting, but you're right. A wrong number in front of a hospital is worse than no number. What do I tell them for now?
  97. Hollie Grieve
    Hollie Grieve None
    I'd tell them it's being set up carefully because of how sensitive the data is, and that the first view is coming once the numbers have been checked. I can put a few sentences together for you if that helps.
  98. Danielle Okonkwo
    Danielle Okonkwo None
    Please. Short ones. Thanks, that would help.
  99. Trent Nakamura
    Trent Nakamura None
    And once it's running I'd like to retire a few of the one-off report requests. At the moment I get asked for the same referral cut every other week. That's the thing I want to get rid of.
  100. Hollie Grieve
    Hollie Grieve None
    That's a good measure of success. We can look at it at the first check-in. How many of those requests are still coming to you.
  101. Trent Nakamura
    Trent Nakamura None
    I like that. I'll keep a tally from now so we have a before.
  102. Ollie Pearson
    Ollie Pearson None
    Let me read back what I've got in the document so we're not relying on memory. Scope: referral, CRM, liaison calls and contracts, with the exhibit check outstanding. Excluded: patient fields on intake tickets, including the free-text box, by allow-list at the connector. Held back: referral stages from the admissions system, pending Trent's field list and Marisol's review. Open: audit view for Marisol.
  103. Marisol Vega
    Marisol Vega None
    That matches my notes. I would add that I will review the document in full before signing and will not sign on the basis of this call alone.
  104. Hollie Grieve
    Hollie Grieve None
    Of course. You'll get it in writing, and you take the time you need.
  105. Marisol Vega
    Marisol Vega None
    I will. I would also like a sample of the load from the helpdesk, with the excluded columns visibly absent, before I confirm that control.
  106. Ollie Pearson
    Ollie Pearson None
    Sure. I'll run a small sample in a test area, nothing in production, and send it over with the allow-list so you can see the columns aren't there.
  107. Marisol Vega
    Marisol Vega None
    Good.
  108. Danielle Okonkwo
    Danielle Okonkwo None
    Can I just say, I came in a bit nervous about this call. I thought Marisol would shut it down. This was actually really constructive.
  109. Marisol Vega
    Marisol Vega None
    I do not intend to shut it down. I intend to make sure it is done properly. They are different things.
  110. Danielle Okonkwo
    Danielle Okonkwo None
    Ha. Noted. Message received.
  111. Hollie Grieve
    Hollie Grieve None
    I think that's the right way round, honestly. It's much easier to build it carefully at the start than to unpick it later.
  112. Trent Nakamura
    Trent Nakamura None
    Agreed. Fewer surprises for everyone.
  113. Hollie Grieve
    Hollie Grieve None
    Okay, let's pin down next steps so nobody leaves unsure. Ollie, you send the scope document with Marisol's wording and the allow-list, plus the sample load. When can that be with us?
  114. Ollie Pearson
    Ollie Pearson None
    The document I can send today, after the call. The sample load by early next week, as long as I can get the field list from Trent.
  115. Trent Nakamura
    Trent Nakamura None
    I'll send the field list for the admissions stages and the helpdesk tomorrow. And the reconciliation list by the end of next week. I'll reconcile it and tell you what I found, even if the answer is that my own report was wrong.
  116. Hollie Grieve
    Hollie Grieve None
    Which is a perfectly good outcome.
  117. Danielle Okonkwo
    Danielle Okonkwo None
    I'll check the contract exhibits by Friday and set up the liaison session for next week. And I'll send Marisol whatever I find, not the other way round.
  118. Marisol Vega
    Marisol Vega None
    Thank you, Danielle. I will review the scope document when it arrives and respond in writing, with any questions listed, within a few working days.
  119. Hollie Grieve
    Hollie Grieve None
    And from me, the short note for the liaisons, a summary of today's decisions for everyone, and I'll look into the read-only audit view with Ollie so that Marisol has a firm answer.
  120. Ollie Pearson
    Ollie Pearson None
    Yep, I'll check that with the team and come back with an answer rather than a maybe.
  121. Hollie Grieve
    Hollie Grieve None
    Anything we've missed? Anyone got anything they want to raise before we go?
  122. Trent Nakamura
    Trent Nakamura None
    Only that the scope statement should be the first page of whatever we send around. So if someone asks later what the brain can see, it's the first thing they read.
  123. Ollie Pearson
    Ollie Pearson None
    Good shout. Making it page one.
  124. Marisol Vega
    Marisol Vega None
    I have nothing further for now.
  125. Danielle Okonkwo
    Danielle Okonkwo None
    Nothing from me. This was great, thanks all. Really good progress. Thanks, Danielle, and I'll speak to you all next week.
  126. Hollie Grieve
    Hollie Grieve None
    Brilliant. Thanks, everyone. I'll send the notes this afternoon. Speak soon.
  127. Trent Nakamura
    Trent Nakamura None
    Cheers all. Trent.
  128. Ollie Pearson
    Ollie Pearson None
    Thanks all. Bye for now.
  129. Marisol Vega
    Marisol Vega None
    Good afternoon. Thank you.

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
Organisations150
People at customers573
BB-Demo staff48
Calls1,382
Email threads2,122
Support tickets789
Documents850
Deals217
Invoices187
Events49
News items84

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.

HelpAsk B

Ask B

B-Brain · read-only