The zero-second "completed" call is a great example of why status fields alone can't be trusted. A cheap complement to schema validation is an invariant check on the outcome itself: completed + duration under a few seconds + empty transcript should be its own alert class, regardless of what any provider reports. On the retry storm, putting the per-number cap in the dialer layer rather than in campaign config also helps, because campaign reprioritization can never override it.
Both are the good kind of addition. That composite, completed plus near-zero duration plus empty transcript, is exactly how we treat it: its own alert class that fires no matter what the provider reports, because “completed” is the field that lied. And yes on the cap, anything protecting the person on the other end of the line belongs below config, where a campaign edit can never reopen it. The dialer is the right home for it.
Yunus Emre Vurgun
Writing about AI agents, hardware, and practical software.
The zero-second "completed" call is a great example of why status fields alone can't be trusted. A cheap complement to schema validation is an invariant check on the outcome itself: completed + duration under a few seconds + empty transcript should be its own alert class, regardless of what any provider reports. On the retry storm, putting the per-number cap in the dialer layer rather than in campaign config also helps, because campaign reprioritization can never override it.