Capability map
NextGenSwitch brings PBX, queues, outbound engagement, selected automation, multi-tenant administration, and integration workflows into one modular platform.
Availability, limits, dependencies, implementation, and support vary by module, plan, and deployment.
Core capabilities
Start with the workflow your team needs to prove, then add modules as requirements become clear.
What sits outside the platform
A feature can be present in the application and still require external services, infrastructure, configuration, policy decisions, and testing before it is ready for a live workflow.
Confirm these dependencies during evaluation so product capability is not confused with an included carrier, cloud, AI, messaging, or managed service.
Review Platform Fit| Area | Typical dependency |
|---|---|
| Calling and numbers | Compatible SIP trunks, DIDs, termination, caller identity, codecs, and capacity from telecom providers. |
| Infrastructure | Compatible compute, storage, network, DNS, certificates, backups, monitoring, and deployment operations. |
| AI and speech | Configured model, speech recognition, text-to-speech, credentials, quotas, latency, and data policies. |
| Messaging | Approved channel providers, sender identities, templates, consent, opt-out, and delivery configuration. |
| Business systems | Documented APIs, authentication, permissions, mappings, error handling, and ownership for connected tools. |
| Governance | Security review plus applicable consent, recording, retention, privacy, and outbound-contact policies. |
Module documentation
Use the module guides to review available fields, workflow steps, examples, maintenance notes, and troubleshooting guidance in the current documentation.
Manage user and device SIP credentials with extension codes, security controls, and optional forwarding.
Read Extensions DocsConfigure shared SIP identities for rotating agents and temporary devices.
Read Hotdesks DocsDistribute inbound calls to multiple extensions simultaneously or by strategy with configurable failover.
Read Ring Groups DocsManage inbound waiting lines with announcements, member priorities, timing controls, and failover routing.
Read Call Queues DocsDefine DID and caller-ID matching rules that route inbound calls to IVRs, queues, extensions, and more.
Read Inbound Routes DocsConfigure dial patterns, trunk selection, number normalization, and optional failover for outbound calling.
Read Outbound Routes DocsConfigure SIP trunk connectivity to carriers or peers with credentials, capacity rules, and caller ID behavior.
Read Trunks DocsConfigure IVR menus with prompts, digit or speech input rules, and fallback destination routing.
Read IVRs DocsPlay voice announcements before sending calls to the next destination.
Read Announcements DocsAutomate outbound dial workflows with scripts, schedules, pacing rules, and campaign-level controls.
Read Campaigns DocsRun unattended high-volume outbound voice outreach with scheduling, retry controls, and answer routing.
Read Broadcasts DocsCentralize customer issue tracking, assignment, and resolution workflows.
Read Support Tickets DocsAI Assistants (AI Bots) answer calls with conversational AI, tailored prompts, and fallback transfer routing.
Read AI Assistants DocsShare your call flows, agent and tenant counts, concurrency, carrier setup, integrations, hosting preference, and rollout timeline.
The team can help identify relevant modules and questions to resolve. Final scope depends on technical review and the selected engagement.
Discuss Your RequirementsExplore a working environment, inspect the relevant module documentation, and compare plan scope before designing a production rollout.