Use case · insurance broker
Chatbot for insurance brokers — coverage explanations, document checklists, claim-intake — without giving advice
The problem
Independent brokers spend hours on '34d-Anfrage' calls explaining the same coverage basics. Worse: every casual phone-utterance is a §60 VVG-liability ('Beratungspflicht zur unbestimmten Zahl')—you owe a written documentation of every advice given. Verbal mistakes = expensive claims.
How Mignuti Chatbot solves it
Mignuti Chatbot handles tier-1 intake: explains coverage scope (from your tariffs), collects claim-data (Schadenanzeige), schedules consultations. Hard-blocked from giving anything resembling Beratung per §59 VVG (the bot specifies: 'I can explain what's in our portfolio — for a recommendation tailored to you, please book a consultation. Per §61 VVG every advice is documented in writing.'). Document-checklists per Versicherungs-Sparte uploadable.
Example questions
- What's the difference between Haftpflicht and Hausrat?
- Do I need separate cyber-insurance for home-office?
- What documents do I need for a car-claim?
- How long is the cancellation period for my BU policy?
- Do you handle commercial insurance for SMEs?
- What's covered if my bike gets stolen?
FAQ
Doesn't this violate §59 VVG (Beratungspflicht)?
No — the bot doesn't advise, it explains. Crucial distinction: 'Haftpflicht-Police covers personal-injury claims up to €X' (explanation, allowed) vs 'You should buy Haftpflicht with €10M coverage' (advice, requires §60 VVG documentation). The system-prompt enforces this. Substantive 'should I…?' questions trigger lead-capture for booked consultation.
What about claim-intake — sensitive data flows through the bot?
PII redaction (Presidio) is built in: names, addresses, IBANs, license plates, claim numbers are stripped before any AI call and any logging. Platform data stays EU-only (Frankfurt); AI responses run via Anthropic (USA, EU-US DPF + EU SCCs). DPA per Art. 28 GDPR included.
Can the bot push specific products?
Only if you configure it — which would constitute one-sided advice and trigger §60 VVG documentation requirements. We strongly recommend: bot stays neutral, explains options, leads to consultation. Otherwise you accumulate documentation-debt fast.