B-Glass
Tobias Renwick

Tannahill Systems / BG-Demo – Training

Callcompleted

Tannahill Systems logo Tannahill Systems · 30 May 2023 14:15

Tobias Renwick trained Kenny Lockhart and Scott Galbraith on search, dashboards and chat for 15 licensed users. Kenny called the manual work it replaces a game-changer. No commercial discussion.

What was said

What this says

As at Fri 9 Oct 2026

Tobias Renwick trained Kenny Lockhart and Scott Galbraith on search, dashboards and chat for 15 licensed users. Kenny called the manual work it replaces a game-changer. No commercial discussion.

What happened: Tobias walked Kenny and Scott through search, dashboards and chat for the support team's 15 licensed users. He covered nightly refresh, Snowflake ownership and the helpdesk connector.

Customer view: Kenny wants the team finding similar tickets and spotting trends. He said "This is what we've been doing by hand."

Watch: Tobias warned that if the connector stops, the data goes stale and answers become less useful. He suggested checking it weekly in the early days and measuring a task before and after.

Commercial: No price, renewal or rival was raised. The call sets up adoption, which later feeds the value case for the renewal.

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

Themes

As at Fri 9 Oct 2026
Theme
Onboarding training for support
Importance
praise
Sentiment
positive
Voice
champion

Who was there

BG-Demo

Them

Follow-up

Next steps

As at Fri 9 Oct 2026
  • Tobias Renwick to send Kenny Lockhart a login link and the follow-up details after the call.
  • Kenny Lockhart's team to measure a specific task now and repeat it in a few weeks to show the difference.

Risks

As at Fri 9 Oct 2026
  • If the helpdesk connector stops loading, the data goes stale and the team loses trust in the answers.
  • Only one person is suggested to learn the brain first, which could leave adoption resting on one user.

Opportunities

As at Fri 9 Oct 2026
  • Dashboards are a clear next use for ticket volume and resolution times, which would show investment by the customer.

Transcript

  1. Tobias Renwick
    Tobias Renwick
    Hi Kenny, Scott, can you both hear me?
  2. Kenny Lockhart
    Kenny Lockhart
    Yes, loud and clear.
  3. Scott Galbraith
    Scott Galbraith
    Good here.
  4. Tobias Renwick
    Tobias Renwick
    Right, so today we're walking through how to use the brain for your support team. You've got 15 users licensed, and the goal is to get them comfortable with search and dashboards over the next couple of weeks. Sound good?
  5. Kenny Lockhart
    Kenny Lockhart
    Perfect. We want to get the team using it for finding similar tickets and spotting trends.
  6. Tobias Renwick
    Tobias Renwick
    Good. Let me share my screen. So the brain has three main ways to interact: search, dashboards, and chat. Most teams start with search. You type a natural question..."show me unresolved tickets from this week", and the brain works out what fields it needs and brings back results.
  7. Scott Galbraith
    Scott Galbraith
    Can we search all our historical data?
  8. Tobias Renwick
    Tobias Renwick
    Yes. Everything from when you connected your helpdesk integration is indexed and searchable. You can find patterns, which agent handled certain issues, whatever you need.
  9. Scott Galbraith
    Scott Galbraith
    How often does the data refresh?
  10. Tobias Renwick
    Tobias Renwick
    Nightly. So by tomorrow morning, everything from today will be in there. There's a slight lag: you won't see today's tickets until tomorrow: but after that, it's all current and searchable in seconds.
  11. Kenny Lockhart
    Kenny Lockhart
    This is what we've been doing by hand. That's a game-changer. What about dashboards?
  12. Tobias Renwick
    Tobias Renwick
    Dashboards let you build visual reports without code. Pick a metric, set a time range, add filters if you want. The brain builds the chart. Your team might want ticket volume by week, or resolution times by agent.
  13. Scott Galbraith
    Scott Galbraith
    How many can we build?
  14. Tobias Renwick
    Tobias Renwick
    As many as you need. Twenty or thirty is typical, but there's no hard limit.
  15. Kenny Lockhart
    Kenny Lockhart
    And this all lives in our Snowflake account? We own the data?
  16. Tobias Renwick
    Tobias Renwick
    Completely. The brain runs inside your Snowflake account. We have no access to the data. If you cancel, the brain stops, but your data stays.
  17. Scott Galbraith
    Scott Galbraith
    How does the connector to our helpdesk work?
  18. Tobias Renwick
    Tobias Renwick
    We set up an API or connector that pulls data on a schedule and loads it to your Snowflake. Your credentials stay on your side, we never see them. That's the design.
  19. Kenny Lockhart
    Kenny Lockhart
    When can we start?
  20. Tobias Renwick
    Tobias Renwick
    You're ready now. I'll send you a login link after this call. I'd suggest one person from your team gets familiar first, then walks the rest through it.
  21. Scott Galbraith
    Scott Galbraith
    If we have a question or something goes wrong?
  22. Tobias Renwick
    Tobias Renwick
    Log it with our support team. They'll get back to you with a standard response time. There's also documentation and a help guide for common questions.
  23. Kenny Lockhart
    Kenny Lockhart
    One more thing, how do we know if it's actually working?
  24. Tobias Renwick
    Tobias Renwick
    Best way is to pick a specific task, like "how long does it take to find a similar ticket?", measure it now, then try it again in a few weeks with the brain. The difference is usually clear. Keep notes and we can talk about it at your next check-in.
  25. Scott Galbraith
    Scott Galbraith
    Anything we should watch out for?
  26. Tobias Renwick
    Tobias Renwick
    Make sure the connector keeps running and pulling fresh data. If it stops, the data goes stale and answers become less useful. Check on it weekly in the early days. Your admin can see the status in settings.
  27. Kenny Lockhart
    Kenny Lockhart
    That's really helpful. I think we're ready. Thanks, Tobias.
  28. Tobias Renwick
    Tobias Renwick
    You're welcome. I'll send those details now. Reach out if the team has questions, and we'll check in in a few weeks. Best, Tobias.
  29. Scott Galbraith
    Scott Galbraith
    Cheers.

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

Help & Support

Open as a page

Help & Support

B-Glass 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
Organisations225
People at customers862
BG-Demo staff records (in post and leavers)58
Calls1,995
Email threads3,013
Support tickets1,159
Documents1,218
Deals315
Invoices285
Events49
News items119

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

Who to contact

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

Help

Ask B

B-Glass · read-only