Moving from 3CX, Metaswitch, BroadWorks, FreePBX or Switchvox? NCS runs beside it while you move. See how

AI voice agents

AI agents that answer routine calls, on real telephony. In Beta.

Voice agents built in the NCS console answer routine inbound calls and route callers by what they need, so staff take the calls the agent hands over. Voice agents are in Beta.

Who it is for

Providers whose customers get routine calls, such as billing questions or appointment requests, and want them answered at any hour.

  • Built in the console, without code
  • Reached from any IVR menu option
  • Tested before it takes a real call

What AI voice agents do.

Build an agent

  • A role: receptionist, sales, support or scheduler
  • Languages and a voice
  • Knowledge from your own documents
  • Instructions, with help to generate them

Route by intent

  • Intents such as billing, technical support or sales
  • Each intent routes to a queue, a team, an extension, or takes a message
  • A fallback when no intent matches

On the phone system

  • Any IVR menu option can hand a call to an AI agent
  • Every agent listed with its type and status
  • Chat agents built in the same place

Your AI, too

  • APIs, webhooks and MCP integrations for AI you already run
  • A dedicated NCS team for custom AI work

Building a voice agent.

  1. 1

    Give it a role

    Receptionist, sales, support or scheduler, with its languages.

  2. 2

    Give it knowledge

    Your documents and its instructions.

  3. 3

    Map the intents

    Where each kind of request goes, and a fallback.

  4. 4

    Test it

    Talk to it before any caller does.

  5. 5

    Put it on a menu option

    Point an IVR keypress at the agent.

Who controls what.

You, the provider

  • Which plans include AI voice agents
  • Your brand throughout

Your customer's admin

  • Agents, their knowledge and their routing
  • Which menu options reach an agent

Their callers

  • Speak naturally
  • Reach a person when the agent should hand over

Works with

Every module shares one core, one identity and one app, so each one adds to the others.

Your other systems

APIs, webhooks and MCP integrations put real telephony under the AI you already run, and a dedicated NCS team takes on custom AI work.

Getting started with AI voice agents

Voice agents are in Beta. Start with one agent, on one menu option, for one routine reason people call. Test it with real questions, including ones it should not answer, before widening it.

How adoption works →

AI voice agents questions.

Voice agents are in Beta. We show what runs today on the call rather than promising it on a page.
Answer routine requests, route callers by what they need to a queue, a team or an extension, or take a message.
Through an IVR menu option pointed at the agent.
What you give it: your own documents and its instructions.
Yes. APIs, webhooks and MCP integrations put real telephony under your own AI, and a dedicated NCS team takes on custom work.