An insurance phone system provider turns its call data into a programmable API platform.
JAS Communications provides 3CX, a business phone system, to insurance brokerages across North America. 3CX stored call recordings and event data but offered no programmatic access and no AI capabilities. Devpro built the API layer on top of the 3CX database and a post-call AI pipeline that retrieves audio and processes it through Devpro's own services, delivering transcription, sentiment analysis, and automated summaries. A live analysis layer was added later via an SBC connection. The platform now processes 11.9 million API requests per month.
- Initial build
- 5 months · discovery to production
- Ongoing since
- 2023
- Region
- QC, Canada (serves North America)
- Scope
- REST API · webhooks · web portal · AI analytics
- Client type
- Telecom platform · insurance industry
"What sets Devpro apart is their ability to translate complex business needs into clean, scalable, and reliable solutions. They communicate clearly, deliver on timelines, and proactively flag opportunities to improve performance and usability, not just "build what's asked.""
President, JAS Communications
What Problem Was JAS Communications Trying to Solve?
JAS Communications provides 3CX, a business phone system, to insurance brokerages. 3CX stored call recordings and event data, but offered no API and no path for third-party tools to integrate. JAS had no way to give customers programmatic access to their own call data and no way to build AI capabilities on top of it.
- No API on the phone system. 3CX stored call records and audio, but provided no programmatic access. There was no export, no webhook, and no vendor roadmap to add one.
- No AI processing on call data. Call recordings sat in storage with no transcription, no sentiment analysis, and no automated summaries. Extracting insights required manual effort on every call.
- No integration pathway for partners. Partners and enterprise customers wanted to build on top of JAS's platform, but there was no authentication layer, no webhook system, and no defined API contract to integrate against.
What Did Devpro Build for JAS Communications?
Devpro built a REST API layer directly on the 3CX database, exposing call records, events, and system metadata to authenticated third parties. On top of that, Devpro built a post-call AI pipeline: audio is retrieved from the API and run through Devpro's own AI services to generate transcriptions, sentiment scores, summaries, and key points. A live analysis layer via an SBC connection was added later, enabling real-time transcription and call monitoring. Both capabilities are surfaced through a single API and a customer-facing analytics portal.
REST API over the phone system
A complete programmatic interface to JAS's call data (historical records, live events, and system metadata), built directly on top of the existing phone system database with no changes to the underlying vendor platform.
OAuth 2.0 and API key authentication
A full authentication system using OAuth 2.0 and JWT tokens that lets external platforms, enterprise customers, and partners securely connect to JAS's API with scoped credentials and access controls.
Webhook event system
Database-event-driven webhooks that push real-time call events (answered, transferred, ended, flagged) to any registered subscriber endpoint across the platform.
AI call analytics
Post-call AI pipeline built entirely by Devpro: audio is retrieved from the 3CX database via the API and run through Devpro's own AI services for transcription, sentiment scoring, automated summaries, and key points extraction. A live analysis layer via SBC was added in a later phase to support real-time call monitoring.
Web analytics portal
A browser-based interface giving JAS and its customers live and historical visibility into their call data, with reports, post-call transcription, sentiment scores, and (via the SBC layer) real-time call monitoring.
Role-based access control
Role-based access control with granular permission tiers for JAS administrators, brokerages, and individual users. Each user sees only the data scoped to their organization.
What Results Has JAS Communications Achieved with the API Platform?
API requests processed
Across all organizations on the platform
Platform uptime
Mission-critical reliability, measured across the past year
