Skip to content

For teams / Voice AI use cases

AI
phone receptionist

Build an Omni voice agent that greets callers, answers from your knowledge base, books appointments, and transfers to your team when the conversation needs a person.
A thoughtful greeting, at any hour.
PyAI / WorkspaceActual product
The PyAI Console agent editor showing instructions and voice settings with sample data
The actual agent editor, shown with sample data. Configure it for your own workflow.Explore Agents
What you are building toward

Answer every call 24/7 with a natural agent that books, answers, and routes.

A practical way to start

A few clear steps.
One useful workflow.

Connect the pieces for this use case, then test the full experience with the calls, recordings or text your users will bring.

  1. 01

    Describe the agent

    Give it a persona, your hours and policies, and your business context in the console - no code.

  2. 02

    Ground it in your docs

    Upload your FAQ, pricing, and policies; Omni answers from them instead of guessing.

  3. 03

    Point your number at it

    Connect Omni's realtime endpoint to your telephony and go live. Warm-transfer to staff anytime.

See the workspace behind it

Make the setup
your own.

Write the instructions, choose a voice and connect the knowledge and tools for the job. Then test the conversation before connecting it to your callers.

Explore Agents

Follow the real Console with a sample workspace, narrated by Aria, our Natural English voice.

Product tour
Actual Console UI · sample workspaceAria Natural · PyAI Speak

The right part of the voice stack

Built around your job.
Powered by PyAI.

Explore the product behind each part of this use case, including its controls, API examples and integration requirements.

Before you take it further

A little more detail.
A clearer next step.

Start with a sandbox key and a representative input. Review the result before widening the workflow.

How does PyAI support ai phone receptionist?

Build an Omni voice agent that greets callers, answers from your knowledge base, books appointments, and transfers to your team when the conversation needs a person.

What does it cost to test this use case?

Sandbox keys never bill, so you can try the product before sending funded live traffic. Live usage requires available credit and uses the rates for the products in your workflow. See current pricing and account terms before a production rollout.

Can we keep our existing application?

Yes. Hear and Speak support OpenAI-compatible request shapes. Omni uses its native realtime protocol through the official SDK. You can also configure a managed Agent visually and connect the knowledge and tools your business already uses.

How do we keep the experience useful in production?

Give the agent clear instructions and business content, connect tools for real actions, and define when it should reach a human. Test with representative calls before a wider rollout. Use Trace and Recap where the workflow needs reviewable findings, summaries and follow-up.

Put the idea into motion.

Sandbox keys never bill. Fund a live key when you go to production.