B-Viz
Jordan Pike

Shawsheen Freight / BG-Demo – Demo

Callcompleted

Shawsheen Freight logo Shawsheen Freight · 26 Jan 2026 14:30

Shawsheen Freight saw B-Viz answer claims questions on sample data. Erin Gallant could see the fit. Jared Pelletier's single sign-on, access and retention questions are still owed in writing, and cost is deferred to the next call.

What was said

What this says

As at Fri 9 Oct 2026

Shawsheen Freight saw B-Viz answer claims questions on sample data. Erin Gallant could see the fit. Jared Pelletier's single sign-on, access and retention questions are still owed in writing, and cost is deferred to the next call.

What happened: Hannah Lowe ran a demo on a sample of Shawsheen's data. Erin said it was the first time she had seen a claim come up with the load attached.

Customer view: Erin put the current process at twenty minutes of flicking between screens, against a few seconds in B-Viz. She also doubted the sample result and wanted to check it against their own numbers.

Commercial: Erin asked when cost would be discussed. Jordan Pike deferred it to the next call, once scope is right.

Watch: Jared, who will fix things if they break, still needs written answers on single sign-on at this tier, data retention and access. Single sign-on is an Enterprise feature, so the tier needs confirming in writing.

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

Themes

As at Fri 9 Oct 2026
Theme
Demo, security questions open
Importance
upsell
Sentiment
positive
Voice
decision-maker

Who was there

BG-Demo

Them

Follow-up

Next steps

As at Fri 9 Oct 2026
  • Hannah Lowe to send the written security answers and demo notes this week.
  • Jordan Pike to send the summary and book the next call, where cost will be discussed.
  • Hannah to confirm in writing whether single sign-on is included at the proposed tier.

Risks

As at Fri 9 Oct 2026
  • Single sign-on at the prospect's tier is unconfirmed and may point to Enterprise.
  • Data retention and access answers are owed in writing before Jared can brief IT.
  • Erin distrusted the sample figures, so results on the customer's own data must hold up.

Opportunities

As at Fri 9 Oct 2026
  • Erin wants claims by reason dashboards first, then call volume by shipper.
  • Loads, claims, calls and the shipper file give a clear first connector set.

Transcript

  1. Hannah Lowe
    Hannah Lowe
    Hi all, Hannah from BG-Demo. Before I start, what's the one thing you most need to know today? I'd rather answer that first than walk you through everything.
  2. Jordan Pike
    Jordan Pike
    Hey, Jordan here. For me, honestly, it's whether this works on your data, not ours. So let's make sure we see your data.
  3. Erin Gallant
    Erin Gallant
    For me, can it stop people ringing me to find a claim.
  4. Jared Pelletier
    Jared Pelletier
    Mine's how it connects and what that means for my admin time. I'll be the one fixing things if they break.
  5. Hannah Lowe
    Hannah Lowe
    Good, that's useful. The short answer on connections is that B-Viz reads from your systems. The longer answer is that it depends which systems and how they're set up. I'll show you.
  6. Jared Pelletier
    Jared Pelletier
    Which ones do you connect first? I'd want to know that before anything else.
  7. Hannah Lowe
    Hannah Lowe
    Usually the systems people already ask for. For you that's the loads, the claims and the call recordings, but that's a conversation with Erin's team about what's in use.
  8. Erin Gallant
    Erin Gallant
    Loads, claims, calls, yes. And the shipper file, which is the messy one.
  9. Hannah Lowe
    Hannah Lowe
    Right, the messy one is where most of our time goes. Let me show you the demo environment, which has a sample of your data in it.
  10. Hannah Lowe
    Hannah Lowe
    Here you can ask a question in plain English. Let's try: what's the claim history for a shipper this month?
  11. Erin Gallant
    Erin Gallant
    Oh, that's the first time I've seen that come up with the load attached.
  12. Jordan Pike
    Jordan Pike
    That's the whole pitch in one question. Okay Erin, ask one of your own.
  13. Erin Gallant
    Erin Gallant
    Right. Which shipper had the most claims closed without a call back?
  14. Hannah Lowe
    Hannah Lowe
    Let me run that, give it a second. There, that's the list. Note it's based on the sample, so check it against your own numbers before you rely on it.
  15. Erin Gallant
    Erin Gallant
    Hmm, I'd want to check that one, the sample's not the full picture.
  16. Hannah Lowe
    Hannah Lowe
    Exactly the right instinct. I'd never want anyone trusting a sample figure in front of a customer.
  17. Jared Pelletier
    Jared Pelletier
    What about access? Who can see what? I need to know that before I say anything to IT.
  18. Hannah Lowe
    Hannah Lowe
    Good question. Access follows the permissions in your systems, so a user only sees what they already have access to. To be precise, that's how it's designed, and I'll put it in writing for your security team.
  19. Jared Pelletier
    Jared Pelletier
    And single sign-on? Do we get that at this tier?
  20. Hannah Lowe
    Hannah Lowe
    I'd rather not guess on that one. I'll confirm the exact plan detail in writing, so you're not relying on my memory.
  21. Jared Pelletier
    Jared Pelletier
    Fine. Where's the data actually held? My security questionnaire will ask.
  22. Hannah Lowe
    Hannah Lowe
    It's built and runs inside your own Snowflake account, so your data stays in your environment. I'll put that in writing with the detail. Is there anything in the questionnaire you've already answered?
  23. Jared Pelletier
    Jared Pelletier
    Some of it. Data retention is the one I can't answer yet.
  24. Hannah Lowe
    Hannah Lowe
    I'm not going to answer retention off the top of my head. I'll check with a colleague in security and come back to you in writing, so it's right first time.
  25. Jordan Pike
    Jordan Pike
    Let's park that for now. Erin, back to your claims question. How fast does this get you an answer?
  26. Erin Gallant
    Erin Gallant
    A few seconds, if the question's clear. That's the difference. Right now it's twenty minutes of flicking between screens.
  27. Hannah Lowe
    Hannah Lowe
    Sorry, I'm going to show the dashboards. Let me just open that view.
  28. Hannah Lowe
    Hannah Lowe
    Right. Dashboards are how a team keeps an eye on things. Erin, you mentioned calls. Would you want a dashboard of call volume by shipper?
  29. Erin Gallant
    Erin Gallant
    Yes, but I'd rather see claims by reason first. Then calls.
  30. Hannah Lowe
    Hannah Lowe
    Good. We'd build that together, and I'd want your team in the room, because they know the reasons better than the data does.
  31. Jared Pelletier
    Jared Pelletier
    Is building dashboards something my team does, or does your side do it?
  32. Hannah Lowe
    Hannah Lowe
    Both. Once it's set up you can build them yourselves, and we help with the first few so they're right.
  33. Jordan Pike
    Jordan Pike
    Sorry, I dropped off for a second. Where are we?
  34. Hannah Lowe
    Hannah Lowe
    We've done the claims question and the access question. Still to do are the security questions, which I'll answer in writing.
  35. Erin Gallant
    Erin Gallant
    And the cost, when do we talk about that?
  36. Jordan Pike
    Jordan Pike
    Next call, once we've got the scope right. I'd rather have the right number than a fast one.
  37. Jared Pelletier
    Jared Pelletier
    Agreed. I'd like the written answers before the next call, if possible.
  38. Hannah Lowe
    Hannah Lowe
    I'll get them to you this week. I'll send the demo notes with the questions too, so you've got it all in one place.
  39. Erin Gallant
    Erin Gallant
    Thanks, this has been really useful. I think we can see how it'd fit.
  40. Jordan Pike
    Jordan Pike
    That's what I wanted to hear. Next step: Hannah sends the written answers, I send the summary, and we book the next call.
  41. Hannah Lowe
    Hannah Lowe
    Sounds good. I'll put that in writing. Thanks all.
  42. Jared Pelletier
    Jared Pelletier
    Thanks, bye.
  43. Erin Gallant
    Erin Gallant
    Bye, thanks both.
  44. Jordan Pike
    Jordan Pike
    Bye all, speak soon.

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