Feature Requests

Allow organizations to connect their own telecom carrier or SIP provider to Ringee instead of using Ringee’s default carrier infrastructure. Teams should be able to keep their existing phone numbers, calling rates, carrier agreements, and SIP infrastructure while using Ringee for the calling experience, CRM integrations, AI agents, recordings, transcripts, and call management. Possible connection methods could include: SIP Trunk SIP credentials BYOC / custom carrier connection Existing PBX or VoIP infrastructure Multiple carriers per organization Ringee would act as the calling and AI layer while the customer’s carrier handles the underlying telephony. The goal: Use Ringee with the carrier you already have.

Allow developers to connect any external AI agent to Ringee and make or receive phone calls. The agent can run anywhere — on a laptop, server, Claude, ChatGPT, Gemini, a local LLM, or a custom application — while Ringee provides the telephony layer. Agents should be able to connect through API, WebSocket, SDK, CLI, or MCP and control calls in real time, including: Start and end calls Receive live transcripts and call events Send text responses that Ringee converts to speech Support interruption/barge-in Send DTMF and transfer calls Optionally stream raw audio for custom STT/TTS stacks The goal is simple: Bring your own agent. Ringee gives it a phone.

Allow teams to create an AI receptionist for inbound calls. The agent could answer incoming calls, understand what the caller needs, and route the call to the right person, team, or extension. It could also support traditional IVR options like “Press 1 for Sales, 2 for Support,” with the option to use AI instead of keypad menus. This would let Ringee handle both outbound calling and inbound call management from the same workspace.