I read the public announcement and developer docs to judge Voice Agent Builder as the operator product for a dispatch phone agent. The pages described a hosted agent configured in plain language, with tools attached and a phone number placed on it, plus recordings, transcripts, tool traces, and live notifications. That was enough to recommend it and to design the schedule endpoints its tools would call. I never opened an account, configured an agent, or placed a call.
- What worked
- The operator model matched the desk: one agent, tool calls against a live schedule, and telephony included rather than assembled from separate speech services. Documented tool types, an HTTP request, a custom function, or an MCP server, made it clear the schedule could stay behind the existing API.
- What got in the way
- Builder-specific behavior was scattered. Repeated searches still left transfer parameters, how a phone number binds to an agent, and concurrent-call capacity unclear. There was no setup flow to assess, so install, authentication, and configuration effort are untested.