Kelvia Enterprise
AI voice connected to your PBX, locations, and operation.
For organizations that need real technical control: PBX/SIP with validated templates, dedicated rollout, tailored limits, and transfers without carrier or number migration.
Live operation
PBX / SIP control
SLA
Contract terms
SIP
Native PBX mode
4
PBX templates
Madrid HQ
Reception
CRM
Sequence
PBX routes the call
Asterisk / FreePBX first; 3CX, Yeastar, and Grandstream next
Kelvia answers over SIP
G.711 media stream into the realtime AI pipeline
Handoff stays internal
SIP REFER returns control to your phone system
Everything included in Enterprise
The complete platform, with tailored limits.
- AI profiles and routing across locations
- WhatsApp, voice & webchat from one platform
- Appointment booking & two-way calendar sync
- Real-time transcripts & analytics dashboard
- PBX / SIP trunk connectivity over VPN
- Staff XMPP contact management
- Scoped API keys & webhook integrations
- Consent, audit, and tenant-scoped controls
- Priority technical onboarding
Built for technical buying, not a pricing card.
SLA, security, deployment, and integrations are scoped around your stack. The important parts are agreed before production.
SLA
Self-host
SIP
Custom credit volumes
Your ops team sets the monthly ceiling. No overage surprises, no forced plan upgrades mid-campaign.
Dedicated account manager
One person who knows your stack, your SLA, and your team. Reachable — not queued.
Contract-specific SLA terms
Response windows and support commitments are agreed in the contract before production rollout.
Role-based access control
Give staff limited access, managers operational control, and headquarters the right multi-location visibility.
Self-managed deployment path
Run the core stack on your own servers with Docker Compose while AI, telephony, payments, and email stay as explicit provider integrations.
Custom integrations & API
Scoped API keys for read and write access. Connect your CRM, EHR, or ticketing system directly.
Staff XMPP contacts
Register staff JIDs, resend invitations, and route internal notifications through your own XMPP environment.
Profiles and routing for multi-team operations.
Use AI profiles when sales, support, bookings, languages, locations, or PBX paths need different behavior. Routing policies keep selection explicit by channel, intent, department, hours, and priority.
Transfers only go to verified people, departments, or PBX targets.
Kelvia can route a caller to sales, support, reception, a named staff member, or an internal PBX extension, but transfer targets are treated as controlled directory entries rather than free-form phone numbers.
Directory verification
Staff and department destinations must have a verified transfer target before the AI can offer them. Editing the destination clears verification.
PSTN fraud checks
Cloud phone transfers are classified against the tenant's verified country rules. Premium-rate, shared-cost, toll-free, special-service, international, satellite, unknown-cost, and cross-country targets are blocked.
SIP/PBX extensions
Enterprise SIP mode skips PSTN rate classification because the PBX owns the downstream route, but verified internal targets such as 211 or reception are still required.
Connect your phone system. Keep control.
Kelvia joins as an AI SIP endpoint through closed PBX templates. Your phone system keeps routing, extensions, PSTN carrier control, and internal transfer rules.
The AI answers over SIP and returns control to your PBX with REFER when a transfer happens.
Private VPN tunnel
Audio stays encrypted inside a dedicated point-to-point tunnel. Zero public internet exposure.
Internal extensions
Transfer to 'reception' or ext. 211 directly — no E.164 number or carrier change required.
Per-line auth
Each PBX has its own unique security key. No cross-tenant access possible.
Your infrastructure
Your PBX manages the PSTN. Kelvia plugs in as a SIP endpoint and handles the AI layer only.
No number migration
Keep your existing carrier and phone system. Kelvia adds to it, not replaces it.
SIP REFER transfers
The AI issues a SIP REFER on handoff. Your PBX handles the internal call route.
Separate XMPP path
Internal XMPP can use a dedicated WireGuard route with its own host, port, and health checks.