Quality on the actual call
Evaluate the audio your callers hear, the details the system captures and the action it completes. Native 8 kHz phone audio is available in Omni; use the supported audio format for each product.
PyAI AMD
Open the existing product experience, choose the matching settings and evaluate your actual words or recording.
Answering machine detection analyzes the beginning of an answered call to distinguish a person from a voicemail greeting or other automated response. Your calling workflow uses the result to choose its next action.
Route outbound calls with clearer handling of live answers, voicemail and uncertain classifications. AMD is a classification component, not an agent or a guarantee about the caller. Evaluate false machine decisions and classification delay together, using the carriers and greetings your calls encounter.
Evaluate the audio your callers hear, the details the system captures and the action it completes. Native 8 kHz phone audio is available in Omni; use the supported audio format for each product.
Hear and Speak offer OpenAI-compatible speech endpoints. Omni uses the realtime PyAI SDK. Pair the conversation with AMD, Trace, Recap and managed telephony where your workflow needs them.
Review the product meter, sandbox limits and managed telephony terms on the pricing page. Cloning enrollment and prompt-to-voice design are free; generated speech follows synthesis billing.
Connect the call's audio stream using the documented AMD integration.
Choose the detection policy and handle human, machine and uncertain results explicitly.
Test representative greetings, carrier messages and live answers before applying the policy to your outbound workflow.
Listen to stock voices before choosing the voice for your workflow. A language label does not promise every regional accent. For generated speech, you can also enroll a voice you have permission to use or design a voice from a prompt. Verify language and product compatibility before using the result.
Listen to the voice directoryGreet a caller clearly, understand the request and connect the right next step.
Read back names and dates and confirm the actual booking result before announcing success.
Compare AMD policies with the same live-answer and voicemail examples. Faster decisions are useful only when false classifications remain acceptable for your workflow.
Read the comparison and migration guidanceAnswering machine detection analyzes the beginning of an answered call to distinguish a person from a voicemail greeting or other automated response. Your calling workflow uses the result to choose its next action.
AMD is a classification component, not an agent or a guarantee about the caller. Evaluate false machine decisions and classification delay together, using the carriers and greetings your calls encounter.
Connect the call's audio stream using the documented AMD integration. Choose the detection policy and handle human, machine and uncertain results explicitly. Test representative greetings, carrier messages and live answers before applying the policy to your outbound workflow.
PyAI offers sandbox testing with limits. Live usage follows the product's billing terms; see https://pyai.com/pricing for current rates, inclusions and managed telephony charges. Free testing does not mean unlimited free production usage.
Start with the product's documented API and integration guide. Omni uses the PyAI realtime SDK; an OpenAI-compatible speech endpoint does not make every realtime or workflow API interchangeable.
Test representative names, dates, amounts, audio conditions and corrections. For agents, include business-tool failures and handoff to a person; inspect the observed outcome, not just a transcript.
Speak supports stock, cloned and prompt-designed voices. Cloning enrollment and voice design are free; synthesis follows the current billing terms. Use a voice you have permission to reproduce and verify its intended language and product compatibility.