B-Brain
Callie Brennan

Brimscombe Energy / BB-Demo – Onboarding

Callcompleted

Brimscombe Energy logo Brimscombe Energy · 2025-03-18 13:15

Onboarding call on 18 Mar 2025. Siân Pritchard and Nikhil Rao agree connector fixes, access, SSO and a three-wave rollout. £115k contracted value matches invoices. The complaints recorder is not yet connected.

What was said

What this says

Current to 13 Oct 26

Onboarding call on 18 Mar 2025. Siân Pritchard and Nikhil Rao agree connector fixes, access, SSO and a three-wave rollout. £115k contracted value matches invoices. The complaints recorder is not yet connected.

What happened: Callie Brennan reviewed connector status, billing field mapping, access roles and rollout. One billing mapping was amber after a schema change, and complaints calls were only partly indexed.

Customer view: Siân wants value measured before it is claimed. She called it the smoothest implementation she has done.

Commercial: Order form shows one hundred and eighty licensed users, inside the Enterprise allowance, at £115k a year matching invoices. The on-site training day add-on was offered but deferred.

Watch: The complaints wave depends on a recorder token, and Nikhil is the only admin. A second admin is to be named.

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

Themes

Current to 9 Oct 26
Theme
Enterprise onboarding progress
Importance
praise
Sentiment
positive
Voice
champion

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Nikhil Rao sends the new billing column names in writing so Callie Brennan can re-map the connector.
  • Siân Pritchard introduces Callie to the owner of the complaints recorder workspace and chases the token.
  • Callie Brennan sends the written summary that afternoon and holds a check-in the following Tuesday.

Risks

Current to 9 Oct 26
  • The complaints recorder token could slip, which delays the complaints wave the business has been promised.
  • Nikhil is the only admin, so the platform depends on one person until a second is named.
  • The billing mapping is amber, and stale data can go unnoticed if nobody watches the refresh log.

Opportunities

Current to 9 Oct 26
  • The on-site training day add-on is available and may be revisited after the second wave.
  • Questions asked by team give Siân the adoption evidence she wants for the business case.
  • Connecting the complaints recorder workspace deepens use of the brain for regulated complaint handling.

Transcript

  1. Callie Brennan
    Callie Brennan None
    Hello, can you both hear me alright? I've got the little green bar moving on my side, so I think we're live.
  2. Siân Pritchard
    Siân Pritchard None
    Loud and clear, Callie. Good afternoon. I think Nikhil is just joining, he was finishing something in the warehouse.
  3. Nikhil Rao
    Nikhil Rao None
    Here. Sorry. A load ran long and I wanted to see it finish. Can you hear me?
  4. Callie Brennan
    Callie Brennan None
    Perfectly. Don't apologise, that's exactly the sort of thing I want to hear about later. How's the week been, Siân? Still raining in Gloucester?
  5. Siân Pritchard
    Siân Pritchard None
    Grey, but dry, which is a win for March. Busy though. The key account team asked the brain about site contracts on Monday, and the collections team asked it which customers had open complaints before they rang them. First time they've done that without sending me a spreadsheet.
  6. Callie Brennan
    Callie Brennan None
    That's lovely to hear. Right, so here's the plan for the next forty minutes or so. First, where each connector stands. Second, the field mapping for sites, contracts and customers, because that's where your one view lives. Third, access and roles, and what I need from your side before we switch on the next refresh. Then handover and who owns what. Does that suit?
  7. Siân Pritchard
    Siân Pritchard None
    That suits. I'd add one thing at the end, if there's time: how we bring the complaints team on, in waves, so we don't flood the helpdesk.
  8. Callie Brennan
    Callie Brennan None
    Done, I'll put it under rollout. Nikhil, anything you want on the list?
  9. Nikhil Rao
    Nikhil Rao None
    Which role has access. That's my list. Everything else follows from it.
  10. Callie Brennan
    Callie Brennan None
    Ha, fair. Then we'll start there, actually. I'll share my screen. Can you see the connector status page?
  11. Siân Pritchard
    Siân Pritchard None
    Yes, I can see it. Lots of green.
  12. Callie Brennan
    Callie Brennan None
    Lots of green, one amber, and the rest are waiting on me or on you. So, the CRM connector, the helpdesk, the call recorder and Microsoft 365 are all loaded and indexed. The accounting system is connected but I've only pulled the customer and invoice objects so far. The amber one is the billing system, and that's the one I want to talk about.
  13. Nikhil Rao
    Nikhil Rao None
    I checked the load history this morning. The billing extract landed, but the contract table had a schema change last week. Two columns renamed. That's why your mapping is amber.
  14. Callie Brennan
    Callie Brennan None
    Right, that explains it. Thank you, that saves me an hour. Which columns?
  15. Nikhil Rao
    Nikhil Rao None
    The supply start and the supply end. They were separate by meter point, now they're by site contract. I'll put the new names in the channel after the call. In writing.
  16. Callie Brennan
    Callie Brennan None
    In writing is exactly what I need. I never touch a mapping from a verbal, and I'd rather not guess at a column. Once I have those names I'll re-map and tell you what changed.
  17. Siân Pritchard
    Siân Pritchard None
    Can I ask, because this is the bit the business cares about, when that's fixed, what does a key account manager see when they open a business customer? I want to be able to say it plainly to them.
  18. Callie Brennan
    Callie Brennan None
    Good question, and I'll show you rather than describe it. Give me a second. This is the sandbox view of one test customer, so not real data. At the top is the organisation, then every site underneath it, each site's contract and its end date, then the calls and emails tied to the account, then open tickets, then the latest bills from the accounting system. All on one page.
  19. Siân Pritchard
    Siân Pritchard None
    One customer, one view. That's it. That's what I've been saying to people for a year and they've been nodding politely.
  20. Callie Brennan
    Callie Brennan None
    Well, now they get to click on it. What I'd flag is that the page is only as good as the mapping underneath. If a site belongs to two parent companies in your billing system, the brain will show it twice, and I'd want to know which parent is right before we go live to the teams.
  21. Nikhil Rao
    Nikhil Rao None
    That happens. Not often. Sites that changed hands mid-contract. I can pull a list of the ones with two parents.
  22. Siân Pritchard
    Siân Pritchard None
    Do that and send it to me as well, Nikhil. The complaints team will know which ones are real. Some of them will be live disputes.
  23. Nikhil Rao
    Nikhil Rao None
    Okay. Tomorrow, once I've tested the query. I'm not sending a list I haven't run twice.
  24. Callie Brennan
    Callie Brennan None
    Perfect. That maps cleanly onto my next step, which is access. So, before we switch on the refresh for the billing connector, what I need from your side is a service role in your Snowflake account, scoped to the schemas we've listed, read only on the source side, and write only to the brain's own schema. Nikhil, you've seen the role request?
  25. Nikhil Rao
    Nikhil Rao None
    I've seen it. I trimmed it. You asked for read on the whole finance schema. I'm giving you the four tables you need and nothing else.
  26. Callie Brennan
    Callie Brennan None
    That's better than what I asked for, honestly. I'd rather have less access and be told what's missing than more access I don't use. Can you confirm the role name in writing, and I'll note it in the setup document?
  27. Nikhil Rao
    Nikhil Rao None
    I'll write it in the ticket, not email. Auditor can follow a ticket.
  28. Siân Pritchard
    Siân Pritchard None
    He does love an auditor. Mind you, so does the regulator, so I'm glad.
  29. Callie Brennan
    Callie Brennan None
    Same here. Okay, the second thing on access is single sign-on. You're on Enterprise, so you've got SSO and SCIM included. Nikhil, who owns the identity side?
  30. Nikhil Rao
    Nikhil Rao None
    A colleague in IT. I'll introduce you. They'll want the metadata file and a test group first. We don't turn on provisioning for everyone on day one.
  31. Callie Brennan
    Callie Brennan None
    Sensible. We'll do a test group, confirm the sign-in works, confirm a leaver is removed when they're removed in your directory, and then widen it. I'll write that as three steps with a date against each once your colleague has picked it up.
  32. Siân Pritchard
    Siân Pritchard None
    How many people are we actually licensing here? I keep saying a hundred and something and I'd rather quote the real number.
  33. Callie Brennan
    Callie Brennan None
    It's one hundred and eighty licensed users on the order form, which is inside the Enterprise allowance. And the contracted value is £115,000 a year, matching what's been invoiced, so no surprises there.
  34. Siân Pritchard
    Siân Pritchard None
    Good. Because the business will ask what the £115,000 a year is buying, and I'd like to answer with evidence, not enthusiasm. Let's measure it before we claim it.
  35. Callie Brennan
    Callie Brennan None
    I'd say that's the right instinct. What would you measure first?
  36. Siân Pritchard
    Siân Pritchard None
    Two things. How long it takes a complaints handler to pull together the history of a business customer before they reply, and how often the key account team goes into the brain before a renewal conversation. I've got a rough baseline for the first from an audit last year. The second I'll have to count from now.
  37. Callie Brennan
    Callie Brennan None
    Then the questions asked will be your friend. The brain keeps a count of questions by team and by person, so we can show you adoption by team without anyone filling in a form. I'll make sure that page is switched on for you as admin.
  38. Nikhil Rao
    Nikhil Rao None
    Who sees it by person? I'm not sharing individual names with managers by default.
  39. Callie Brennan
    Callie Brennan None
    Admins only by default, and you decide what to open up. I'd suggest team totals for managers and keep names with you and Siân. We can change it any time.
  40. Nikhil Rao
    Nikhil Rao None
    Good.
  41. Callie Brennan
    Callie Brennan None
    Right, let me move to the refresh, because I know it's the thing you care about, Nikhil. Once the billing mapping is sorted and the role is confirmed, I'll run the first full refresh for that connector in the evening, and I want it complete before the nightly window closes. The commitment is that the nightly refresh is done by 07:00 your time on business days.
  42. Nikhil Rao
    Nikhil Rao None
    My loads finish well before that. Normally. If yours collides with mine, which one yields?
  43. Callie Brennan
    Callie Brennan None
    Yours go first. I'll schedule after your loads, not alongside them, and I'll read your load history before I trigger anything. If your job is late, mine waits and I tell you it waited. I'd rather arrive late than make you reconcile two things at six in the morning.
  44. Nikhil Rao
    Nikhil Rao None
    That's acceptable.
  45. Siân Pritchard
    Siân Pritchard None
    He means thank you.
  46. Nikhil Rao
    Nikhil Rao None
    I mean acceptable.
  47. Callie Brennan
    Callie Brennan None
    I'll take it. Okay, so let me do the other thing I wanted to cover, which is the call recorder. The calls are indexed, but I noticed the complaints team's calls are only partly there. Siân, do you know why?
  48. Siân Pritchard
    Siân Pritchard None
    I do, actually. Their recordings sit on a separate recorder licence, the older one, and nobody's connected it. I should have said. I assumed the call recorder was one thing.
  49. Callie Brennan
    Callie Brennan None
    That's a really useful catch, and it matters, because complaints calls are exactly the ones you said you can't miss a deadline on. Is it a different system, or the same one with a different workspace?
  50. Nikhil Rao
    Nikhil Rao None
    Same vendor. Different workspace. Different admin. I'd need to ask for a token and I'm not asking for one until I know it's wanted.
  51. Siân Pritchard
    Siân Pritchard None
    It's wanted. Please. I'll tell the owner of that workspace this afternoon that you'll be in touch, so it doesn't come out of nowhere.
  52. Callie Brennan
    Callie Brennan None
    That's the fourth thing on my list for you then, and I'll put the owner's name in the setup note once I have it. What I'll do is not start that connector until written access arrives, same as the others. And I'll check how it sits against your connector allowance so there's no surprise.
  53. Nikhil Rao
    Nikhil Rao None
    We have room. Twenty connectors in Enterprise, I count fewer than that in use.
  54. Callie Brennan
    Callie Brennan None
    Right, you're well inside it. Good. Now, handover. This is the bit I care about most, honestly, because the point of onboarding is that you can run the thing without me. By the end I want Nikhil able to re-run a connector, read the refresh log and add a user without opening a ticket.
  55. Nikhil Rao
    Nikhil Rao None
    I can already read the log. I'd want to see what a failed mapping looks like before it happens, not after.
  56. Callie Brennan
    Callie Brennan None
    Then let's break one, on purpose, in the sandbox. I'll do it now if you've got ten minutes. I'll rename a column in a test table, run the connector, and you'll see what it says.
  57. Nikhil Rao
    Nikhil Rao None
    Go on.
  58. Callie Brennan
    Callie Brennan None
    Okay. Renaming the column now. Running the connector. Give it a moment, it takes a little while on the test data.
  59. Callie Brennan
    Callie Brennan None
    There. See the status? It doesn't say failed, it says mapping needs review, and it lists the field it can't find and the one it thinks is the nearest match. It won't guess for you. It stops, and records stay as they were last time, so nobody queries half a table.
  60. Nikhil Rao
    Nikhil Rao None
    That's the behaviour I wanted. It holds the last good load.
  61. Siân Pritchard
    Siân Pritchard None
    So if the billing system changes again, the teams see yesterday's data, not a gap.
  62. Callie Brennan
    Callie Brennan None
    Yesterday's data, flagged as such, and you'd see it on the admin page. What I'd say, though, and I want to be straight about this, is that yesterday's data can go stale quietly if nobody's looking. So I'd ask Nikhil to glance at that page each morning for the first few weeks.
  63. Nikhil Rao
    Nikhil Rao None
    I'll set an alert on the refresh log rather than rely on glancing.
  64. Callie Brennan
    Callie Brennan None
    Even better. Now, rollout. Siân, you wanted to talk about waves.
  65. Siân Pritchard
    Siân Pritchard None
    Yes. My thinking is key account first, because they've been asking longest and they're the most forgiving. Then collections. Then complaints last, because the stakes are highest and I want the mapping proven before they rely on it for a deadline.
  66. Callie Brennan
    Callie Brennan None
    I'd go the same way. And a gap of a couple of weeks between each wave, so you can see what questions people actually ask and fix the mapping behind them. One thing I'd add is a short training session per team, not a big launch. Thirty minutes of showing them their own customers, not a demo of mine.
  67. Siân Pritchard
    Siân Pritchard None
    On their own customers. Yes. That's what will land. They won't care about a test customer.
  68. Callie Brennan
    Callie Brennan None
    Agreed. So for each wave I'd want a nominated person in the team who gets a bit more time with me, a go-to for the others. Can you name them, Siân, or is that too early?
  69. Siân Pritchard
    Siân Pritchard None
    For key account I can, today. For the other two I'll need to ask. I'd rather not name someone and then find they're on leave for the month.
  70. Callie Brennan
    Callie Brennan None
    Completely fair. Send me key account's name and I'll fold it in. And for complaints, one more thing, because you mentioned the regulator's rules earlier. Is there a specific report or view they must be able to produce from the brain?
  71. Siân Pritchard
    Siân Pritchard None
    There is. For each complaint they have to show when it was received, what was said, who handled it and when the response went. The deadline isn't negotiable. So what I want is for the brain to show that timeline from the helpdesk and the call recorder together, without anyone copying and pasting.
  72. Callie Brennan
    Callie Brennan None
    Then that's a page we build with you, not for you, and we do it before complaints go live. I'll put it in the plan as its own step, with Nikhil checking the data underneath and you checking the page against a real complaint, an old closed one.
  73. Siân Pritchard
    Siân Pritchard None
    A closed one. Yes. I've got three in mind that were awkward. If it handles those, it handles anything.
  74. Nikhil Rao
    Nikhil Rao None
    Awkward ones need the call recording connector first.
  75. Callie Brennan
    Callie Brennan None
    They do, so that's the ordering. The complaints workspace token comes first, then I connect it, then we test the timeline. I'll write that so nobody has to remember it.
  76. Siân Pritchard
    Siân Pritchard None
    Can I ask about the helpdesk side, while we're here? We had one ticket with you in the last month, it was only a how-to question, but I wasn't sure it was answered properly.
  77. Callie Brennan
    Callie Brennan None
    Which one was it? Do you remember what you asked?
  78. Siân Pritchard
    Siân Pritchard None
    How to save a search so the whole team can use it, rather than each person rebuilding it.
  79. Callie Brennan
    Callie Brennan None
    Right. So there are saved searches and there are shared pages. A saved search stays with the person unless they share it to a team space. If you want the whole team to open the same thing, a shared page is the better route, and I'll show you in the next session. I'd rather show it than leave you with a paragraph.
  80. Siân Pritchard
    Siân Pritchard None
    Show me. Please. I'd like to be able to do it myself in front of the teams.
  81. Callie Brennan
    Callie Brennan None
    Lovely. Let me do it now, quickly. I'll create a page from a search, name it, and then set who can see it. There, share with team, and I pick key account. And now Nikhil, from your admin side, you can see who has it and take it back if you need to.
  82. Nikhil Rao
    Nikhil Rao None
    I see it. It's listed under the team space. Can I stop people creating shared pages in the regulated areas?
  83. Callie Brennan
    Callie Brennan None
    You can restrict it by space. So complaints could be locked to pages that you or Siân publish, and everyone else reads. I think that's wise for the complaints team, at least at the start.
  84. Siân Pritchard
    Siân Pritchard None
    I'd go with that. Publish centrally, read locally. At least until I trust it.
  85. Callie Brennan
    Callie Brennan None
    That's the setup I'd put in the note, then. Okay, I want to make sure we've covered the data side properly before I go to next steps. Nikhil, anything from your Snowflake account that worries you? Cost, warehouse size, concurrency?
  86. Nikhil Rao
    Nikhil Rao None
    Warehouse size, yes. I want the brain on its own warehouse so I can see what it costs separately. Not sharing with the finance reporting jobs.
  87. Callie Brennan
    Callie Brennan None
    Agreed, and it's the cleaner design anyway. Give it its own, name it so it's obvious, and put it on an auto-suspend. I'll tell you what size we've run on for similar volumes, and then you can adjust once you've seen the first week of load.
  88. Nikhil Rao
    Nikhil Rao None
    I'd rather start small and go up than the other way.
  89. Callie Brennan
    Callie Brennan None
    Same. Start small, watch it, move up if the refresh runs past the window. Never the other way round.
  90. Siân Pritchard
    Siân Pritchard None
    Callie, can I check where we are on time? I'm conscious we've got a few minutes and I want to be clear on who's doing what.
  91. Callie Brennan
    Callie Brennan None
    Of course, we're about two thirds through, so good timing. Let me read it back and you tell me if I've got it wrong. Nikhil: the new column names in writing, the list of sites with two parents, the role name in the ticket, a dedicated warehouse, and an introduction to your colleague in IT for SSO. Siân: the name for key account, an introduction to the owner of the complaints recorder workspace, and the three awkward closed complaints for the test. Me: re-map the billing connector once the names arrive, schedule the refresh after your loads, build the complaints timeline page with you, and write the setup note.
  92. Nikhil Rao
    Nikhil Rao None
    That's right. I'd add one thing to mine. I'll tell you if anything in production is going to change, so you're not surprised again. Not on a Friday.
  93. Callie Brennan
    Callie Brennan None
    Never on a Friday, I've got that written already. Thank you.
  94. Siân Pritchard
    Siân Pritchard None
    And mine's right, though I'd say the key account name will be today, the owner introduction tomorrow, and the closed complaints by the end of the week. Is that quick enough for you?
  95. Callie Brennan
    Callie Brennan None
    More than quick enough. The only thing that's tight is the complaints connector, because it's the last piece, so if the token slips, the complaints wave slips with it. I'd rather tell you that now than in three weeks.
  96. Siân Pritchard
    Siân Pritchard None
    Understood. Then I'll chase the token myself. I'm not letting that deadline drift. The complaints wave is the one I've promised the business.
  97. Nikhil Rao
    Nikhil Rao None
    I'll chase it as well, but access goes through the right route. No tokens by email, no shared passwords. It goes in the ticket, with a named owner.
  98. Callie Brennan
    Callie Brennan None
    That's exactly what I'd want. Okay, a couple of smaller things while I've got you. Training. You've got the onsite training day as an add-on available to you, if you'd like it, but for now I'd suggest we use the team sessions we talked about, and look again once the second wave is in.
  99. Siân Pritchard
    Siân Pritchard None
    Team sessions first. I'll tell you if people want more.
  100. Callie Brennan
    Callie Brennan None
    Good. And the other small thing is the admin count. Right now it's Nikhil as the only admin, and you, Siân, as champion with elevated rights. I'd like a second admin named, so you're not relying on one person for the platform if someone's on holiday.
  101. Nikhil Rao
    Nikhil Rao None
    Fair. Someone in my team. I'll name them in the ticket. They'll need the same training as me.
  102. Callie Brennan
    Callie Brennan None
    I'll make time for them. It's an hour, no more, since you'll have covered the main bits by then. And honestly, it's the single most useful thing for the long run, because it means the brain doesn't depend on one person.
  103. Siân Pritchard
    Siân Pritchard None
    I couldn't agree more. And it's less of a worry for me too.
  104. Callie Brennan
    Callie Brennan None
    Right. Let me show you one last thing, then we'll wrap up. This is the setup note I'm keeping. It's a living document, you can see it's got the connectors, the roles, the mapping decisions and a date against each step. At handover I'll give you the final version and it's yours.
  105. Nikhil Rao
    Nikhil Rao None
    Can I add comments?
  106. Callie Brennan
    Callie Brennan None
    Yes. I'll share it with edit rights for both of you. If you spot something wrong, mark it, and I'll fix it before I mark the step done.
  107. Siân Pritchard
    Siân Pritchard None
    That's very clear. Honestly, Callie, this has been the smoothest implementation I've done. I wasn't expecting that, and I've been burnt before.
  108. Callie Brennan
    Callie Brennan None
    That's kind, thank you. I'd say it's because you've had Nikhil on the technical side from the start, and because you both give me answers in writing. It makes my job much easier.
  109. Nikhil Rao
    Nikhil Rao None
    It's the only way I know how to do it.
  110. Siân Pritchard
    Siân Pritchard None
    Diolch, Callie. That's a lot to be getting on with, but it feels like the right list.
  111. Callie Brennan
    Callie Brennan None
    Let me finish with the dates, because I like a date against every step. I'll send the written summary this afternoon. Billing re-map the day after Nikhil sends the column names. First full refresh for that connector the evening after. Complaints recorder connection as soon as the token is in the ticket. And I'd like us to speak again next week for a short check on how the first wave is going. Does Tuesday suit?
  112. Siân Pritchard
    Siân Pritchard None
    Tuesday suits me, same time works.
  113. Nikhil Rao
    Nikhil Rao None
    Same time. I'll have the site list by then.
  114. Callie Brennan
    Callie Brennan None
    Brilliant. Is there anything else either of you wanted to raise that we haven't touched? Worries, anything the business has said to you?
  115. Siân Pritchard
    Siân Pritchard None
    Only that expectations are high. People have heard me talk about this at the events and now they want it yesterday. I'd rather go a bit slower and get it right.
  116. Callie Brennan
    Callie Brennan None
    I'd rather that too. We'll keep the waves as they are, and I'll tell you honestly if any step is running late, rather than let you find out from the teams.
  117. Nikhil Rao
    Nikhil Rao None
    Nothing else from me.
  118. Callie Brennan
    Callie Brennan None
    Then thank you both. I know it's been a long call. I'll get that summary out within the hour. Speak Tuesday.
  119. Siân Pritchard
    Siân Pritchard None
    Diolch, Callie. Speak Tuesday. Cheers, Nikhil.
  120. Nikhil Rao
    Nikhil Rao None
    Cheers. Bye.
  121. Callie Brennan
    Callie Brennan None
    Bye both. Thanks, everyone.

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