Class 5 · Reimagined

Real-Time Voice
Application Platform

Not a PBX. A programmable runtime that connects call flows, AI decisioning, external APIs, and transcription-based intelligence, all in real time.

AI Decisioning ScriptForge Logic API Integration Live Transcription Dynamic Routing
System Contrast

Rigid System vs Living Platform

Both sides receive the same call. The traditional PBX follows a fixed path. The ConnexCS platform adapts, every time.

Traditional PBX
4 min avg handle
Call Arrives
Phone rings. Fixed routing applied.
IVR Menu
Wait in Queue
Agent Answers
Call Ends
ConnexCS Platform
90 sec to agent
Call Arrives
CLI matched against CRM.
AI Detects Intent
ScriptForge Evaluates
Priority Route Applied
Agent Briefed
Follow-up Triggered
Four Ways To Build

Choose Your Level of Control

Class 5 isn't one interface, it's four. Configure standalone objects, draw a flow on a canvas, declare behaviour in markup, or write code that runs inside the call itself. Each tier trades simplicity for control, and most platforms only offer one or two of them.

Standalone ObjectsTuring-Complete Code

Static Configuration

Create queues, IVRs, ring groups, and voicemail boxes as standalone configured objects. The fastest path from zero to a working phone system, no design step required.

Configured Objects
Sales QueueQueue
Main IVRIVR
Support Ring GroupRing Group
After-Hours VoicemailVoicemail
Foundation Layer

Voice Engine Core

The standard PBX components, IVR, queues, conferencing, ring groups, exist here. But they are not fixed features of a product. They are composable primitives that voice applications assemble and reconfigure at runtime.

Interactive Voice Response
runtime

Dynamic menu trees with AI-assisted intent routing, DTMF and speech recognition inputs, and runtime path modification via ScriptForge.

playPrompt()
gatherInput()
branchOnIntent()
injectDynamic()
Call Queues
runtime

Skills-based queue management with live position announcements, callback scheduling, and API-driven agent availability checks.

enqueue()
setSkillFilter()
announcePosition()
offerCallback()
Call Transfer
runtime

Blind, attended, and supervised transfer modes. API-triggered transfers allow external systems to redirect active calls at any point.

blindTransfer()
attendedTransfer()
apiRedirect()
whisper()
Conferencing
runtime

Multi-party conference rooms with recording, muting controls, participant management, and ScriptForge event hooks on join/leave.

createRoom()
addParticipant()
muteAll()
onParticipantJoin()
Ring Groups
runtime

Sequential, simultaneous, and weighted-priority ring strategies. Runtime strategy changes via API without reconfiguration downtime.

setStrategy()
addEndpoint()
setPriority()
onNoAnswer()
Intelligence Layer

AI Decision & Orchestration

Every call passes through an AI layer that interprets intent, evaluates context, and dispatches decisions, routing, escalation, CRM triggers, and logic execution, in real time.

Incoming Call Scenarios
Input Signal
IntentProduct information / pricing
SentimentPositive (0.72)
Keyword signalspricingenterprisedemotrial
AI Processing
Intent classified: sales, confidence 0.91
CRM queried: no existing account found
Lead score calculated from call behaviour
Optimal agent matched by product knowledge
Decision Outputs
Routing Decision
Senior Sales, Enterprise pool
CRM Trigger
New lead record created in Salesforce
ScriptForge Rule
Demo scheduling IVR injected at call end
External Connectivity

API Integration Layer

The platform is fully programmable via APIs. Any external system can influence a live call, in real time, through bidirectional API connectivity.

External Systems
Salesforce CRM
Customer Data
Zendesk
Ticketing System
SAP ERP
Enterprise Resource Planning
Custom Webhook
Any External System
Integration Flow
Call Event
ConnexCS Platform
Salesforce CRM
API Request
Response
Request
GET /contacts?cli={caller_number}
Response
{ "name": "Jane Doe", "account": "Acme Corp", "tier": "enterprise" }
Call update
Caller name displayed to agent. Priority queue applied.
Transcription Intelligence

Call Content Analysis

Every call transcript can be searched using reusable Query Profiles, keyword and phrase matching rules with boolean logic that surface specific conversations across your entire call history.

Query Profiles
Profile Configurationprivate
Name
Fraud Monitoring
Query
"wire transfer" OR "routing number" OR "gift card" AND NOT "authorised"
Customer
None (global)
Action
Alert
Query Syntax
Supported expressions
Keyword matchPhrase matchAND / OR / NOTLemmatizationFull-text search
Matched Transcripts3 results
Call ID
Date
Customer
Matched Text
Leg
Score
CX-009821
2026-06-14
Acme Corp
...asked for routing number and said gift card only...
Caller
0.94
CX-009344
2026-06-13
Global Ltd
...wire transfer details needed urgently...
Caller
0.87
CX-008910
2026-06-11
Nexus Inc
...send payment via gift card immediately...
Caller
0.81
Query Profile use cases
Fraud Monitoring
Compliance Review
Customer Experience
Keyword Detection
Dispute Investigation
Programmable Logic

ScriptForge Bridge

ScriptForge executes JavaScript inline at call time, no deployment, no dial plan edits. Custom logic, conditional routing, and API calls run as part of the call flow itself.

Execution Flow
Call Event
ScriptForge Logic
Decision Execution
System Action
Live Examples
Priority routing for enterprise accounts
ScriptForge · JavaScript
// Executes on call entry
const caller = await api.crm.lookup(call.cli);

if (caller.tier === 'enterprise') {
	call.route.setPriority('VIP');
	call.queue.setTarget('senior-agents');
	call.whisper('Enterprise account — Account Manager: ' + caller.am);
}
Enterprise callers skip the standard queue and reach a senior agent with account context pre-loaded.
Platform Architecture

System Capabilities

Six integrated subsystems that operate as a unified voice application runtime. Hover each to see how it interacts with the rest of the platform.

Deployment Patterns

Use Cases

Each use case is a configured voice application, not a feature bundle. The system adapts its behaviour based on call context, not dial plan rules.

Contact Centre

Customer Support Automation

AI classifies the call intent before any agent interaction, pre-populates a support ticket with entities extracted from the live transcript, and routes to the correct queue, reducing handle time by eliminating manual triage.

Systems involved
Voice Engine AI Orchestration Routing Engine Zendesk API
Call Flow
1
Inbound Call
2
AI Triage
3
Intent Routing
4
Agent Queue
5
Auto-Ticket
Architecture Contrast

Traditional PBX vs Voice Application Platform

The same call infrastructure, rebuilt around programmability, integration, and intelligence.

Dimension
Traditional PBX
ConnexCS Platform
Routing Logic
Static, fixed dial plan, no runtime changes
Dynamic, AI-driven, context-aware, API-informed
System Integration
Isolated, no external API connectivity
Integrated, CRM, ERP, ticketing, webhooks
Call Logic
Manual, admin-configured, change-ticket required
Programmable, ScriptForge executes JS at call time
Intelligence Layer
None, no AI or ML processing
AI Orchestration, real-time intent & decision engine
Call Content
Opaque, recordings only, no analysis
Structured, live transcription, NLP, entity extraction
Architecture Type
Feature-based, capabilities bundled as product
System-based, composable runtime with open interfaces
Voice Application Platform

Stop Building Phone Systems.
Start Building Voice Applications.

Design real-time communication workflows powered by AI, APIs, and programmable logic. Connect every call to the systems and intelligence that drive your business.