B-Glass
Hamza Akhtar

Kronfeld Assekuranz / BG-Demo – Onboarding

Callcompleted

Kronfeld Assekuranz logo Kronfeld Assekuranz · 21 May 2026 10:30

Onboarding call on 21 May 2026 for Kronfeld Assekuranz's Growth implementation. Stefanie Lange and Philipp Schulz want broker data in one place. The plan stages four connectors, with end of June called tight.

What was said

What this says

As at Fri 9 Oct 2026

Onboarding call on 21 May 2026 for Kronfeld Assekuranz's Growth implementation. Stefanie Lange and Philipp Schulz want broker data in one place. The plan stages four connectors, with end of June called tight.

What happened: Hamza Akhtar set out an eight-week plan for four connectors: Salesforce, the call recorder, Microsoft 365 email and the claims system. Salesforce and the call recorder go first, email and claims later.

Customer view: Stefanie described fragmented broker data across Salesforce, a separate call system, email and claims ticketing. Philipp said the brain would transform how they work.

Commercial: Four first adopters are planned, against 40 users on Growth, so there is a lot of headroom to fill. A QBR is planned for September under the Growth tier.

Watch: Stefanie called end of June tight, and Hamza's recap put Salesforce live in the first week of July. Credentials depend on Philipp turning them round in a day or two.

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

Themes

As at Fri 9 Oct 2026
Theme
Growth onboarding connector plan
Importance
neutral
Sentiment
positive
Voice
champion

Who was there

BG-Demo

Them

Follow-up

Next steps

As at Fri 9 Oct 2026
  • Hamza Akhtar sends the Salesforce spec by Friday of that week.
  • Philipp Schulz sends a one-pager on each system and then the API credentials.
  • Hamza Akhtar runs the training in mid-July and the QBR follows in September.

Risks

As at Fri 9 Oct 2026
  • Stefanie called the end of June target for Salesforce and the call recorder tight.
  • Go-live depends on Philipp supplying API credentials within a day or two of the spec.

Opportunities

As at Fri 9 Oct 2026
  • Only four first adopters against 40 users leaves room to widen use across broker management and claims.

Transcript

  1. Hamza Akhtar
    Hamza Akhtar
    Hi Stefanie, hi Philipp, thanks for joining. I'm Hamza Akhtar, I'll be your implementation lead. How is everyone doing today?
  2. Stefanie Lange
    Stefanie Lange
    Hi Hamza, we're good thanks. Looking forward to getting started.
  3. Philipp Schulz
    Philipp Schulz
    Hi Hamza, good to meet you. Yes, ready to go.
  4. Hamza Akhtar
    Hamza Akhtar
    Brilliant. So I want to walk through the plan for the next 8 weeks. You've signed up for Growth with 40 users and four connectors, and I want to make sure we're aligned on what we're building, the timeline, and who does what. Stefanie, from my notes, the main thing your broker management and claims teams need is to see everything about each broker in one place: their submissions, calls, complaints, tickets, instead of jumping between systems. Is that still the big pain point?
  5. Stefanie Lange
    Stefanie Lange
    Yeah, exactly. Right now the submissions are in Salesforce, the calls are in a completely different system, then there's email scattered everywhere, and claims has its own ticketing system. It's really fragmented. If I want to know what's happened with a broker, I'm spending way too much time stitching things together.
  6. Philipp Schulz
    Philipp Schulz
    And the calls especially are a pain to access. The transcripts aren't linked to anything, so you've got to remember dates and names and hunt for them. If we could ask the brain a question and get the full picture, it would transform how we work.
  7. Hamza Akhtar
    Hamza Akhtar
    That's exactly what we're building. Now, the four connectors you've listed, I'm assuming Salesforce for the CRM, the call recorder, Microsoft 365 for email, and your claims system. Is that right?
  8. Philipp Schulz
    Philipp Schulz
    Yes, those four. We've got them all with APIs available, so the connectors should be straightforward to set up.
  9. Hamza Akhtar
    Hamza Akhtar
    Good. My plan is to stage these rather than flip them all live at once. I'd like Salesforce and the call recorder live by the end of June. Those two are your highest value. Then email and claims in July. Does that timeline work for you both?
  10. Stefanie Lange
    Stefanie Lange
    End of June is tight but yeah, we can aim for that.
  11. Hamza Akhtar
    Hamza Akhtar
    Right. Philipp, what I'll need from you is API credentials and read access to the key objects in Salesforce: accounts, opportunities, tasks, that kind of thing. I can send you a detailed spec by Friday of this week. How quickly can you get those set up once you have the spec?
  12. Philipp Schulz
    Philipp Schulz
    I can probably turn that around in a day or two. So if you send Friday, I'd say Wednesday or Thursday next week you'd have the credentials.
  13. Hamza Akhtar
    Hamza Akhtar
    Perfect, that's the pace I need. Same thing for the call recorder, I'll need API credentials and access to the recordings and transcripts. And for email, if you're on Microsoft 365, that's usually straightforward. Then the claims system, I'll need to understand their API setup. Philipp, can you send me a quick one-pager on each system by end of this week? Just high level: what it is, the API availability, and who owns it.
  14. Philipp Schulz
    Philipp Schulz
    Yeah, I can do that.
  15. Hamza Akhtar
    Hamza Akhtar
    Excellent. Now, on the user side, Stefanie, once the connectors are live, your team needs to start using the brain. Who are your first adopters going to be? I always recommend starting with your most frustrated users, the ones who are most keen to get data back quickly.
  16. Stefanie Lange
    Stefanie Lange
    I'm thinking three or four people in broker management who are really keen, and maybe one person from claims who's very analytical. So four to start.
  17. Hamza Akhtar
    Hamza Akhtar
    Perfect. That's a good size. Once they're using it, they'll ask questions and that'll pull in more of the team. I'd also like to do a structured training session once things are stable: probably mid-July, once Salesforce and the call recorder have been live for a few weeks and we've ironed out any wrinkles. We can walk the team through how to ask questions, what kind of answers to expect, how to interpret the results.
  18. Stefanie Lange
    Stefanie Lange
    How long does that take, usually?
  19. Hamza Akhtar
    Hamza Akhtar
    Two or three hours depending on how much detail people want. Are you all in Düsseldorf, or spread out?
  20. Stefanie Lange
    Stefanie Lange
    Everyone's in the office here.
  21. Hamza Akhtar
    Hamza Akhtar
    Great. We can probably do it in person, or virtual if you prefer. We'll sort that out once we're closer. One more thing, you're on Growth, which means we do quarterly business reviews. So come September, we'll sit down and review how you're using it, what questions you're asking, whether the team has found what they need. But that's a few months away, so let's not worry about it now. Any questions so far?
  22. Philipp Schulz
    Philipp Schulz
    What happens if there's a blocker during implementation? Who do I reach out to?
  23. Hamza Akhtar
    Hamza Akhtar
    Good question. During implementation, I'm your dedicated person. You can email me any time at hamza.akhtar@bg-demo.example, and I aim to get back to you within a business day. If it's urgent, there's also a support channel you can use. But for the next couple of months, I'm basically on your project.
  24. Philipp Schulz
    Philipp Schulz
    That's good to know.
  25. Hamza Akhtar
    Hamza Akhtar
    Right, so let me recap the timeline. This week, I send you the Salesforce spec and you send me a one-pager on the other systems. Next week, you send credentials. First week of July, I go live with Salesforce. Second week of July, call recorder goes live. Mid-July, we do the training. End of July, we flip on email and claims. By end of August, all four connectors are live and your team is trained. Then we move into business-as-usual, with a QBR coming up in September. Does that work?
  26. Stefanie Lange
    Stefanie Lange
    Yeah, that sounds solid.
  27. Philipp Schulz
    Philipp Schulz
    Yep, we can work to that.
  28. Hamza Akhtar
    Hamza Akhtar
    Brilliant. Anything else you want to cover today?
  29. Stefanie Lange
    Stefanie Lange
    No, I think we're good.
  30. Hamza Akhtar
    Hamza Akhtar
    Great. I'll get that spec out to you by Friday and we'll take it from there. Thanks both, speak soon.
  31. Stefanie Lange
    Stefanie Lange
    Thanks Hamza.
  32. Philipp Schulz
    Philipp Schulz
    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