Root-Cause Fix in a 73-Node Voice Agent
When a property owner belonged to multiple administrators, incidents were routed to the first admin the API returned. We found the bug across 50 executions and shipped a structured fix.
The challenge
IACall's "Agente Fincas Plus" voice agent (73 nodes) creates property incidents for administrators. When a property owner belonged to multiple administrators, the workflow always assigned the incident to the first admin returned by the API (resultado[0]) — even when it was the wrong one.
The approach
- Root-cause analysis across 50 executions identified the un-filtered
resultado[0]as the culprit. - 4 executions were confirmed affected (affecting Veris and Cases de Dret).
The fix
- Added
id_administradorto agents in Supabase. - New CODE node
FilterMatchesByAdmin+ aMatchFound?switch that routes to a WhatsApp "recado" (message) when no match is found. - Updated the
Create Call1node to use the new reference. - Reviewed the same pattern in
registrar_cliente/administrar_clienteflows.
Results
- Incidents now route to the correct administrator every time.
- A structured, reusable pattern (CODE node + switch) that can be applied to the rest of the call flows.
व्यावसायिक समस्याएँ
- Incidents were assigned to the wrong administrator for multi-admin property owners
- The root cause was hidden inside 73 nodes and surfaced only in specific call flows
- No-match cases had no fallback path
मुख्य लाभ
- Incidents always route to the correct administrator
- Clear fallback (WhatsApp message) when no administrator matches
- Structured fix reusable across registrar/administrar flows
- 50 executions analyzed to confirm the fix addresses the real cause
अनुप्रयोग विवरण
- 73-node Retell voice workflow (IACall)
- New CODE node FilterMatchesByAdmin + MatchFound? switch
- Supabase: added id_administrador to agents
- Same pattern reviewed in registrar_cliente / administrar_cliente