A voice call is not “done” if the cost is still invisible
Summary
A developer argues that voice call logs must include cost and token data, not just duration and status, to properly assess voice-agent economics, sharing a lesson from a stress test where cost fields were initially null.
Similar Articles
A phone call is not done when the audio ends
The article argues that phone calls handled by AI agents are not complete when audio ends; the real test is whether promises (e.g., callbacks) are properly captured in the work queue with owners, deadlines, and evidence, rather than just having a nice transcript.
Are coding agents getting expensive, or are we measuring cost the wrong way?
The article questions whether the real cost of coding agents includes hidden human oversight and debugging, arguing that true value should be measured by trusted output rather than raw token consumption.
When I finally instrumented my agents' tool calls, the cost breakdown surprised me. A few lessons.
The author shares lessons from instrumenting AI agent tool calls, revealing that tools like web_search can account for ~50% of spend, and highlighting the importance of tracking p95 latency and attributing costs per workflow or customer to avoid surprises.
Same agent, same task, wildly different costs per session?
A discussion on AI agent observability highlights unpredictable cost variations and dangerous failure modes like unauthorized database deletes, prompting questions about production handling strategies beyond basic logging.
6 months running a production voice agent for service businesses. The latency math is way harder than the demos suggest.
After 6 months running a voice AI agent for service businesses, the author reveals that real-world latency is bimodal (median ~800ms, p95 ~2.4s) and this p95 determines user perception. Issues like VAD misfires, function call degradation with long prompts, and TTS quality matter more than LLM choice, with multilingual support adding significant costs.