B-Viz
Jordan Pike

Shilshole Software / BG-Demo – Demo

Callcompleted

Shilshole Software logo Shilshole Software · 18 Sep 2026 16:15

Theo Gallagher demoed B-Viz to Kristen Haugen and Jenna Lindstrom. Concerns were stale sources after a helpdesk move, access to call recordings and admin rights. Kristen will take it to her director.

What was said

What this says

As at Fri 9 Oct 2026

Theo Gallagher demoed B-Viz to Kristen Haugen and Jenna Lindstrom. Concerns were stale sources after a helpdesk move, access to call recordings and admin rights. Kristen will take it to her director.

What happened: Theo Gallagher ran a 60 minute demo with Jordan Pike, Kristen Haugen and new attendee Jenna Lindstrom, Support Operations Manager. It answered a berth invoice question from billing, the CRM and ticket history.

Customer view: Jenna worries the old helpdesk history did not come across cleanly after the move last spring. Kristen's biggest concern is who can see call recordings, and her director will ask that first.

Commercial: The by-person usage view showed one team lead asking a big share of questions, a key-person risk Kristen wants to spread. Jordan recommended the first weeks focus on connectors, and Kristen said chat can be switched on later.

Watch: Kristen's admin confirmation and Jenna's connector list are still open. No commercial decision was made.

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

Themes

As at Fri 9 Oct 2026
Theme
Demo, connectors and access
Importance
neutral
Sentiment
positive
Voice
champion

Who was there

BG-Demo

Them

Follow-up

Next steps

As at Fri 9 Oct 2026
  • Theo Gallagher to send the control reference and admin answer by end of day.
  • Jenna Lindstrom to send the connector list by Friday.
  • Kristen Haugen to confirm admin rights by email and take the demo to her director.

Risks

As at Fri 9 Oct 2026
  • Old helpdesk history may not have loaded cleanly, which would undermine trust in answers.
  • Access to call recordings is the director's first question and must be evidenced.
  • Admin rights and the connector owners are still unconfirmed.

Opportunities

As at Fri 9 Oct 2026
  • The stale source card answers Jenna's concern from last spring.
  • The by-person usage view gives Kristen an internal case to take to her director.

Transcript

  1. Theo Gallagher
    Theo Gallagher
    Can everyone see my screen? Good. Before we start, three open items from last time so we're aligned. Jenna owns the connector list, I owe the answer on where the data sits, and Kristen is confirming who needs admin rights. Jordan's keeping the commercial notes.
  2. Jenna Lindstrom
    Jenna Lindstrom
    Mine's mostly done. I've got the systems list, just not all the owners yet.
  3. Kristen Haugen
    Kristen Haugen
    And I'll confirm admin rights by email, I promise.
  4. Jordan Pike
    Jordan Pike
    Perfect. We've got an hour, so let's move.
  5. Theo Gallagher
    Theo Gallagher
    Great. I'll use a question you'd really ask. Something like: which customers asked about berth invoices last month, and what did we tell them? Kristen, is that close?
  6. Kristen Haugen
    Kristen Haugen
    Close. Yes, that's exactly it.
  7. Theo Gallagher
    Theo Gallagher
    Here we go. It's answering from three sources: billing, the CRM and the ticket history. You can see the source behind each line, so nobody has to take it on trust.
  8. Jenna Lindstrom
    Jenna Lindstrom
    Can I check something? Does it show the tickets from before we changed helpdesk?
  9. Theo Gallagher
    Theo Gallagher
    Good question. It should, as long as the old helpdesk export is connected. That's the connector list, which is on my list for you, Jenna.
  10. Jenna Lindstrom
    Jenna Lindstrom
    Right, that's what I've been worrying about. We moved systems last spring and I'm not sure the old history came across cleanly.
  11. Theo Gallagher
    Theo Gallagher
    That's the most common break I see. A connector that stops loading usually shows as a flat count of records. If the count stops moving, that's a broken source, and we'd catch it.
  12. Jordan Pike
    Jordan Pike
    And what does a broken source cost you? Sorry, I'm jumping ahead.
  13. Theo Gallagher
    Theo Gallagher
    No, that's fair, Jordan. It costs trust. People stop asking the tool when they think it's out of date.
  14. Kristen Haugen
    Kristen Haugen
    Who can see the call recordings in it? That's our biggest concern, honestly.
  15. Theo Gallagher
    Theo Gallagher
    Access follows the roles you set up in your own environment. I'll send the control reference for that today, and we can evidence it with the access logs, not just describe it.
  16. Kristen Haugen
    Kristen Haugen
    Good. My director will ask that before anything else.
  17. Jenna Lindstrom
    Jenna Lindstrom
    How many admins would we need? Realistically.
  18. Theo Gallagher
    Theo Gallagher
    For a team your size, a couple. Two at most to start. I'll put that in writing.
  19. Jenna Lindstrom
    Jenna Lindstrom
    And who does the day-to-day? The connectors, I mean.
  20. Theo Gallagher
    Theo Gallagher
    You, or a colleague in support operations. Someone checks the connectors each week, and the dashboard tells them which one has stalled.
  21. Kristen Haugen
    Kristen Haugen
    Okay. Can we see the usage side? Who's asking the questions?
  22. Theo Gallagher
    Theo Gallagher
    Yes. Let me pull the view by person, which you asked for earlier. Give me a moment, the demo data is a bit slow today.
  23. Theo Gallagher
    Theo Gallagher
    Right, here. Questions asked, by person and by team. One person asks a big share of the questions, which is worth knowing. If they left, that's a key-person risk.
  24. Kristen Haugen
    Kristen Haugen
    Oh, that's one of my team leads. Yes, that's interesting.
  25. Jordan Pike
    Jordan Pike
    That's the sort of thing that makes the case internally, isn't it? What would you do with it, Kristen?
  26. Kristen Haugen
    Kristen Haugen
    Spread the knowledge, I suppose. Make sure two people can answer the same question.
  27. Theo Gallagher
    Theo Gallagher
    Exactly. That's a conversation for the onboarding plan. Shall we look at the dashboards next?
  28. Jenna Lindstrom
    Jenna Lindstrom
    Yes please. Mine are the ones our managers actually look at.
  29. Theo Gallagher
    Theo Gallagher
    Here's a dashboard built from a sample onboarding checklist. Each card links back to the source, so your managers can click through and check it themselves.
  30. Jenna Lindstrom
    Jenna Lindstrom
    Can it show which connector is behind which card? Because when a card looks wrong, that's the first thing we check.
  31. Theo Gallagher
    Theo Gallagher
    It can. The source name sits under every figure. Let me show you a card with a stale source so you can see how it looks.
  32. Theo Gallagher
    Theo Gallagher
    Here's the stale one. The record count hasn't moved in weeks, and the card says so in plain words. That's the kind of thing we want surfaced before a customer notices.
  33. Jenna Lindstrom
    Jenna Lindstrom
    Good. That's exactly what would have saved us last spring.
  34. Jordan Pike
    Jordan Pike
    To be transparent, Jenna, that's why we'd recommend the first few weeks focus on connectors, not dashboards.
  35. Jenna Lindstrom
    Jenna Lindstrom
    Agreed. I'd rather fix the sources first.
  36. Kristen Haugen
    Kristen Haugen
    Can we talk about the pages and chat for the team? I'm not sure my team will use chat.
  37. Theo Gallagher
    Theo Gallagher
    Most teams start with search and pages, and chat comes later once people trust the answers. We can switch on what you need and leave the rest.
  38. Kristen Haugen
    Kristen Haugen
    Fine. That's less scary to take to my director.
  39. Kristen Haugen
    Kristen Haugen
    This is helpful. I need to take it to my director.
  40. Jordan Pike
    Jordan Pike
    Let's do that. I'll send the recap today with the control reference, the admin answer and the connector list.
  41. Jenna Lindstrom
    Jenna Lindstrom
    And I'll send the connector list by Friday.
  42. Theo Gallagher
    Theo Gallagher
    Thanks, both. I'll have the control reference to you by end of day, and the admin answer in writing.
  43. Kristen Haugen
    Kristen Haugen
    Perfect. Thanks, everyone.
  44. Jordan Pike
    Jordan Pike
    Thanks, Theo. Talk soon, Kristen. Bye, Jenna.
  45. Theo Gallagher
    Theo Gallagher
    Thanks all. Bye.
  46. Jenna Lindstrom
    Jenna Lindstrom
    Bye.

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