Standard ERPNext can email a customer when a Sales Order is submitted, but it has no first-class way to text them, send a one-time passcode, or place and log a phone call. Teams end up copy-pasting numbers into the Twilio console, running SMS from a disconnected script, and logging calls by hand in a comment field — so delivery updates arrive late, OTP flows live outside the ERP, and call history never lands on the customer's record. ERPNext's native Notification DocType stops at email and system alerts; there is no built-in SMS provider abstraction wired to Twilio, no click-to-call, and no inbound-call capture.

ECOSIRE builds a proper Frappe app (installed with bench get-app / bench install-app) that treats Twilio as a first-class channel inside ERPNext. We add a Twilio Settings single DocType to hold your Account SID, Auth Token (stored as a Password field, never plaintext), messaging service SID and caller ID; an SMS Log and Call Log DocType to persist every outbound and inbound event with delivery status; and configurable SMS Template records with Jinja rendering against the source document. Outbound SMS fires from hooks.py doc_events (for example on_submit of Sales Order, Delivery Note or Payment Entry) or from Notification rules, so a text goes out the moment the document changes state. OTP/2FA generation and verification run through whitelisted server methods with rate limiting and short TTL, callable from both server scripts and client scripts.

On the voice side we wire Twilio Programmable Voice so users get a click-to-call button on Contact, Lead and Customer forms — a whitelisted method places the call via the Twilio REST API and dials the agent first, then the customer. Inbound calls hit a Twilio webhook we expose as a whitelisted endpoint; we match the caller ID against existing Contacts/Leads, create or update a Call Log, and (where you use ERPNext/Frappe CRM) link it to the relevant record and open a follow-up task. Delivery-status and call-status callbacks from Twilio update each log row asynchronously via the background job queue, and a scheduler event reconciles any events the webhook missed. If you run WhatsApp on the Twilio channel, we route templated WhatsApp messages through the same sending pipeline and settings.

Everything respects ERPNext's permission model: sending, viewing logs and managing Twilio Settings are gated behind dedicated roles and role profiles, so agents can click-to-call without seeing your credentials. All events are queryable through the standard Frappe REST API and report views, and the app is built and tested against ERPNext/Frappe v15 and v16.

Because this is build-to-order, nothing ships as an instant download. After a short scoping call we confirm exactly which document events trigger SMS, your OTP and call-routing rules, and your Twilio account details, then build against a staging copy of your ERPNext. Typical delivery is one working week from confirmed scope. You get the installable source for your version, UAT on staging, a go-live with rollback plan, and a support window afterward.