Evidence Calls where the voicemail tool worked correctly (Gloria heard the greeting, waited for beep, left a message): 019c72b9-6336-788b-930e-b2f477019c7b — "Please leave your message for 213..." → Gloria left full voicemail ✅ 019c7288-2c1c-7441-9731-ca538030b4c7 — "Please leave your message for 425..." → Gloria left full voicemail ✅ Calls where something kills the call before the tool fires (ended as voicemail with no AI response): 019c72d3-a424-744c-8b2c-e7fccaf46d27 — VM greeting transcribed fully, Gloria never spoke, call terminated. voicemailDetection was completely removed from assistant at this point. 019c72c2-81b3-7006-8fde-9f76245a89a8 — Same pattern. 019c72c6-9485-733f-b062-25b81f2d293c — Gloria only got out "Hi." before call was killed. Current Assistant Config voicemailDetection: fully removed (not present on assistant object) voicemailMessage: cleared ("") firstMessage: cleared ("") firstMessageMode: assistant-speaks-first-with-model-generated-message Voicemail tool (c7268b65-9b3f-4633-a426-0611e8357b44): beepDetectionEnabled: true Prompt includes explicit voicemail detection instructions at highest priority Question Something at the platform level appears to be detecting voicemail and terminating the call (endedReason: voicemail) independently of the voicemailDetection assistant setting. This prevents the voicemail tool from ever executing. Is there a platform-level voicemail detection that operates outside the assistant config? How do we disable it so the voicemail tool is the sole handler? Please advise ASAP.