News and analysis
Voice AI demos: control calls even when the rate stays unchanged
Twilio examines abuse of a public demo; HighLevel cancels announced rate changes. Price and permitted consumption need separate checks.
A voice-agent demonstration can perform a real billable action: the server calls a number entered by a visitor. The URL may seem obscure, but internet reachability already calls for access controls. Two October publications are useful together because they separate the price of a minute from the volume of permitted calls.
What happened in the described demo
On 6 October, a Twilio author examined his own Voice AI incident, with approximately $971.50 in Twilio charges and $10.58 in Gemini usage over about four hours. These are the costs of one described incident, not a forecast for every demonstration. The article discusses a public endpoint that initiated outbound calls.
Log patterns were consistent with telephone traffic abuse, but could not establish who received revenue. The incident preceded publication. For a new project, the important mechanism is that an external request could initiate a real call using the application owner’s account.
The practical implication is that an address is not authorization. Even an unadvertised URL needs an identified caller, permitted destination and bounded usage for the server action. Acceptance of a “call me” interface should include these properties rather than only the quality of the AI conversation.
Read the whole pricing update
In its 12 October update, HighLevel cancelled previously announced Voice pricing changes scheduled for 13 October. The body states that affected rates remain unchanged. A headline about pricing updates is not itself evidence of an increase.
The connection is specific: an unchanged rate does not make public calling safe from unexpected consumption. Without appropriate restrictions, usage can change independently of the price. Checking the current rate is necessary, but does not establish who initiated calls.
Check the demo before opening access
Use a separate test environment and agreed sample numbers. Establish who may start an action, allowed destinations, concurrent-call limits and duration controls. Define a way to stop the demonstration when unusual activity appears.
Repeat a request and check that it does not create an unintended extra call. Correlate the application event with the provider’s record and call outcome. Logs should help establish the action path without unnecessarily exposing customer details.
These are design checks, not a promise to eliminate abuse. Public access needs a named person responsible for monitoring and shutdown decisions. A visual test without telephony can instead use a clearly labelled scenario that makes no calls.
Our business rules guide helps define permissions. The archived call-centre project provides telephony and CRM context, without claiming this incident as our experience. For your voice workflow, discuss the boundary between a demo and a billable action.