Proactive & transfer
Voice MCP can place proactive outbound briefing calls through a guarded dialer, and warm-transfer a live call into a conference bridge.
Beyond answering inbound calls, Voice MCP can reach out on its own — and hand a live call to a colleague.
Proactive outbound briefings
Voice MCP can place outbound briefing calls, such as a morning briefing at a user's chosen hour. Every outbound call goes through a single guarded dialer that enforces a stack of protections before anything rings:
- Opt-in — the recipient must have opted in.
- Quiet hours — calls are suppressed outside the allowed window.
- Rate limiting and cool-off — repeat calls are throttled.
- Hard daily budget cap — a per-tenant daily dollar cap that even a forced call cannot exceed.
The dialer places calls through the tenant's telephony client. When no telephony credentials are configured, it degrades to stub mode — the guarded flow runs end to end without actually dialing.
Off unless double-enabled
The briefing scheduler is double-gated and off by default. It runs only when the operator turns on the scheduler environment switch and the tenant carries the proactive feature flag. Treat proactive calling as an opt-in, gated preview — not a default-on capability.
The budget cap is not optional
A forced call — such as a user-initiated test call from settings — skips the readiness gates (opt-in, quiet hours, cool-off, and rate limit), but it still cannot exceed the hard daily budget cap. Spend protection is the one guard that always applies.
Warm transfer and conference
During a call, the agent can transfer the caller to a colleague. The transfer is implemented as a redirect into a conference bridge (<Dial><Conference>), so the parties can be joined together rather than blind-handed off.
As with outbound dialing, when telephony credentials are absent the transfer path uses a stub client and does not place a real bridge.