Outbound Transcription

Where Plivo hands back what was SAID on a callback.

⛔EVERY CALL HAS TO BE READABLE, NOT JUST ROOSTER'S OWN. Frederick, 2026-09-16: "we should transcribe all calls so they'll calls can be read and analyzed by Rooster um, for training purposes and we can understand what calls are about if we want to see what all the calls are about for a month, analytics."

Rooster's own conversations already carry a transcript -- he is one end of them, so record_agent_transcript writes what he heard and said. A CALLBACK has no Rooster on it: it is a manager and a customer, and until now nothing was written down at all. A month of those was unreadable and unanalysable, which is exactly the gap above.

The twin of /inbound/transcription, and a separate route for the same reason /outbound/recording is: Plivo signs the URL it posts to, so each path verifies its own. Both delegate to the SAME service.record_transcription -- one way to write a transcript, two doors it can arrive through.