New Orleans is testing Carbyne’s AI-powered Emergency Call Triage software

Once that was clear, the conversation landed in a more practical place. The strongest case for the pilot is that duplicate-call floods are real, especially in cities where one event can trigger hundreds of reports at once. In that situation, tying up trained dispatchers on “yes, we know” calls can delay people with new information or unrelated emergencies. Several people with call center or overloaded system experience said this kind of front-end diversion has existed for years with simpler tooling. The question is whether speech AI improves it enough to justify the added risk. That is where most skepticism settled. Many people argued the described task does not need an LLM-style conversational system at all. A recorded message, keypad confirmation, or a simple state machine could do most of the job with fewer failure modes and less user distrust. Others pushed back that rigid IVR logic breaks down when callers are panicked, accented, speaking another language, or unable to navigate menus. In that narrow sense, speech models may help if they are only classifying “same incident or not” and default to a human whenever confidence is low. The deeper concern was not that this specific use case is impossible. It was that governments are using “AI triage” as a politically easier substitute for staffing, oversight, and accountability. People expect the scope to creep from duplicate-call handling into broader automated call taking. They also expect blame to shift from managers onto vendors and black-box systems when something fails. So the thread did not reject automation in principle. It rejected vague system boundaries, weak fallback paths, and the all-too-familiar pattern where underfunded public services get a flashy layer of software instead of capacity.