Most Pakistani SMBs running ERPNext hit the same wall the moment they try to notify customers: ERPNext's stock SMS Settings assume a generic HTTP gateway with a fixed GET/POST shape, and its Notification DocType can fire an SMS or email but has no concept of a masked sender ID, a PTA-registered brand mask, per-gateway delivery receipts, or WhatsApp at all. So order confirmations, dispatch alerts, payment reminders, and login OTPs either go out from an unbranded long code that customers ignore, or don't go out from ERPNext at all — staff copy-paste numbers into a separate SMS panel and reconciliation dies. That is exactly the gap this build-to-order app closes.

ECOSIRE builds a proper Frappe app (ecosire_pk_messaging) installed into your own ERPNext bench, not a hosted middle-man. Inside it live real DocTypes: PK Gateway Account (credentials, base URL, masked sender ID, per-gateway rate caps), Message Template (Urdu/English bodies with Jinja placeholders, category, and a WhatsApp variant), and Message Log (every send with provider message-id, status, cost, and delivery-receipt timestamp). Adapters for the common local providers — the Telenor/Jazz aggregator style HTTP APIs plus WhatsApp Cloud API — are implemented behind one whitelisted dispatch method, so switching gateway is a config change on PK Gateway Account, not a code change. Because each account carries its own masked sender ID, your transactional traffic goes out under your registered brand mask while promotional traffic can route through a separate account to stay compliant.

Delivery is wired to ERPNext where the events actually happen. We hook hooks.py doc events — on_submit of Sales Order and Delivery Note, on_payment_authorized, and your custom triggers — through server scripts so an alert fires the instant a document changes state, rendering the right bilingual template automatically. OTP flows expose a whitelisted REST method (/api/method/ecosire_pk_messaging.api.send_otp) for your portal or mobile app, with generation, hashing, expiry, and attempt-throttling handled server-side. A scheduler event (scheduler_events in hooks.py) polls provider delivery-receipt endpoints and retries soft failures, while a client script on the Message Template form gives non-technical staff a live preview and test-send button. Everything respects ERPNext permissions: a dedicated role profile controls who can send campaigns versus who can only read Message Log, and promotional sends can require an approval workflow.

Because it is build-to-order, nothing here is a download you install blind. You start with a short scoping call, we confirm which local gateways you use, your masked sender IDs, the exact ERPNext events that should trigger alerts, and your Urdu/English template wording. ECOSIRE then builds your version against Frappe/ERPNext v15/v16, tests it on a staging bench, runs UAT with you, and installs it on your production instance with a rollback plan. Typical delivery is one working week from confirmed scope, and you receive the full source and git repository so nothing is locked to us.