Kilevel
Dashboard

Language / Sprache

KILEVEL © 2026

Germany

AI voice agents for businesses in Germany

Agents that hold calls in German, tell callers they are speaking with an AI, and record only after consent, with the documentation a German procurement review asks for.

This page inEnglishDeutschTürkçe

The problem

A voice agent in Germany has to do more than speak the language. Callers must be told they are talking to an AI, recording usually needs explicit consent, and data protection officers and works councils will ask how it all works.

Who it is for

  • Companies in Germany: Serving German-speaking callers.

  • Data protection and IT: Reviewing where data goes and who processes it.

  • Works councils: Assessing performance measurement.

What it handles

  • German conversations

    German speech recognition and voices, with numbers and dates read the way a native speaker would say them.

  • AI disclosure

    For workspaces in the EU it is on for every voice flow and cannot be turned off. The sentence is spoken first and cannot be talked over.

  • Recording consent

    A step asks, waits for a clear yes or no, spoken or by keypad, and starts recording only on a yes.

How it works

  1. Build in German

    Set the flow's language and pick a German voice.

  2. Add consent

    Start unrecorded and add the recording consent step.

  3. Check with your advisers

    Review the disclosure wording and your legal basis with counsel.

What you need

  • A German or other suitable phone number, or a SIP trunk
  • Your disclosure wording, or a preset
  • A decision on what is recorded and how consent is checked
  • Your data protection officer's review

What it connects to

  • Voices: ElevenLabs and PlayHT, with Fish Audio as an EU and GDPR-oriented option.

  • Telephony: SIP trunks to your carrier, plus Twilio and Telnyx.

What to expect

  • Callers know they are speaking with an AI from the first sentence.
  • Recordings begin only after the caller has agreed.
  • Your review has documents to work from.

Limits

  • This page is not legal advice. As controller, you are responsible for the lawfulness of the processing.
  • Custom disclosure wording replaces text designed for the purpose. Have it reviewed.
  • Consent checks that involve the model rely on its judgement for a legally required step.
  • Not every processing step happens in Germany or the EU. Recordings are stored in Frankfurt; the Trust Center lists every subprocessor and where it processes data.

How to evaluate it

  • Start with the Trust Center: Read the subprocessor list and the Data Processing Agreement first.

  • Test the consent path: Try yes, no and unclear answers, and check the recording.

Questions

Is AI disclosure mandatory?

The EU AI Act (Article 50) requires that people are told when they interact with an AI system. In EU workspaces, disclosure is on for every voice flow and cannot be turned off.

Where are recordings stored?

In Frankfurt, Germany. Other processing steps may involve other providers: the Trust Center lists each subprocessor and where it processes data.

Is there a Data Processing Agreement?

Yes. It forms part of the terms and is published under Legal.

See it on your own calls

Start with a test number and a small set of real questions. Nothing has to change on your main line until you decide it should.