What works today, what is in pilot and what comes next.

Pilot · voice-first core

Broad telephony is technically ready but real-world gates remain

The repository confirms provider and number configuration, flows, IVR, queues, WebRTC, recordings, reporting, provisioning, roles, backups and diagnostics. Production release still requires tests with a real provider, target hardware and the recovery process.

• Open gate: a WebRTC call on the target browser, network and headset.
• Open gate: inbound and outbound calls through a real SIP provider.
• Open gate: a physical phone using target TLS/SRTP and a full backup and restore exercise.

Planned · contact center

Supervision, outbound and integrations need a dedicated product scope

Competitors offer live supervision, listen/whisper/barge, dialers, packaged CRM integrations and advanced QA. PBXCenter does not claim these today. They are roadmap candidates requiring API contracts, permissions, audit and security testing.

• Planned: a supervisor console with secure listen, whisper and barge plus complete audit history.
• Planned: a progressive outbound dialer with limits, consent controls and destination safeguards.
• Planned: versioned CRM integrations with contact, event and delivery-error mapping.

Planned · AI and omnichannel

Transcription and digital channels cannot be navigation labels only

Transcription, summaries, scoring and email, SMS or chat only make sense with privacy, retention, cost, accuracy and responsibility controls. Until then, PBXCenter remains explicitly voice-first.

• Planned: transcription and summaries with explicit consent, retention and an off switch.
• Under analysis: omnichannel as a case-management module rather than channels pasted onto call history.
• Publication gate: working UI, API, permissions, tests, documentation and an approved maintenance model.