Inbound Dropped

Where a caller lands when the stream dies under them.

⛔THE CALLER IS STILL ON THE LINE, AND UNTIL THIS THEY GOT SILENCE. Plivo plays this because <Stream keepCallAlive="true"> leaves the leg up when the websocket goes; before it existed there was nothing after the stream element, so the call simply ended. Frederick, 2026-09-14, after staging redeployed mid-sentence: "Rooster said hi, and the phone hung up on me."

The same floor the agent's own absence gets: apologise, and take a recording either way. inbound_answer's failsafe branch carries the reasoning for doing BOTH. Whether a callback gets booked, and on what number, is _how_to_book_a_dropped_call's job -- see its own comment for the current rule (RULE 4) and the three it replaced, kept rather than deleted. ⛔RULE 4 BOOKS NOTHING IN PRACTICE TODAY -- that is the intended behaviour, not a gap; see _how_to_book_a_dropped_call's own docstring.

⛔AND THIS CALL'S OWN ROW IS ALWAYS SETTLED, whatever gets booked or not, via service.settle_after_dropped_stream -- a row left reading 'ringing' blocks a redial on its ticket for up to thirty minutes (see that function's own docstring for the production numbers). Frederick: "they should just be able to call them back ... it's easier than sending the human back through the loop."