cloudvoicemanager.com

Menu
ARCHITECTURE

Built Like Infrastructure. Not a SaaS Black Box.

Cloud Voice Manager is a self-hosted communications platform built to route calls reliably, process AI conversations in real time, store call data under your control, and stay synchronized with the HMS Cloud Fleet automatically. This page explains the architecture at a level business and technical buyers can both trust.
See the Deployment Model
Talk to Sales

A Phone System Touches More Than Phones

A modern communications platform is not just SIP trunks and extensions. It is audio streaming, live transcription, AI orchestration, CRM sync, routing logic, user permissions, media storage, reporting, and tenant isolation – all moving at the same time.
If the architecture is weak, the product will feel weak. Calls will get dropped. Data will fragment. AI will lag. Reporting will lie. Security will become an afterthought.
Cloud Voice Manager was designed to avoid that entire category of failure by treating the phone system as operational infrastructure from the start.
HIGH-LEVEL PLATFORM OVERVIEW

The Platform Has Four Core Layers.

Telephony Layer

Telnyx provides carrier-grade SIP trunking, DID provisioning, SMS delivery, and media connectivity. This is the ingress and egress point for calls and messages.

Control and Routing Layer

Cloud Voice Manager manages extensions, queues, IVR logic, routing rules, number assignment, tenant scope, permissions, call state, and operational workflows.

AI and Transcription Layer

Deepgram handles speech-to-text in real time. Cloud AI Manager provides knowledge, prompts, and persona controls. Cloud Voice Manager orchestrates the live AI interaction.

Data and Business Context Layer

SALT CRM, HMS merchant context, recordings, transcripts, audit logs, SMS records, and reporting data provide the persistent business record of every interaction.

The architecture works because these layers are coordinated by design – not stitched together after deployment.

INBOUND CALL FLOW

What Happens When a Call Comes In

Number Hit

An inbound DID routes through the Telnyx carrier layer into Cloud Voice Manager.

Tenant and Route Resolution

The platform identifies the tenant, number mapping, time-based rules, and the correct route path for that call.

Call Handling Decision

The route decides whether the call rings a user, hits a queue, enters IVR logic, reaches voicemail, or is answered by an AI voice agent.

Live Interaction

During the call, state changes are tracked in real time. Recording, transcription, AI orchestration, and queue logic all operate against the same active call context.

Transfer or Completion

The call is either completed, transferred, escalated, or routed onward with the full context preserved.

Post-Call Writeback

Metadata, summary, transcript, disposition, and recording links are stored and synchronized to the right systems automatically.

AI AUDIO FLOW

Real-Time AI Without Breaking the Call Experience.

AI call handling only works when latency stays low and context stays coherent. Cloud Voice Manager keeps that loop tight.
  • The live caller audio stream is processed in real time
  • Deepgram converts speech to text with sub-second latency
  • Cloud Voice Manager passes the live transcript and call context into the AI orchestration layer
  • Cloud AI Manager supplies persona, prompt, and knowledge context
  • The AI response is generated based on live intent and business rules
  • The caller hears a real-time reply, not a delayed post-processing result
  • If a human transfer is required, the active context is handed off rather than discarded
This is what allows AI agents to feel like part of the phone system instead of a separate experiment bolted onto it
POST-CALL DATA FLOW

The Conversation Becomes a Business Record Automatically.

When a call ends, Cloud Voice Manager turns the live interaction into structured data
that the rest of the business can use.

Call Detail Record

Finalized with route path, duration, direction, and outcome

Recording Storage

Stored according to the deployment's retention policy

Transcript Indexed

Attached and indexed for search

CRM Sync

SALT CRM receives the activity record and linked assets

API Access

Webhooks and API-accessible objects available

Reporting Update

Layers update for supervisors, admins, and partners

Reporting Update

Layers update for supervisors, admins, and partners

This is the difference between “we took a call” and “we captured what happened and made it operationally useful.”
DEPLOYMENT MODEL

Self-Hosted by Design

Cloud Voice Manager is not a shared-cloud tenant on someone else’s SaaS platform. It is deployed on infrastructure controlled by HMS, the partner, or the business operating the system.

What the Deployment Model Delivers:

  • Control over data residency and storage policy
  • Predictable scaling tied to your own infrastructure choices
  • Freedom from per-seat SaaS licensing pressure
  • Tighter control over recordings, backups, and retention
  • Ability to align the communications stack with internal security requirements

For technical evaluators, this means fewer unknowns. For business buyers, it means more control and less vendor dependency.

MULTI-TENANT BOUNDARIES

One Core Platform. Clean Tenant Separation.

Cloud Voice Manager’s multi-tenant architecture is designed so one deployment can serve many businesses, brands, or locations without mixing their data or operational logic.

Isolation Happens at Multiple Layers:

Per-tenant routing, numbers, users, and permissions

Separate call history, recordings, transcripts, SMS threads, and voicemail stores

Independent AI personas, knowledge assignments, and business rules

Tenant-scoped administrative access

API and reporting boundaries enforced per tenants

This is the difference between “we took a call” and “we captured what happened and made it operationally useful.”
RELIABILITY, SCALE, AND OBSERVABILITY

Built to Stay Useful Under Load

Reliability is not one feature. It is the outcome of multiple architectural decisions working together.

Carrier-Grade Telephony

Through Telnyx

Predictable Call Handling

Queueing and routing logic designed for reliability

Real-Time Visibility

Through the live dashboard

Searchable Logs

Audit trails and reporting for investigation

Tenant-Scoped Controls

Prevent one environment from disrupting another

Flexible Retention

Storage controls to match operational needs

The goal is simple: when call volume rises, your system should become more valuable, not more fragile.
ARCHITECTURAL TRANSPARENCY

Transparent Architecture. Sensible Boundaries

The public architecture story should explain how the platform works without exposing sensitive implementation details. That means public diagrams stay high-level by design.

What Stays Out of the Public Site:

Internal IP addresses and hostnames

Private ports and service discovery details

Environment-specific infrastructure maps

Sensitive credential flow details

Internal-only deployment procedures

Detailed implementation artifacts belong in private technical documentation, not on a public marketing page

Understand the Stack Before You Buy the Stack.

Book a technical walkthrough of Cloud Voice Manager to see the call flow, AI audio path, deployment model, and data architecture in a format built for technical reviewers and operational leaders.
Book a Technical Walkthrough
Explore Security
Talk to Sales