A caller knows something is wrong. A device knows where they are. A public safety operator needs both pieces of information, preferably before the conversation becomes a guessing game. Between those three points sits a surprisingly large amount of work. Viiz Communications has made that middle distance its business.
- Carriers buy voice services and routing. Enterprises buy customer support.
- Connected-device companies use Viiz agents to respond to alerts and pass useful information onward.
- Public safety teams can add live backup and AI for non-emergency inquiries.
Consider the Consumer Cellular IRIS Ally medical alert device. It can be worn on a lanyard or clipped at the hip. Its features include fall detection, location tracking and two-way communication. But the interesting part of this product is also the least visible: the arrangement for someone to answer.
Under the partnership announced in October 2024, a Viiz agent responds by voice when the device is activated. The monitoring platform brings supporting data into the interaction. The agent assesses the situation and passes appropriate information to first responders. A wearable produces a signal; a service turns that signal into a conversation with consequences.
The telephone book had a second act
Viiz’s own history begins in 2004 with James MacKenzie and John Wilson, two executives with Nortel experience. The company developed telecommunications technology and services, expanding through research and acquisitions. In October 2016, WiMacTel announced that it would become Viiz. Its announcement described more than 1,200 communications-provider and enterprise customers.
The old work still matters. Viiz offers directory assistance, operator services, billing support and routing for abbreviated N11 numbers. It also replaces aging voice platforms with cloud-based systems, preserving features clients still need. A familiar telephone service can depend on an unfamiliar stack of infrastructure. Moving that stack is a business in its own right.
There is a useful connection here. Helping somebody complete a call requires routing knowledge, reliable information and a workable escalation path. Those capabilities also matter when a connected device reports trouble. Viiz’s move toward emergency support becomes easier to understand when you follow the work rather than the product labels.
The alert is only the beginning
Viiz describes its emergency workflow in three steps. A device or application sends an alert and available data through an API. A specialist receives it and, where possible, speaks to the user. When emergency assistance is needed, the specialist makes a handoff to the appropriate public safety answering point, or PSAP, and stays on the call to share relevant details.
Simplified from Viiz’s published emergency workflow. The next action depends on the situation.
The company applies that arrangement to wearables, home safety systems, applications and connected mobility. Its promise depends on joining data transport to operational judgment. A vehicle sensor, for example, supplies information; the response workflow determines what happens with it. Viiz sells the integration and the staffed operation around that information.
That combination distinguishes its offer from buying a communications tool alone. It also makes implementation consequential. Clients need to decide what information agents receive, what agents should ask and where calls should go. The API is a starting point. The practical product is the sequence that follows.
AI meets the municipal boundary
ViizViital extends the approach to non-emergency inquiries at public safety call centers. Announced in February 2025, it uses conversational AI to answer questions and direct callers to resources. Viiz offers live-agent support alongside it. The service is intended to give telecommunicators more room for calls requiring immediate attention.
Insight’s implementation account identifies staffing shortages as the pressure behind the project. It reports a ten-week implementation and 60% shorter non-emergency call times. Those are partner-reported results, rather than a guarantee for another center. More revealing is what testing added: a disambiguation tool for a county containing multiple municipalities, absent from the initial minimum viable product.
“If you’ve seen one 911 center, you’ve seen one 911 center.”Chad Brothers, in Insight’s implementation account
Local differences changed the build. An answer can be sensible and still belong to the wrong jurisdiction. For anyone designing a similar system, the transferable lesson is to test geographic ambiguity early and make human escalation explicit. Success depends on more than recognizing a caller’s words.
Capacity is part of the product
Viiz’s commercial model spans software as a service, business process outsourcing and combinations of the two. A customer can buy technology, staffed execution or an integrated service. Its customer-care work includes technical support, after-hours coverage, carrier account assistance and healthcare coordination. Teams are adapted to a client’s brand and requirements.
ViizLiink offers live-agent support for emergency and non-emergency overflow. Its TransferAssist service addresses misrouted and out-of-jurisdiction calls: participating PSAPs configure a dedicated transfer number, and Viiz agents identify the correct destination and complete a warm transfer. The company advertises pay-per-use pricing. That gives the service a concrete purchasing unit: assistance when a transfer is needed.
Training is part of the operational substance. In October 2024, Viiz’s Anniston monitoring center received TMA Five Diamond designation. The program’s requirements include operator education, alarm confirmation and emergency preparedness. In this market, an effective conversation depends on preparation long before a call arrives.
Build around the next handoff
The attraction for a carrier, device maker or public agency is understandable: combine specialist communications infrastructure with people who can operate the workflow. The fit depends on local procedures, reliable integrations and clear escalation responsibilities. A poorly maintained directory or an unclear transfer rule would weaken the arrangement, however fluent the automated voice.
In April 2026, Viiz reported Chad Brothers’ participation in a Google Cloud Next discussion about conversational AI modernization. The company’s useful question remains wonderfully concrete: after the information arrives, who can do something with it? For a business built around answering calls, that is a sensible place to keep looking.