This is a module, not a standalone product.
Telephony is a module inside Riven Business, not a separate product. It rides on the Communications layer and works across every suite. Inbound SMS and calls become ERP records — contacts, CRM leads, activities, tickets. AI voice agents answer, route, and summarize. Usage meters to your tenant billing.
Or email [email protected]
The telephony ERP modules ship with every suite tenant. The infrastructure — phone numbers, Telnyx profiles, AI agents, billing — is provisioned when you opt in.
Send and receive SMS from tenant phone numbers. Inbound SMS creates ERP contact activities and CRM leads automatically.
Inbound and outbound voice calls with programmatic Call Control — dialing, transfers, IVR, and voicemail.
AI-powered agents that answer, route, and summarize calls. STT to LLM to TTS pipeline with transcripts in CRM.
Unified telephony surface combining voice and SMS on the same number, with shared contact history.
WhatsApp Business API integration with ERP contact sync for messaging customers on WhatsApp.
Synchronizes 3CX PBX call logs, contacts, and recordings with ERP CRM records. Call history in contact timeline.
Every inbound message or call is grounded in the same ERP context your suites already share. No separate phone vendor, no data island.
A customer texts or calls your tenant phone number. Telnyx routes the webhook to the sms-handler service.
The handler queries the ERP for the caller. Existing contacts get their activity timeline updated. New callers create a CRM lead.
For SMS, the on-prem Qwen model generates a contextual response. For voice, the STT to LLM to TTS pipeline handles the call.
The reply is sent via Telnyx. The conversation, AI response, and any CRM objects created are written to the ERP audit trail.
SMS, AI inference, and voice minutes are metered through Bifrost virtual keys and attributed to the tenant Stripe subscription.
Telephony does not live in a silo. Each event maps to a concrete ERP object, so your contact timeline, CRM pipeline, and billing ledger all stay in sync.
| Telephony event | ERP record | What happens |
|---|---|---|
| Inbound SMS | CRM Lead + Activity | New caller creates a lead. Existing contact gets an activity log entry with the message content and AI response. |
| Inbound call | CRM Activity + Ticket | Call creates an activity with duration and transcript. Voicemails create support tickets for follow-up. |
| AI voice agent conversation | CRM Activity + Transcript | Full transcript stored against the contact record. Call summary and action items posted to chatter. |
| Opt-out (STOP) | Contact Preferences | Consent withdrawal writes to the contact communication preferences. Future outreach is blocked automatically. |
| Usage (SMS, minutes, AI) | Tenant Billing Ledger | Metering receipts attributed to the tenant Bifrost virtual key. Wholesale cost and billable amount recorded. |
ERP modules ship at every tier. Infrastructure — phone numbers, AI agents, SMS credits — scales with your suite tier.
| Tier | Phone lines | SMS limit | AI voice | Includes |
|---|---|---|---|---|
| Free / Solo | 0 | — | — | ERP modules only |
| Starter | 1 | 100/mo | — | 1 phone line |
| Growth | 1 | 1,000/mo | AI voice agents | |
| Pro | 3 | 5,000/mo | WhatsApp + recording | |
| Platform | Unlimited | 50,000/mo | Unlimited |
Carrier compliance is a gate, not an afterthought. Telephony provisioning registers your 10DLC brand and campaign with The Campaign Registry before any outreach SMS is sent. Opt-out keywords (STOP, HELP, UNSUBSCRIBE) are handled automatically, consent records are stored in ERP contact preferences, and daily spend limits prevent runaway costs. Quiet hours are enforced by default.
One signup provisions your workspace. Opt into telephony from the console to get phone numbers, AI voice agents, and SMS — all grounded in your ERP.
Learn about Riven Business