Record Call Disposition

How this call ended, said by the person who was on it.

Frederick, 2026-09-17: "At the end of the call, it should force you to do a disposition on the ticket... And then that also will tell Rooster how the call ended."

⛔THE CLAIM IS ALWAYS RECORDED; THE TICKET MOVING IS A CONSEQUENCE. 77 of 142 calls in production carry no ticket at all, because somebody rang and asked nothing -- so a disposition that required one would not exist for the majority of calls, and the Rooster-learning half of this would be missing its larger part.

⛔AND IT APPENDS RATHER THAN REPLACING. If Rooster ever dispositions a call and a human later disagrees, BOTH rows survive -- that disagreement is the training signal this exists to collect.

⛔THE PATH CARRIES call_uuid, THE SAME ID AS ITS FOUR SIBLINGS. It was {call_id} -- the only one of the five /calls/{...} routes spelled that way -- and it meant the internal primary key, which no browser has. Every caller of this route sends what the Plivo SDK gave it, so the route that asked for something else answered 404 to every well-formed request.

422 on a word outside the seven an agent may choose (voice.domain. CHOOSABLE_CALL_DISPOSITIONS -- as of 2026-09-22, this is no longer the same six as CALL_DISPOSITIONS itself, which still accepts two retired words for historical rows), rather than letting the database's CHECK answer with a 500: an agent picking from a list should never see a server error, and the message names the word.