Hamza Akhtar

Vellacott Payments / BB-Demo – Onboarding

Callcompleted

Vellacott Payments: documents logo Vellacott Payments: documents · 2025-09-19 14:30

Onboarding call on 19 Sep 2025. Tomasz Wiśniewski saw the brain join onboarding, partnership and complaints records and called it very good. His one concern is draft documents in the complaints folders. Rollout is staged by team.

What was said

What this says

Current to 11 Oct 26

Onboarding call on 19 Sep 2025. Tomasz Wiśniewski saw the brain join onboarding, partnership and complaints records and called it very good. His one concern is draft documents in the complaints folders. Rollout is staged by team.

What happened: Hamza Akhtar closed the previous actions, demoed one marketplace client page and walked through SSO, SCIM and user rollout. Every action ended with a named owner.

Customer view: Tomasz wants complaints, onboarding history and partnership notes in one place. He said the demo answer would normally take someone an hour or more, and Femi Olatunji noted that compliance will want the sources.

Commercial: Hamza said the licence is for one hundred and fifty users and usage is nowhere near it. Rollout goes partnerships, then merchant onboarding, then complaints, one team a week, with training requested from the CSM Daniel.

Watch: Tomasz does not want drafts in the complaints folders quoted as final. He owns the check with the complaints lead. SSO is only enforced after Femi's leaver and joiner test.

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

Themes

Current to 9 Oct 26
Theme
Onboarding, SSO and complaints
Importance
praise
Sentiment
positive
Voice
champion

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Tomasz asks the complaints lead to confirm there are no working drafts, answer by the end of the following week.
  • Femi runs the SSO leaver and joiner test early the following week, then Hamza enforces SSO.
  • Hamza asks the CSM Daniel for the first team training session the following week.

Risks

Current to 9 Oct 26
  • Draft documents in the complaints folders could be quoted by the brain as final answers.
  • SSO enforcement depends on Femi's leaver and joiner test being completed cleanly.

Opportunities

Current to 9 Oct 26
  • Staged rollout across partnerships, merchant onboarding and complaints can raise active users well within the licensed number.
  • Complaints dashboards owned by admins show the customer investing in the dashboards builder.

Transcript

  1. Hamza Akhtar
    Hamza Akhtar None
    Hello, both. Afternoon. Can you hear me?
  2. Femi Olatunji
    Femi Olatunji None
    Afternoon. Yes, fine. Tomasz is just joining, I can see him in the lobby.
  3. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Hello, hello. Sorry, previous meeting overran. I am here now. Good afternoon, Hamza.
  4. Hamza Akhtar
    Hamza Akhtar None
    No worries at all. Good to meet you properly, Tomasz. Femi's told me you like to start with the actions.
  5. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Yes. Let me be concrete. Three actions from last time. One, Femi sends the identity contact and the group names. Two, Femi sends the list of complaints folders. Three, Femi drops the temporary grant after the backfill. What's the status?
  6. Femi Olatunji
    Femi Olatunji None
    So, one is done, I sent it on Monday. Two is done as well, the complaints lead gave me the folders and I passed them to Hamza. Three, the backfill finished yesterday, so I dropped the grant this morning.
  7. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Good. All three closed. Hamza, you had actions also?
  8. Hamza Akhtar
    Hamza Akhtar None
    I did, two of them. The access summary for your security people, which went over on Friday, and the scoped shared drive connector. That one's built and has done its first load.
  9. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Excellent. So we have no floating actions. I like that. Now, what is the agenda today?
  10. Hamza Akhtar
    Hamza Akhtar None
    Three bits. First, a quick look at how the brain sees one of your marketplace clients across partnerships, onboarding and complaints. Second, SSO and SCIM going live. Third, who owns what once I step back.
  11. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Yes. The first is what I care about most. When a marketplace client complains, I want to see their onboarding history and the partnership notes in one place, not in four.
  12. Hamza Akhtar
    Hamza Akhtar None
    Right, that's exactly what we can show. Let me share. I'll use a client record from your data, and Femi, shout if anything looks wrong.
  13. Hamza Akhtar
    Hamza Akhtar None
    So, this is the page for one of your marketplace clients. Here you have the account notes from the CRM, here are the tickets from the helpdesk, and here the folder documents from complaints. The brain has joined them on the client name.
  14. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Mm. So complaints is here, below. That is the key part. Can I ask it a question, like a person would?
  15. Hamza Akhtar
    Hamza Akhtar None
    Please. Try something you'd really ask.
  16. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Okay. I type, which complaints from this client are still open and what did onboarding promise them about payout timing.
  17. Hamza Akhtar
    Hamza Akhtar None
    And there's the answer. It lists the open ones, with the source for each, and then pulls the line from the onboarding notes. You can click through to the original.
  18. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    That is very good. Femi, did you see? Normally this is one hour of work for someone. Maybe more.
  19. Femi Olatunji
    Femi Olatunji None
    Yeah, I saw. And the sources are there, which is what compliance will ask for. They'll want to know where an answer came from.
  20. Hamza Akhtar
    Hamza Akhtar None
    Always. Every answer carries its references, so nobody has to take it on trust.
  21. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    One concern. The complaints folders. I do not want drafts in there. If someone writes a draft response, and the brain quotes it as final, that is a problem.
  22. Hamza Akhtar
    Hamza Akhtar None
    Fair, and we scoped to the folders the complaints lead named, which should be the final record only. But it's worth a check. Femi, could you ask the complaints lead to confirm there are no working drafts in those folders?
  23. Femi Olatunji
    Femi Olatunji None
    Yes, I'll do it. Actually, can I put it on Tomasz? The complaints lead reports into his area.
  24. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Yes, fine. It is mine. I will ask the complaints lead, and I will have the answer before the end of next week. We close this today, I will message them straight after the call.
  25. Hamza Akhtar
    Hamza Akhtar None
    Brilliant, thanks. I'll write that down against your name.
  26. Hamza Akhtar
    Hamza Akhtar None
    Let me move to SSO. Femi, you've got the groups mapped. Can you tell me how the identity team feel?
  27. Femi Olatunji
    Femi Olatunji None
    They're comfortable. They had a couple of questions about how SCIM removes people when they leave, and I think the access summary answered those.
  28. Hamza Akhtar
    Hamza Akhtar None
    Good. So, deprovisioning is automatic. When someone's removed in your directory, their access to the brain goes at the next sync, and their seat is freed.
  29. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Good. And who tests it? What's the owner?
  30. Femi Olatunji
    Femi Olatunji None
    I can do that. I'll test with one leaver account and one new joiner and report back.
  31. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Okay. Femi, your name. When?
  32. Femi Olatunji
    Femi Olatunji None
    Early next week. Monday or Tuesday.
  33. Hamza Akhtar
    Hamza Akhtar None
    Perfect. I'll switch SSO to enforced once Femi has confirmed it's clean, not before. That way nobody's locked out on day one.
  34. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Good plan. Now users. Last quarter was almost nobody. Now there are many more. How many can we add in the first wave?
  35. Hamza Akhtar
    Hamza Akhtar None
    You're licensed for one hundred and fifty, and you're nowhere near it. So realistically as many as you like. I'd just stage it by team so you can train each group and answer their questions.
  36. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Yes. Partnerships first, since that is my team. Then merchant onboarding. Then complaints. One team each week.
  37. Femi Olatunji
    Femi Olatunji None
    That's sensible. It also means I'm not fielding everyone's questions at once.
  38. Hamza Akhtar
    Hamza Akhtar None
    Agreed. Daniel, who's your CSM, can run a short training for each team if you'd like. I'll pass that request over to him.
  39. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Yes please. That would be useful. Hamza, you send the request to Daniel, and I'd like the first session to be next week.
  40. Hamza Akhtar
    Hamza Akhtar None
    Done. I'll message him today.
  41. Femi Olatunji
    Femi Olatunji None
    One technical thing before we wrap. The dashboards builder. When the teams start making their own, who can edit them? I don't want twenty versions of the same complaints chart.
  42. Hamza Akhtar
    Hamza Akhtar None
    Good thing to settle early. Anyone in the working teams group can build, but you can set a small set of shared dashboards as owned by admins, and everyone else can copy but not overwrite. I'd do that for the complaints ones.
  43. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Yes. Do it. Complaints dashboards are owned by admins. Femi, you are the owner.
  44. Femi Olatunji
    Femi Olatunji None
    Fine. I'll set them up and tell the team they're read and copy only.
  45. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Good. So let me say the actions back. Me: ask complaints lead about drafts, answer by end of next week. Femi: SSO leaver and joiner test early next week, own the complaints dashboards. Hamza: SSO enforced after the test, request training from Daniel today. Correct?
  46. Hamza Akhtar
    Hamza Akhtar None
    That's all of it. I'll put it in the notes with the names against each one.
  47. Femi Olatunji
    Femi Olatunji None
    Sounds right to me.
  48. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Good. Thank you both. This is going well. Cheers, Hamza. Cheers, Femi.
  49. Hamza Akhtar
    Hamza Akhtar None
    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
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