The OutboundMessage webhook currently fires only for completed calls.

It should also fire for: no answer, busy, failed, canceled, voicemail etc.

Call status already exists in the payload, and native workflows already support all statuses (no answer, busy, failed, etc.). However, the API webhook does not - creating missing API/webhook parity.

Workflows are not scalable or reliable for external reporting systems (e.g. speed-to-lead tracking).

Small change. High impact for developers and agencies