
Claim intake
Basics of a claim get captured before it reaches an adjuster, so urgent or incomplete cases stand out fast.
Captures the full Schadenmeldung, answers policy and premium questions, books advisor callbacks, and writes the next step into your Maklerverwaltungsprogramm — without giving insurance advice.
Auto claim filing
Renters insurance inquiry
Five recurring moments where the agent intakes first — so adjusters and brokers see structured cases instead of half-finished voicemails.

Basics of a claim get captured before it reaches an adjuster, so urgent or incomplete cases stand out fast.

Coverage, billing, and document questions get qualified before they go to a specialist.

Renewals, missing documents, and callback requests get followed up before they pile into backlog.

Status checks and document follow-ups stop crowding the queue your sales and service teams own.

Calls reach the right specialist with context already attached, instead of starting from zero.
Enter your number — your phone rings within 30 seconds.
A clear path, visible relief at each step — and a team that quickly sees what the agent is for after a Monday-morning storm queue.
01
You choose the 1–2 call types that block the team most — Schadenmeldung, policy and premium questions, address changes, renewal callbacks.
Visible within days: where routine calls eat up advisor and Sachbearbeitung time.
02
You decide what the agent may read back from the file, what it captures into the MVP, and when it routes the call to a §34d / §34i licensed advisor.
Consistent answers, clean handoff — Versicherungsberatung stays with the licensed team.
03
The pilot runs on real routine calls. Each week the numbers show what works and where to fine-tune.
Four weeks of controlled operation — no annual contract.
What changes
Routine call share
Calls the agent fully resolves vs. those passed to an advisor or claims handler.
Right-moment handoffs
How often the AI hands off at the right moment — when a human is genuinely needed.
After-hours requests captured
Structured by category — claim, policy, premium, address, document — sorted by your rules.
Structured Schadenmeldungen vs. emails
Share of inbound claims that arrive complete from the call instead of half-written by email.
Happy to support the rollout too — from the first call type to live across branches. Book a short demo and we'll show you how it would look in your brokerage.
And anything else with an API. We connect to your systems — you don't switch.
and many more
FAQ
Calls run on GDPR-aligned infrastructure. The data flow — what is captured, where transcripts live, who can read them, how long they're kept — is documented for your DPO before the pilot starts. Your MVP stays the source of record.
assfinet (AMS), VIAS, Keasy, meinMVP, openVIVA c2, Professional works, and Smart InsurTech all connect through their existing interfaces — including BiPRO flows where you already use them. NAFI, Morgen & Morgen, Franke und Bornberg, Levelnine, and Mr-Money are reachable for tariff and condition lookups. Anything else with an API connects the same way.
No. The agent triages, qualifies, captures the Schadenmeldung, and books the broker callback. It reads back what is on file — coverage, deductible, premium status — but it does not give Versicherungsberatung. That line stays with your §34d / §34i licensed advisors. It's the same hard line as a healthcare agent that does not give medical advice.
Weekend calls arrive structured by category — claim, policy, premium, address, document — sorted by your rules. Not a voicemail list. The Schadenbearbeitung opens the day with a queue, not a backlog.
The agent operates inside the bounds your regulator already sets. It does not give advice, it documents what was said, and it routes anything that requires a §34d / §34i licensed advisor to a human. Transcripts, retention windows, and routing rules are signed off by your compliance lead before the pilot starts.
Four weeks of pilot operation, success criteria agreed up front, no annual lock-in. If the numbers don't move, you decide against the rollout — and keep what you learned about your call mix.
GDPR in the call path. Voice tuned for EU/DACH. Calls tied to outcomes, tasks, and audit — without your team gluing it together.
Goal, knowledge, handoff rules, and provider choices are written down before live traffic. The rollout has an owner, a path, and an end date — not just a kickoff deck.
Scope, goals, owners
Knowledge + providers
Quality review
Production traffic
Multi-carrier routing, monitored failover, and runtime observability — so transfers actually go through and call records stay intact when traffic spikes.
99.95% uptime
Same agent logic across English, German, French, Italian, Spanish, and 45+ more — with per-workflow language pinning and regional accent handling when it matters.
+ 45 more languages
Optimized WebRTC and SIP infrastructure — callers hear no delay, anywhere in Europe.
Reviews, follow-up tasks, and handoffs all tie back to the source conversation. No re-reading transcripts in a spreadsheet to figure out what to do next.
Hear how voice AI sounds in your industry — and where it delivers impact first.