Virtual receptionist
Greet callers, respond to questions, and guide them through a conversational call flow.
For MSPs, telcos and hosted-voice providers
Consolidate customer PBXs without giving up control
Give each customer an isolated tenant on one Asterisk-based platform. Add an AI virtual receptionist, call transcripts, summaries, and sentiment analysis while keeping your SIP trunks, infrastructure, and brand.
MiRTA PBX SwitchboardLive extension status
Virtual receptionist and call analysis
Talk with AI
Welcome callers with an AI virtual receptionist. Extend your voice service with transcription, summaries, and sentiment analysis for recorded conversations.
Call transcription
Turn recorded calls into readable transcripts for review and follow-up.
Call summaries
Help teams catch up on the key points of a recorded conversation.
Sentiment analysis
Review AI-generated sentiment scores and analysis to help assess how a conversation went.
Provider consolidation
From PBX sprawl to one operating plane
Per-customer PBX instances multiply upgrades, backups, troubleshooting paths, and provisioning work. MiRTA PBX centralizes the management model while preserving tenant boundaries.
| Operating concern | Per-customer PBX estate | MiRTA PBX operating model |
|---|---|---|
| Provisioning | Different instances, configuration paths, and lifecycle tasks. | One multitenant management layer with database-backed configuration. |
| Customer separation | Isolation often depends on a separate VM or PBX for every customer. | Logical tenant separation within a provider-operated platform. |
| Capacity | Resources can become stranded across many small deployments. | Add licensed Asterisk nodes as the shared service requires them. |
| Operations | Monitoring, upgrades, and troubleshooting repeat across the estate. | Standardize the provider workflow and keep customer-specific policy where it belongs. |
Platform control
Keep control of brand, trunks, infrastructure, and margin
MiRTA PBX is designed for operators building a service, not for businesses buying another bundled seat plan.
- Your customer relationship Operate the service under your brand and define how each tenant is presented and supported.
- Your SIP strategy Keep the trunks, carriers, numbering, and routing approach that fit your network.
- Your deployment Run the platform on infrastructure sized for your operating and resilience requirements.
- Your unit economics License server capacity rather than paying a platform fee for every customer or extension.
Product evidence
Built around the work operators do every day
Tenant administration, routing, realtime status, call history, media, queues, and integrations live in one provider-facing interface.
Multitenant operations
Apply platform-wide standards while keeping configuration, dialplans, data, and permissions separated by tenant.
Realtime configuration
Use database-backed Asterisk configuration to reduce flat-file churn and support repeatable automation.
Single-node to clustered
Start with a focused deployment and add Asterisk nodes when capacity or resilience requirements justify it.
Transparent licensing
License capacity, not customer count
A MiRTA PBX server license is €200 per month and does not cap tenants, extensions, channels, DIDs, voicemail, or core features.
Technical review
Map MiRTA PBX to your current estate
Bring your current platform, customer scale, trunking approach, and HA requirements. Leave with a target topology, fit assessment, and practical pilot or migration step.