Two independent switches per line. Inbound recording announces to whoever dialled in. Outbound recording is its own decision, and its announcement is played to the CALLED party — not to the builder — because in two-party-consent regions theirs is the consent that matters. Finished recordings are stored by id and posted into the customer's thread.
Also called: record my calls · two-party consent · recording announcement · listen back to what was agreed
- 1record="record-from-answer-dual" with a recordingStatusCallback so the platform is actually handed the recording id
- 2For outbound, the announcement is hung on the <Number> element so it plays to the called party before the legs bridge — a <Say> before <Dial> would only reach the browser leg
- 3Only the SID is stored; playback streams through an authenticated proxy rather than handing out a naked link
- 4A recording that a voicemail row already owns is not threaded twice
Recording was switched on and working, and the builder who turned it on could not find a single recording in the product — the audio was being captured and kept on the carrier's side with nothing handed back. Fixing that exposed the second half: a recording that exists is not the same as one that can be found, and recorded calls were appearing nowhere near the customer's thread, which is where anyone actually goes looking. Calls you place and calls you receive are separate switches, because someone who dials a business has chosen to call it and someone you ring has not.
- Recordings that exist at the carrier but never reach the product
- Recordings unfindable outside a separate tab
- One consent switch covering two very different legal situations
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →