What problem does it solve?
Choosing the wrong Twilio recording method is the most common voice development mistake — using the Record verb instead of Dial record captures only the caller (voicemail-style) instead of both parties, and REST API recording is silently ignored on ConversationRelay calls.
Core Features & Use Cases
- Two-Party Call Recording: Use Dial record with dual-channel modes to capture agent and caller on separate tracks for QA and speech analytics.
- ConversationRelay Recording: Start recording via Start Recording TwiML before Connect, since REST API record:true is silently ignored.
- PCI-Compliant Pausing: Pause and resume recordings mid-call via the Recordings REST API when customers provide payment information.
- Use Case: A support team needs dual-channel recordings of every agent call for quality assurance, with recording paused during payment capture and callbacks validated via X-Twilio-Signature.
Quick Start
Ask the AI to generate a Flask or Express webhook that answers an incoming Twilio call and records both parties in dual-channel mode with a recording status callback.