What was said
What this says
Current to 11 Oct 26Hamza Akhtar walked Clare Huddleston and Phil Catterall through the Enterprise dashboards builder. Clare called it pretty straightforward and asked for help building the first few dashboards. A build session is to follow.
What happened: Hamza demonstrated the dashboards builder with a partner dashboard and a service health view. The gallery has no dashboards yet.
Customer view: Clare said the builder looks pretty straightforward. Phil asked about refresh timing and filtering by ticket type or priority.
Commercial: Dashboards built show customer investment, and none exist yet. Hamza stressed that anyone on the team can build and share them, which supports wider adoption across teams.
Watch: Adoption now depends on the customer deciding what questions to answer. The follow-up build session is the point to convert interest into live dashboards.
Themes
Current to 9 Oct 26Who was there
BB-Demo
Them
Follow-up
Next steps
Current to 9 Oct 26- Hamza Akhtar to run a follow-up build session with Clare Huddleston the following week.
- Clare Huddleston to choose the three or four starting dashboards.
Risks
Current to 9 Oct 26- No dashboards exist yet, so value from the builder is not yet shown.
- The customer still needs to decide which questions the dashboards should answer.
Opportunities
Current to 9 Oct 26- Dashboards built by several teams would show investment and deepen use of the Enterprise subscription.
- Partner management and member operations could each build their own shared views.
Transcript
- Hamza Akhtar NoneRight, so today we're going to walk through the dashboards builder. You've got Enterprise, so you've got full access. The idea is you can build your own views of the data without needing to ask us. What I'll do is walk through a couple of examples and then show you the interface, and then you can have a go. Any questions before we kick off?
- Clare Huddleston NoneNo, let's do it.
- Hamza Akhtar NoneSo the first example: partner dashboard. You want to see for each of your partner schemes: number of open tickets, number of calls this month, revenue. Simple stuff. The builder lets you pick your data source, your filters and your layout. So you'd say 'show me tickets where scheme equals this partner, grouped by status'. Then you can add another card for calls, another for revenue. All updates nightly.
- Phil Catterall NoneSo if someone adds a new ticket, when does that appear on the dashboard?
- Hamza Akhtar NoneBy 07:00 the next morning, your time. The brain syncs every night. So if someone opens a ticket at 2 p.m., you'll see it tomorrow morning.
- Clare Huddleston NoneAnd can multiple people build dashboards, or is it just admins?
- Hamza Akhtar NoneAnyone on your team can build them. You've got 150 licensed users, and anyone of those can save a dashboard they want to use. It's not restricted. So if partner management wants their own view, they build it themselves.
- Phil Catterall NoneCan they see each other's dashboards?
- Hamza Akhtar NoneYes. Anything you save becomes available to everyone unless you specifically mark it private. Most teams make them shared. So partner management makes a partner health dashboard, member operations make a member dashboard, and everyone can browse them. Makes sense?
- Clare Huddleston NoneThat makes sense.
- Hamza Akhtar NoneRight, so let me share my screen. You'll see the builder interface. Here's the dashboard gallery: you've got no dashboards yet, but once you create one, it shows up here. Click 'New Dashboard' and you get this blank canvas. You pick a name, say 'Partner Health', and then you start adding cards. Each card is one question about your data.
- Phil Catterall NoneAnd you can add as many cards as you want?
- Hamza Akhtar NonePretty much. As many as makes sense. Most teams have dashboards with five, ten cards. Too many and it gets hard to read. So you add a card, you pick your data source, say Salesforce tickets, and then you configure it. This dropdown here is your metric: count of records, sum of a value, average, that sort of thing. Then you add filters. So 'status equals open'. Then layout: bar chart, table, cards, whatever you want.
- Clare Huddleston NoneThis looks pretty straightforward actually.
- Hamza Akhtar NoneYeah, it's designed to be. The hard part isn't building the dashboard, it's knowing what questions you want to answer. So think about what would help you run the business better, and we build those views. Let me show you another example: a service health view. Say you want to see 'have we met our SLAs this month across all partner schemes?' You'd build a card that counts how many tickets were resolved within a day.
- Phil Catterall NoneCan you filter by ticket type or priority?
- Hamza Akhtar NoneAbsolutely. Any field in your Salesforce data, you can filter on. So if you want to see high-priority tickets only, you'd add that filter. The interface shows you what fields you've got available.
- Clare Huddleston NoneOK, and when we're ready, can we get you to help us build the first few?
- Hamza Akhtar NoneOf course. That's what we're here for. Why don't we schedule a follow-up next week, just you and me, and we'll build out the three or four dashboards you want to start with. Then the team can use those as templates. Sound good?
- Clare Huddleston NoneYeah, that's perfect.
- Hamza Akhtar NoneGreat. Any other questions on the builder before I hand it back to you?
- Phil Catterall NoneNo, I think that's clear. Thanks.
- Hamza Akhtar NoneCheers both. Speak soon.