Recording consent
Start recording only after the caller has agreed — with a consent step that asks, checks the answer, and starts the recording itself.
In some jurisdictions — Germany is the best-known example — a call may only be recorded after the caller has explicitly agreed. "Stay on the line to continue" does not count; the caller has to say yes or press a key.
The building blocks
Three nodes on the flow canvas, available on voice flows:
- Recording consent — asks the caller, waits for a clear yes or no (spoken, or a keypad digit), and starts recording automatically on a yes.
- Start recording and Stop recording — for flows that control recording themselves, for example pausing while payment details are given.
The question is pre-filled and translated into the flow's language, and can be edited. Every start and stop is logged with a timestamp.
Checking the answer
Choose how "yes" is recognised:
| Check | How it decides |
|---|---|
| Model | The model judges whether the caller agreed. Understands every supported language; the default |
| Keyword | A fixed list of yes/no words. Predictable, but covers only a few languages |
| Either | Recording starts if either check says yes |
| Both | Recording starts only if both checks say yes |
Warning
Any check that involves the model relies on its judgement for a legally required step. The editor marks those modes with a warning. Decide, with your counsel, which check your use case needs.
Starting a call unrecorded
For consent-first flows, start the call with recording off and let the consent step turn it on. A recording started this way contains only what was said after consent.