B-Viz
Hamza Akhtar

Quabbin Clinical Research / BG-Demo – Training

Callcompleted

Quabbin Clinical Research logo Quabbin Clinical Research · 15 Jun 2026 14:45

First Enterprise training session with Meredith Sullivan and Rachel Feldman. Positive: a single answer joined an invoice and an open issue. Open points: a connector alert request and a permissions check.

What was said

What this says

As at Fri 9 Oct 2026

First Enterprise training session with Meredith Sullivan and Rachel Feldman. Positive: a single answer joined an invoice and an open issue. Open points: a connector alert request and a permissions check.

What happened: Hamza ran pages, chat and search on Quabbin's own data, then a practice block. Rachel found two naming mismatches between systems and one question that was too broad.

Customer view: Meredith wants one portfolio view per sponsor and said sponsor separation is non-negotiable. She said more sponsor relations people are logging in every day.

Commercial: Adoption is building on the Enterprise tier, and freshness by 07:00 matters to Rachel because study managers will ask. Hamza did not promise the connector nudge.

Watch: Rachel's permissions list and the group check are open. A source that stops loading would be the first sign of staleness.

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

Themes

As at Fri 9 Oct 2026
Theme
Hands-on onboarding training
Importance
praise
Sentiment
positive
Voice
champion

Who was there

BG-Demo

Them

Follow-up

Next steps

As at Fri 9 Oct 2026
  • Rachel sends the permissions list on the day of the call so Hamza can check the groups with her.
  • Hamza looks into a connector alert and writes up the study name aliases.
  • Hamza runs the dashboards session next, with Rachel and Meredith bringing colleagues.

Risks

As at Fri 9 Oct 2026
  • A connector that stops loading could leave data stale unnoticed, and no alert exists yet.
  • Sponsor-level permissions are non-negotiable and the groups still need checking.

Opportunities

As at Fri 9 Oct 2026
  • Growing daily use by sponsor relations staff supports a case for wider adoption.
  • A single sponsor view could become the team's standard way of working.

Transcript

  1. Hamza Akhtar
    Hamza Akhtar
    Hello, can you hear me all right? I think I'm on mute on the wrong thing. Afternoon from London.
  2. Meredith Sullivan
    Meredith Sullivan
    We can hear you fine. Good morning from Boston. Rachel's just getting her laptop to share, give her a second.
  3. Rachel Feldman
    Rachel Feldman
    Hi, Hamza. Yes, sorry, I'm here. The conference room screen is fighting me. Okay, I'll just use my own.
  4. Hamza Akhtar
    Hamza Akhtar
    No problem at all. Fine weather over there? It's grey and drizzly here, so I'm jealous in advance.
  5. Meredith Sullivan
    Meredith Sullivan
    It's actually lovely. Sponsor update first, if that's okay, because it frames why we're doing this. Two of our sponsors asked this week for a single view of their open issues, and the answer today is still a lot of spreadsheets. One portfolio, one story. That's what I want the teams to get out of this training.
  6. Hamza Akhtar
    Hamza Akhtar
    That's a good way in. So today is the first of the hands-on sessions. I'll keep it practical: pages, chat and search, and then we'll try a few real questions on your data. Rachel, you're the admin, so I'll flag the bits that matter for you as we go.
  7. Rachel Feldman
    Rachel Feldman
    Great. I should say, the connectors are mostly in, but I've got a couple of questions about how often the data refreshes. Our study managers will ask me.
  8. Hamza Akhtar
    Hamza Akhtar
    Yeah, good one. On Enterprise the nightly refresh is done by seven in the morning your local time on business days. So when your people log in at the start of the day, it's yesterday's close of play. If it's ever late, tell me, because on your tier that's something we take seriously.
  9. Rachel Feldman
    Rachel Feldman
    Okay, that's what I needed. Mm. I'll tell them that.
  10. Hamza Akhtar
    Hamza Akhtar
    Right, let me share. You should see the home screen. Can you see it?
  11. Meredith Sullivan
    Meredith Sullivan
    We see it. It's a bit small. Can you zoom?
  12. Hamza Akhtar
    Hamza Akhtar
    Bigger now? Good. So this is a sponsor page. Each sponsor gets one, and it pulls together the studies, the open issues from the helpdesk, recent calls and the invoice status. Nothing here is copied out of Snowflake, it's all read from your own account.
  13. Meredith Sullivan
    Meredith Sullivan
    And this is only ever one sponsor at a time, right? I can't have anything from one showing up on another's page. That is non-negotiable for us.
  14. Hamza Akhtar
    Hamza Akhtar
    Correct. A page is scoped to one sponsor, and permissions follow that. Rachel, we set the groups up during onboarding, and I'd like you to double-check them with me later today. That's the sort of thing I'd rather we look at together than assume.
  15. Rachel Feldman
    Rachel Feldman
    Yes. I've got a list of who sits where. I'll send it over after this.
  16. Hamza Akhtar
    Hamza Akhtar
    Perfect. Now, chat. This is the bit people tend to like most. Let me type a question. Which open issues does this sponsor have, and which of those have had no update for a while?
  17. Meredith Sullivan
    Meredith Sullivan
    Oh, that's good. What does the sponsor know? That's the question I always get asked. Can it show me when we last spoke to them about each issue?
  18. Hamza Akhtar
    Hamza Akhtar
    It can, as long as the call is in the recorder and connected. Let me follow up. When did we last discuss these with the sponsor? There. You can see each answer links back to the call or the ticket it came from, so you can click through and check.
  19. Rachel Feldman
    Rachel Feldman
    The citations are what the study managers will care about. They won't trust it otherwise.
  20. Hamza Akhtar
    Hamza Akhtar
    Agreed, and I'd encourage them to check the source the first few times. It builds the habit. Okay, over to you. Meredith, pick a sponsor and ask something you'd normally ask your team on a Monday morning.
  21. Meredith Sullivan
    Meredith Sullivan
    Okay. Let me think. I'll ask where we stand on the open issues for one of our device sponsors, and whether any invoices are waiting. Typing now. Hold on, I'm a terrible typist.
  22. Meredith Sullivan
    Meredith Sullivan
    Oh wow, it found the invoice and the open issue in one answer. Rachel, look at this. That would've been three tabs and an email to finance.
  23. Rachel Feldman
    Rachel Feldman
    Yeah, that's the thing. Let me try one on the study side. I'll ask which studies have a connector gap on the data side. Hmm. It's saying it has nothing for one source. Is that a broken connector or just no data?
  24. Hamza Akhtar
    Hamza Akhtar
    Good catch, and good question. Click the connector status in the admin area. If records indexed are moving, it's just quiet. If it's flat for days, something changed on the source side. Can you share your screen on that?
  25. Rachel Feldman
    Rachel Feldman
    Sharing. There. It's loading, just slowly. I think the study management export is just quieter this week.
  26. Hamza Akhtar
    Hamza Akhtar
    Right, that looks healthy to me. It's showing recent loads. If you ever see it flat for a good while, raise a ticket and mention the connector name.
  27. Meredith Sullivan
    Meredith Sullivan
    Let's get ahead of it. Can we set something up so Rachel gets a nudge when a source stops loading?
  28. Hamza Akhtar
    Hamza Akhtar
    I'll look at what we can do there and come back to you. I don't want to promise the exact mechanism on the call. Let me note it.
  29. Hamza Akhtar
    Hamza Akhtar
    Okay, search now. Different from chat: it's for finding the thing you already know exists. Try typing a study name and a month.
  30. Rachel Feldman
    Rachel Feldman
    It returned the protocol amendment thread and the call where we discussed it. Nice. Filters on the left are useful.
  31. Meredith Sullivan
    Meredith Sullivan
    Can I save a search? I'd use the same one every week before sponsor calls.
  32. Hamza Akhtar
    Hamza Akhtar
    Yes, top right, the save icon. Name it something your team will recognise, because everyone in the group sees it. We'll do dashboards properly next time.
  33. Hamza Akhtar
    Hamza Akhtar
    Let's use the rest of the session as a proper practice block. I'll go quiet. Each of you try five real questions from your week, and write down anything that gives a strange answer. Don't tidy it, I want the messy ones.
  34. Rachel Feldman
    Rachel Feldman
    Okay, I've got three odd ones. Two are the same underlying cause, I think, a naming mismatch between two systems for the same study. The third I just can't explain.
  35. Hamza Akhtar
    Hamza Akhtar
    That's useful. Paste them into the shared notes. The naming one is a classic, and we can add an alias on our side. The third, let's look at it right now.
  36. Hamza Akhtar
    Hamza Akhtar
    So that was the question wording. It was too broad, and it answered a slightly different question. Try narrowing by sponsor and time and it behaves. Not your fault at all.
  37. Meredith Sullivan
    Meredith Sullivan
    That's reassuring. I'll tell the team to be specific. Honestly, I'm really pleased with how quickly people are picking this up. More of the sponsor relations people are logging in every day, and I want that to keep going.
  38. Hamza Akhtar
    Hamza Akhtar
    It's showing in the usage, too. Good sign this early on. So, next steps. Rachel sends the permissions list today. I'll check the groups with her, look at the connector alert idea, and write up the aliases. Next session we'll cover dashboards and sharing.
  39. Rachel Feldman
    Rachel Feldman
    Works for me. I'll book some of the study managers into that one.
  40. Meredith Sullivan
    Meredith Sullivan
    And I'll bring two of the account leads. Thanks, Hamza, this was really helpful. Talk soon.
  41. Hamza Akhtar
    Hamza Akhtar
    Brilliant, thanks both. Speak soon, cheers.

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

Help & Support

Open as a page

Help & Support

B-Viz 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
Organisations300
People at customers1,880
BG-Demo staff records (in post and leavers)65
Calls2,593
Email threads3,882
Support tickets1,502
Documents1,582
Deals403
Invoices365
Events49
News items147

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-Viz is the tool that reads its data.

Who to contact

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

Help

Ask B

B-Viz · read-only