Answering Machine Detection, often called AMD, enables you to determine if a human, answering machine or fax machine has picked up an outbound voice API call and tailor your call flow accordingly. Twilio's Public Beta Answering Machine Detection system is powered by an algorithm trained on thousands of call samples. We have tuned the system defaults to balance recognition speed and accuracy, but also provide a way for you to tune the performance of the engine based on your use case, via optional API parameters. AMD is priced at $.0075 per call.
Please see the following API parameters for configuring AMD on your outbound call.
Default : none
If you would like to leave a voicemail on an answering machine, specify
The number of seconds that Twilio should attempt to perform answering machine detection before timing out and returning AnsweredBy as
The number of milliseconds that is used as the measuring stick for the length of the speech activity, where durations lower than this value will be interpreted as a human and longer than this value as a machine.
The number of milliseconds of silence after speech activity at which point the speech activity is considered complete.
The number of milliseconds of initial silence after which an
AMD results are returned in the AnsweredBy parameter of the webhook issued to the URL you provide in the outbound call request.
|AnsweredBy||The result of answering machine detection.
Answering Machine Detection will be charged at $.0075 per call where enabled and the called party picks up. Busy or Failed calls may engage our AMD system but will not be charged.
The life cycle of a call using AMD is below. The user experience for a recipient of a call using AMD is impacted if there is a delay from the time they pick up the phone to the first packet of audio they hear. Twilio has optimized our AMD system to quickly classify calls, it is important to also optimize your application to respond quickly to TwiML requests.
To minimize delay, ensure you benchmark your application to ensure that webhooks from Twilio are processed and responded in a timely manner. In test applications running in EC2 we can get this time under 150ms, TwiML served from TwiMLBins can come in under 100ms.
If you are using Play verbs we recommend hosting your media in AWS S3 in US East 1. No matter where you host your media files, ensure that you're setting appropriate Cache Control headers. Twilio uses a caching proxy in its webhook pipeline and will cache media files that have cache headers. Serving media out of Twilio's cache can take 10ms or less, keep in mind that we run a fleet of caching proxies so it may take 10 or so requests before all of the proxies have a copy of your file in cache.
To help you benchmark your server's response time to Twilio, we expose the request duration in milliseconds for every request in the request inspector. You can view these clicking into the call detail page in the console.
Our Public Beta Answering Machine Detection solution is not backwards compatible with our legacy solution, IfMachine. It accepts different POST parameters and AnsweredBy returns different values. IfMachine is considered deprecated and will be removed from the documentation.