Aircall / RingCentral / Knowlarity Telephony Connector for ERPNext

We build a proper Frappe app — its own installable module with hooks.py, custom DocTypes, and a clean namespace — that sits inside your ERPNext site rather than bolting on a fragile external middleware. Outbound click-to-call is a client script button on Lead, Contact, Customer and Opportunity that calls a whitelisted server method (@frappe.whitelist()); that method authenticates to your provider's REST API (Aircall Public API, RingCentral Call Control, Knowlarity or Dialpad) and rings the agent's registered device or softphone. Inbound calls hit a provider webhook that we expose as a whitelisted endpoint; a hooks.py doc event and frappe.publish_realtime push a screen-pop to the agent's browser via the Frappe websocket, matching the caller's number against existing contacts and opening the right record before they answer.

Every call — inbound or outbound, connected or missed — is written to a Call Log / VoIP Call DocType linked back to the originating CRM document, with direction, duration, agent, disposition and a free-text notes field the rep fills during the call. Recordings and voicemail are fetched from the provider (either pushed on the webhook or pulled by a scheduled scheduler_events job) and attached as File records against the call, so the audio lives beside the contact in ERPNext. Provider credentials are stored in a Telephony Settings single DocType with per-agent number mapping and role-profile permissions, so agents only see and act on their own extensions. We target Frappe/ERPNext v15 and v16, follow Frappe app conventions, and keep the adapters modular so a second provider can be added later without a rewrite.

Because this is build-to-order, nothing ships until we agree what "done" means. We start with a short scoping call to confirm your provider(s), which DocTypes need click-to-call, your inbound routing, and how you want dispositions and recordings handled. We then build against a dev bench, deliver on a staging site for UAT, and only cut over to production once you sign off — typically 2 to 4 weeks from confirmed scope, depending on how many providers and call-flows are in play. You receive the full source, a git repo handover, and a post-go-live support window, so this is your app on your bench, not a black box you rent.