B-Viz
Callie Brennan

Strensall Merchants / BG-Demo – Onboarding

Callcompleted

Strensall Merchants logo Strensall Merchants · 26 Mar 2025 11:00

Neil Craven and Ashok Patel agreed how to link trade accounts across branches, with a York test branch first. The delivery connector awaits the supplier. Neil's success test is one builder seeing the same total from any branch.

What was said

What this says

As at Fri 9 Oct 2026

Neil Craven and Ashok Patel agreed how to link trade accounts across branches, with a York test branch first. The delivery connector awaits the supplier. Neil's success test is one builder seeing the same total from any branch.

What happened: Callie Brennan led an onboarding session on connectors and account mapping. Branch system credentials are in and verified, the credit system will be read from its existing nightly file, and the delivery system awaits the supplier's approval.

Customer view: Neil wants one builder to see the same orders and total whichever branch answers. He also said he does not want the rollout dragging.

Commercial: This is an Enterprise customer, licensed for 160 users with only a handful active. Ashok asked about freshness cover, and Callie promised the exact order form wording via Daniel, the customer success manager.

Watch: The delivery connector carries a live-by commitment in the order form. Ashok is the only admin, and the credit file's dependants are unknown.

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

Themes

As at Fri 9 Oct 2026
Theme
Trade account mapping onboarding
Importance
neutral
Sentiment
mixed
Voice
decision-maker

Who was there

BG-Demo

Them

Follow-up

Next steps

As at Fri 9 Oct 2026
  • Ashok sends the pairs export with the query screenshot and chases the delivery supplier by Thursday.
  • Callie confirms connector access in writing, runs the test load early next week and sends the setup note.
  • Callie asks Lewis Kerr to confirm no security review items are open, and Daniel to point Ashok at the freshness wording.

Risks

As at Fri 9 Oct 2026
  • The delivery connector is waiting on the supplier, and the order form has live-by commitments for connectors.
  • Ashok is the only admin, and the credit file's dependants are unknown.
  • Neil is worried that slow progress on agreeing customer accounts will drag.

Opportunities

As at Fri 9 Oct 2026
  • Phasing users from the 160 licensed seats by group, credit first, builds adoption on the Enterprise plan.
  • Call and mailbox connectors follow the trade data, adding depth later.

Transcript

  1. Callie Brennan
    Callie Brennan
    Hello, can you hear me alright? I can see Ashok, and Neil, I think you've just joined.
  2. Neil Craven
    Neil Craven
    Aye, I'm here. Morning, Callie. Sorry, I'm a minute behind. I had a builder on the phone first thing, one of our big housebuilder accounts.
  3. Ashok Patel
    Ashok Patel
    Morning. Yes, I can hear you both fine.
  4. Callie Brennan
    Callie Brennan
    Lovely. Right, so here's the plan for the next hour, and I'll try to give you a few minutes back. First, where we are on the connectors. Second, the trade account mapping, which I know is the bit you both care about most. Third, what happens at the first refresh. And then who does what after today, and I'll write all of that into a setup note so nothing lives only in my head. Does that sound alright?
  5. Neil Craven
    Neil Craven
    Sounds grand. And that builder, actually, that's why I care about the mapping. He rang this morning because the same order showed a different total depending on which branch he'd spoken to.
  6. Callie Brennan
    Callie Brennan
    Ah. Okay, so which branch, which account, do you know?
  7. Neil Craven
    Neil Craven
    That's my line, that is. Not yet. I've asked the branch to send me the account details. But what's the builder actually seeing? He's seeing two numbers for one order. That's what I want gone.
  8. Ashok Patel
    Ashok Patel
    Can I say what I've changed since last time? It might save us a few questions.
  9. Callie Brennan
    Callie Brennan
    Please, yes.
  10. Ashok Patel
    Ashok Patel
    So, I've set up the service user in our Snowflake account, the one you described, with the role limited to the B-Viz schema. I've put the read-only credentials for the branch system into the shared vault, and I've sent you the link in writing. The delivery system I've requested but it isn't through yet. The credit system I haven't started, because I wanted to talk about that one with you first.
  11. Callie Brennan
    Callie Brennan
    That's really helpful, thank you. And that's exactly what I need from your side: written access for each source before I touch it. I never start a connector on a verbal yes. So the branch system, I've got the link, I'll confirm in a moment that it opens for me.
  12. Ashok Patel
    Ashok Patel
    Fine. I'll test it on one branch first, though, if that's alright. Before we point it at all of them.
  13. Callie Brennan
    Callie Brennan
    Yes, that's what I'd suggest anyway. Pick the branch you trust the most. Not the tidiest, necessarily, but one where you know the data well enough to say whether it's right.
  14. Ashok Patel
    Ashok Patel
    Then it'll be one of the York ones. I know the ledger there. I can compare the loaded accounts against the ledger by hand.
  15. Neil Craven
    Neil Craven
    Good. York's fine. Don't pick one of the ones that's mid-changeover, mind, we've got a couple that are still moving tills.
  16. Ashok Patel
    Ashok Patel
    No, I'd avoid those. Noted.
  17. Callie Brennan
    Callie Brennan
    Right. Let me share my screen so you can see the connector list. Can you see that? It's the one with the status column.
  18. Ashok Patel
    Ashok Patel
    Yes. I can see it. Branch system is amber, the rest are grey.
  19. Callie Brennan
    Callie Brennan
    That's right. Amber means credentials are in but nothing's loading yet. Grey means we haven't got access. So, we've got the branch system, the delivery system, the credit system, then the call recorder and the mailboxes. Those last two I'd leave until the trade data is behaving. There's no point layering calls on top of accounts that don't line up.
  20. Neil Craven
    Neil Craven
    Hang on, though. The calls are the bit my key account people are keen on. They want to ask what was said to a builder last time he rang.
  21. Callie Brennan
    Callie Brennan
    Completely, and they'll get it. I'm only saying the order. If the call recorder says one name and the ledger says another, the question comes back muddled. Get the account right first, then the calls slot in.
  22. Neil Craven
    Neil Craven
    Right, aye. That makes sense. Let's sort it, not talk about it. Go on.
  23. Callie Brennan
    Callie Brennan
    So, the mapping. Ashok, what I'd like to understand is how a single trade customer is identified across the branches. Is there one account number, or does each branch have its own?
  24. Ashok Patel
    Ashok Patel
    Which account number is that, is the honest answer. There's the main trade account number, which should be the same everywhere. But historically some branches opened their own account for the same builder, so you've got the group number and then a branch number sitting alongside it. Credit uses the group one. Delivery mostly uses the branch one.
  25. Neil Craven
    Neil Craven
    That'll be it, then. That'll be my builder. Credit thinks he's one customer and the branch thinks he's two.
  26. Ashok Patel
    Ashok Patel
    Possibly. I'd want to look before I say so. The data says otherwise sometimes. I've seen cases where it looks like a duplicate and it's actually two legal entities with the same trading name.
  27. Callie Brennan
    Callie Brennan
    Good, and that's why I won't merge anything on a name match. What I'd propose is that we hold both numbers on the account record, group number as the key, branch number as a linked reference. Then nothing is lost, and if a pair turns out to be separate companies, you can split them again.
  28. Ashok Patel
    Ashok Patel
    I like that. I never delete what I can't restore. If it's a link rather than a merge, I'm comfortable.
  29. Callie Brennan
    Callie Brennan
    That maps cleanly, then. What I need from you is an export of the group to branch number pairs for the test branch. Just the pairs, nothing sensitive. Can you manage that by end of tomorrow?
  30. Ashok Patel
    Ashok Patel
    Thursday, yes. I can do that. Probably as a spreadsheet, with a screenshot of the query so you can see how I pulled it.
  31. Callie Brennan
    Callie Brennan
    Perfect, the screenshot is exactly right.
  32. Neil Craven
    Neil Craven
    Can I ask something a bit daft? When we say the branches see the same account, does that mean a counter lad in a small branch sees the credit position too?
  33. Callie Brennan
    Callie Brennan
    Not daft at all. It depends on how you set permissions, and that's your call, with Ashok as admin. B-Viz runs inside your own Snowflake account, so access follows the roles you give people. We can make credit visible only to the credit team and key accounts, and branch staff see orders and deliveries only. Or whatever mix you want.
  34. Neil Craven
    Neil Craven
    I'd start narrow. Credit people see credit. Branch managers see a flag, like on hold or not, and then they ring credit. I don't want a counter lad telling a builder his limit.
  35. Ashok Patel
    Ashok Patel
    A flag is easy. I'd rather do that as a separate role so I can show you what a branch manager actually sees before anyone gets it.
  36. Callie Brennan
    Callie Brennan
    Agreed. I'll put it in the setup note as a decision for you two, not something I've assumed.
  37. Callie Brennan
    Callie Brennan
    Okay, let me just check I can open the branch system link. Bear with me.
  38. Neil Craven
    Neil Craven
    Take your time. Ashok, is that the link you sent, or the old one?
  39. Ashok Patel
    Ashok Patel
    The new one, from yesterday. The old one expires.
  40. Callie Brennan
    Callie Brennan
    Got it, it opens. And the schema is empty, as it should be. Good. So before we switch on the refresh, a couple of things. The nightly refresh is meant to complete by 07:00 your time on business days. For the first week, though, I'd run it by hand on the test branch and look at it together, rather than leave it to run overnight.
  41. Ashok Patel
    Ashok Patel
    Yes. I'd rather watch the first load. If it fails at three in the morning, nobody sees it.
  42. Neil Craven
    Neil Craven
    And what's the first load going to show us? Rough idea. Is it going to be a mess?
  43. Callie Brennan
    Callie Brennan
    Honestly, a bit untidy, usually. First loads always throw up things nobody knew about: blank fields, old accounts nobody closed, dates in odd formats. It's not a failure, it's the point. We list them, Ashok decides what's real and what's clutter, and we run it again. By the second load it's normally a lot cleaner.
  44. Neil Craven
    Neil Craven
    Right. I'd rather know about the clutter now than have a builder find it.
  45. Ashok Patel
    Ashok Patel
    There will be clutter. We have accounts from before I joined. I won't overstate it, though. I'll know once I see the counts.
  46. Callie Brennan
    Callie Brennan
    Which brings me to users. You're licensed for 160, and at the moment I can see only a handful active in the workspace, just the people we've set up so far.
  47. Neil Craven
    Neil Craven
    That'll be me, Ashok, a couple from credit and a couple of the key account managers. We're not rolling it to the branches until it's right.
  48. Callie Brennan
    Callie Brennan
    Sensible. I'd keep it that way until the test branch is checked. When you do widen it, do it by group, so credit first, then key accounts, then branch managers, rather than everyone in one go.
  49. Neil Craven
    Neil Craven
    Aye. Phased. I'll talk to the area managers about which branches go first. I'd want the ones with the biggest builder accounts, because that's where it bites.
  50. Ashok Patel
    Ashok Patel
    I'd say the opposite for a pilot. Start with a quiet one, so if something's wrong it's not a big account that sees it.
  51. Neil Craven
    Neil Craven
    Hmm. Fair. Quiet one for testing, big ones for the rollout. We'll agree that.
  52. Callie Brennan
    Callie Brennan
    That's a good split, actually. I'll note both.
  53. Callie Brennan
    Callie Brennan
    Now the credit system. Ashok, you said you wanted to talk about that one.
  54. Ashok Patel
    Ashok Patel
    Yes. It's the oldest of the three and the export is, well, awkward. It produces a nightly file, but the person who set it up has moved on to another role and I'm not sure what else depends on it. I don't want to change how it runs and break something in credit control.
  55. Callie Brennan
    Callie Brennan
    Understood. Then we don't touch how it runs. We read the file it already produces, read-only, and we never write back. Can you find out who in credit control relies on that file and what time it lands?
  56. Ashok Patel
    Ashok Patel
    I can. I'll ask the credit team this afternoon. They'll know when it arrives.
  57. Neil Craven
    Neil Craven
    I'll have a word with the head of credit as well. She'll want to know before we point anything at her system anyway.
  58. Callie Brennan
    Callie Brennan
    Thank you, Neil, that helps. If the file lands late, the refresh will be reading yesterday's credit position, and I'd rather we knew that than found out later.
  59. Ashok Patel
    Ashok Patel
    Which is the freshness point. For Enterprise, that's covered in the contract, isn't it? The data being ready by the morning.
  60. Callie Brennan
    Callie Brennan
    The service levels are in your order form, and for Enterprise freshness is part of them. I'd rather not paraphrase the detail from memory, so I'll ask Daniel to point you at the exact wording. He's your customer success manager, he'll be your main contact once we're live.
  61. Neil Craven
    Neil Craven
    Daniel, right. And Lewis is the one who sold us it?
  62. Callie Brennan
    Callie Brennan
    Lewis Kerr, yes, he owns the account on our side and the commercial terms. Daniel looks after adoption and the check-ins. I do the setup, and then I hand over.
  63. Neil Craven
    Neil Craven
    Fine by me. I like knowing who to ring.
  64. Callie Brennan
    Callie Brennan
    Good. Okay, let's use the time on the test branch. Ashok, can you share your screen and show me the account table you're thinking of using?
  65. Ashok Patel
    Ashok Patel
    Give me a second. I need to find the right window. Is that visible?
  66. Callie Brennan
    Callie Brennan
    Yes, I can see a query result. Lots of columns.
  67. Ashok Patel
    Ashok Patel
    That's the York test set. Group number, branch number, trading name, legal name, status. You can see these three rows, same trading name, different branch numbers, same group number. That's the pattern I mean.
  68. Callie Brennan
    Callie Brennan
    Right, and that one's clean. Same legal name too. That would link without any argument. What about the fourth one down? Same trading name, different group number?
  69. Ashok Patel
    Ashok Patel
    That's the one I'd leave alone. Different legal name. I think it's a sister company of the first. I'm not certain.
  70. Neil Craven
    Neil Craven
    It is. Two firms, one family. They share a site foreman and they'll ring us as if they're the same, but they've got separate credit limits. Don't merge those.
  71. Callie Brennan
    Callie Brennan
    Then it stays separate, and that's exactly why I wanted links rather than merges. Neil, would it be useful to mark those as related in the record? Related, not the same.
  72. Neil Craven
    Neil Craven
    That'd be perfect. Related accounts. Key accounts would use that all day.
  73. Ashok Patel
    Ashok Patel
    I can add a column for it. I'd rather add it on our side, in the source, than have B-Viz guess. Otherwise it's a guess.
  74. Callie Brennan
    Callie Brennan
    Yes, please do. We map what you give us. I'd much rather it's your judgement than my inference. That's the cleanest way.
  75. Ashok Patel
    Ashok Patel
    It might take me a few days to populate it for the test branch. I'm not going to rush it.
  76. Callie Brennan
    Callie Brennan
    No rush from me. Let's say we plan the first test load for early next week, and if the related column isn't done we load without it and add it after.
  77. Neil Craven
    Neil Craven
    Good. I don't want us waiting on a perfect spreadsheet.
  78. Ashok Patel
    Ashok Patel
    I'd rather it was right than quick, but I take the point. Without it for the first load is fine.
  79. Callie Brennan
    Callie Brennan
    Okay. Now the delivery system. Ashok, you said the request isn't through yet. Who's holding it?
  80. Ashok Patel
    Ashok Patel
    It's with the supplier of the system. They have to approve any external read access. I've chased once.
  81. Callie Brennan
    Callie Brennan
    Chase again, if you don't mind, and copy me so I can see the reply. If it takes more than a couple of weeks, tell Daniel and Lewis, because the order form has commitments on when connectors are live and I'd like us to be ahead of that, not scrambling.
  82. Neil Craven
    Neil Craven
    I'll ring them as well if it helps. Sometimes a call from the business side shifts things.
  83. Ashok Patel
    Ashok Patel
    It might. I'll tell you if I need it.
  84. Callie Brennan
    Callie Brennan
    Brilliant. So, to recap what I've got so far, and tell me if I've got anything wrong. One: branch system credentials are in and verified, test branch is a York one, not mid-changeover. Two: group number is the key, branch numbers are linked references, nothing merged on a name match. Three: related accounts stay separate but get flagged, added by Ashok in the source. Four: credit system is read-only from the existing nightly file, and you're both finding out who relies on it. Five: delivery system is waiting on the supplier.
  85. Ashok Patel
    Ashok Patel
    That's right. One addition. I want to keep a note of which accounts I've touched in the source, so I can undo it.
  86. Callie Brennan
    Callie Brennan
    Add it to the list. I'll put it in the note as your standing rule.
  87. Neil Craven
    Neil Craven
    Can I come back to the morning's builder? Because I want to be sure this fixes it, and not just the test branch.
  88. Callie Brennan
    Callie Brennan
    Go on.
  89. Neil Craven
    Neil Craven
    He's got orders going through about four of our branches. If what you're saying is right, in the end he's one group account with a few branch numbers. When he rings, whoever picks up should see all his orders in one place and the same total. That's the test I'd set. Not a nice dashboard. A builder ringing and the answer matching.
  90. Callie Brennan
    Callie Brennan
    I like that as the test. Can we write it down as the success measure for the first phase? One real builder, several branches, same orders, same total, whichever branch answers.
  91. Neil Craven
    Neil Craven
    Aye. Write that down. And I'll give you the account when the branch sends me the details.
  92. Ashok Patel
    Ashok Patel
    I'd add a condition. It only works if the branch numbers are all in the load. If one of the four is in a branch we haven't connected, it won't match, and that's not B-Viz being wrong.
  93. Callie Brennan
    Callie Brennan
    Good point, and I'd rather we said that now than argued about it later. So the measure is for builders whose branches are all in the loaded set. I'll word it that way.
  94. Neil Craven
    Neil Craven
    Fair enough. Then we roll the branches in so that his four are covered early. That settles which ones go first, doesn't it?
  95. Ashok Patel
    Ashok Patel
    Test on York, then add his branches one by one. Same method each time.
  96. Callie Brennan
    Callie Brennan
    That works. Now, tickets. I can see you've raised two with us in the last month. One was a login question and one was about the connector wording?
  97. Ashok Patel
    Ashok Patel
    Yes. The first was my own mistake with the single sign-on setup. The second was me not being sure what read-only meant for the credit file. Both answered.
  98. Callie Brennan
    Callie Brennan
    Good, and nothing urgent. That's what I'd hope to see at this stage. If anything stops loading, raise it as urgent and say it's a connector, and it goes to the right people quickly.
  99. Neil Craven
    Neil Craven
    What counts as urgent? Because I know what I'd call urgent and it's not the same as a data person's.
  100. Callie Brennan
    Callie Brennan
    Fair. Urgent is: the whole thing is down, or data that was right is now wrong and people are acting on it. Not: a column is in the wrong order. Ashok will know the difference, and if you're ever unsure, ask Daniel.
  101. Ashok Patel
    Ashok Patel
    I'll triage it. Neil, send them to me first, and I'll decide whether it goes up.
  102. Neil Craven
    Neil Craven
    Fine. I'll pass it on. Don't want ten people raising the same thing.
  103. Callie Brennan
    Callie Brennan
    That's sensible. One admin as the front door. Though, and I say this kindly, I'd like a second named admin, so it doesn't all rest on you if you're off.
  104. Ashok Patel
    Ashok Patel
    Yes, I've thought about that. There's a colleague in my team who'd be suitable. I'd want to train them properly first, not just hand over a login.
  105. Callie Brennan
    Callie Brennan
    Agreed. I can do a short session with both of you after the first load, when there's something real to look at. It's much easier to teach on live data.
  106. Ashok Patel
    Ashok Patel
    Good. That works for me.
  107. Neil Craven
    Neil Craven
    Can I ask about the mailboxes and calls, just so I can tell my people when? Not today, but roughly.
  108. Callie Brennan
    Callie Brennan
    Roughly, after the trade data has had a couple of clean refreshes. I don't want to promise a date on those until I've seen the first load, so I'd say in the weeks after, and I'll give you a proper date in the note once the test branch is checked.
  109. Neil Craven
    Neil Craven
    That's honest enough. I'd rather have no date than a made-up one.
  110. Callie Brennan
    Callie Brennan
    Same here. I won't say should be fine about something I haven't checked.
  111. Ashok Patel
    Ashok Patel
    One question on the call recorder, actually. Do the recordings leave our systems? Our legal people will ask.
  112. Callie Brennan
    Callie Brennan
    Because B-Viz is built and run inside your own Snowflake account, the data stays in your account. I'll give you a short written description of that for your legal team, rather than have you rely on me saying it on a call.
  113. Ashok Patel
    Ashok Patel
    That would help. Thank you.
  114. Neil Craven
    Neil Craven
    While we're here, the security review. Has that all been done? I seem to remember a lot of forms.
  115. Callie Brennan
    Callie Brennan
    Mostly done before you signed, as part of the Enterprise onboarding. If anything's outstanding, Lewis would hold it, so I'll ask him to confirm there's nothing open and tell you both.
  116. Neil Craven
    Neil Craven
    Right. Thanks.
  117. Callie Brennan
    Callie Brennan
    Okay. Let me pull up the setup note and tell you what's going in it, while you tell me what's missing. I'll go through it in the order we spoke.
  118. Callie Brennan
    Callie Brennan
    So, the note says. Connectors: branch live on test branch next week, delivery waiting on supplier, credit read-only from the nightly file, call recorder and mailboxes later. Mapping: group number as key, branch numbers linked, related accounts flagged in source by Ashok. Access: narrow to start, credit sees credit, branch managers see a hold flag. Users: phased by group, credit first, then key accounts, then branch managers. Admins: Ashok now, a second admin trained after the first load. Success measure: one builder, several branches, same orders and total.
  119. Ashok Patel
    Ashok Patel
    Add that the refresh is run by hand for the first week, and that I'm watching the first load.
  120. Callie Brennan
    Callie Brennan
    Done. And I'll add that the success measure only applies where all of a builder's branches are loaded.
  121. Neil Craven
    Neil Craven
    Put in who's doing what by when, as well. I'm good with a list. Names against it.
  122. Callie Brennan
    Callie Brennan
    Yes, always. A date against every step. So. Ashok, by Thursday: the pairs export for the test branch with the query screenshot, and the chase to the delivery supplier. Ashok, by the end of this week too, the name of whoever relies on the credit file and when it lands. Neil, you and the head of credit: a word about the credit system before we read from it, and send me the builder's account when the branch replies. Me: confirm connector access in writing, run the test load early next week, send the note, and ask Lewis about the security review.
  123. Neil Craven
    Neil Craven
    I'll talk to her tomorrow. She's in the office. I'll tell her it's read-only.
  124. Ashok Patel
    Ashok Patel
    I'll do mine by Thursday. If the supplier doesn't reply, I'll say.
  125. Callie Brennan
    Callie Brennan
    Perfect. Is there anything you're worried about that we haven't touched?
  126. Neil Craven
    Neil Craven
    Only that it's slow. We've waited a long time for the branches and credit to agree on a customer. I don't want it dragging.
  127. Callie Brennan
    Callie Brennan
    I hear that. The first thing you'll see is next week's load. If that's good, you'll have a real answer on the builder soon after, and I'll make sure Daniel knows that's the milestone you care about.
  128. Neil Craven
    Neil Craven
    That'll do. Show me one builder with the right total and I'll stop worrying.
  129. Ashok Patel
    Ashok Patel
    My worry is only the credit file. If I find it's used by something I don't know about, I'll say straight away.
  130. Callie Brennan
    Callie Brennan
    Please do. Early bad news is much better than late. Right, I think we've got what we need. I'll send the note this afternoon, and the access confirmation before that.
  131. Neil Craven
    Neil Craven
    Cheers, Callie. Good session. Plenty to chew on.
  132. Ashok Patel
    Ashok Patel
    Thank you. Speak soon.
  133. Callie Brennan
    Callie Brennan
    Thanks both. Speak soon, 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