Skip to main content
bVOIP, renamed 1Stream in April 2026, hosts a phone system for each of your clients. Connect it once with a Partner API key from the bVOIP Control Portal, and Neo reads every phone system your partner account owns.

What Neo can do with bVOIP

  • Tell the people you choose about each new voicemail, by client and mailbox, with the caller and the time
  • Check a user’s extension, phones, forwarding and the phone system’s health on a phone ticket
  • Read a client’s call history and call counts, when the phone system is connected to 1Stream
  • Add or change extensions, queues, ring groups, phone numbers and call routing, with the approvals your access profile sets

Voicemail notifications

A scheduled agent checks your clients’ phone systems every few minutes and sends one notification for each voicemail left since its last run: a Teams or email message, a ticket on the client, or a 1Stream on-call rule. Ask the Neo Support Agent for the agent you want, such as “every 15 minutes, tell the on-call technician in Teams about each new voicemail in the support mailbox (extension 800) of every client”. Keep “every N minutes” in its instructions: the agent reads how often it runs from there, so each voicemail is reported once. To find the voicemails it needs the Voicemail and Recordings and Phone Systems, Services and Reboots groups at Read Only; to alert through a 1Stream on-call rule it also needs Live Calls and On-Call Alerts at Read / Write. The audio stays in bVOIP: the notification says where to play it.

Each ticket stays with its client

One Partner API key reaches every phone system of your partner account. On a ticket that names a company, Neo sends a call only for the phone system that company is mapped to. Work across every client is for chats and scheduled agents.

Your phone systems are mapped to companies

Neo matches your bVOIP phone systems to the companies in your PSA and keeps the mapping on the bVOIP card’s Organization Mapping tab, refreshed on each PSA metadata sync. A phone system carries no client name, so the match reads the first part of its address: contoso.bvoip.net reads “contoso”. The standby system of a high-availability pair is left out, so a client maps to the system that serves its calls. A name that matches exactly one of your PSA companies, as it is or after stripping a legal-form suffix (Ltd, Inc, LLC), or a match you confirm, is handed straight to your agents. An AI match waits for you on the Organization Mapping tab, and so does a name two of your PSA companies share, or two phone systems that match one company. Confirm or correct each there. Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right company by hand. A mapping you set by hand survives every later sync. See bVOIP API for the permission groups.

Next steps

Connect bVOIP

Make a Partner API key in the bVOIP Control Portal and save it in Neo.