If your team runs sales and support on WATI but everything of record lives in ERPNext, you spend the day copying between two tabs. A customer messages on WhatsApp through WATI, but their Contact and Customer history sits in ERPNext; an order ships, but nobody fires the "your order is on the way" template; a prospect replies to a broadcast, and that intent never becomes a Lead. ERPNext core has notifications and the odd webhook, but it has no native concept of a WATI session, template, or broadcast list — so the two systems stay stitched together by humans, and the seams show as missed messages and stale records.

The WATI Connector is a proper Frappe app (its own module, DocTypes, and hooks.py) that ECOSIRE builds and installs onto your bench, running natively on ERPNext v15/v16. On the ERPNext side we add configuration DocTypes — a single WATI Settings (Single) DocType holding the API endpoint and access token, plus mapping DocTypes for template-to-DocType-event bindings and broadcast-list membership. Outbound flows hang off hooks.py doc events (on_submit, on_update, after_insert): when a Sales Order or Sales Invoice reaches the right state, a background job (enqueued via frappe.enqueue, never blocking the user's save) calls the WATI API to send the mapped approved template with field-level parameter mapping from the source document. Inbound flows arrive on a whitelisted method (@frappe.whitelist(allow_guest=True)) registered as your WATI webhook; we verify the payload, upsert the Contact, thread the message onto the linked record, and — per your rules — create a Lead or a HD Ticket and route it. A daily scheduler_events job reconciles contacts and broadcast-list membership so the two directories don't drift.

Everything is driven by your data and your permission model. Template-to-event mappings, cooldowns, and routing live in DocTypes so your admins tune behavior without a code change; server scripts and client scripts we author cover the org-specific logic; and a dedicated WATI Integration role profile scopes who can edit settings, view message logs, and trigger manual sends. Sync state and every API call are logged to a WATI Message Log DocType with retry and idempotency keys, so a failed WATI call is visible and replayable rather than silently lost. Where you already have custom fields on Customer or Sales Order, we map to them rather than duplicating.

Because this is build-to-order, nothing ships until we agree on scope. We start with a short scoping call, confirm which DocTypes and events drive messages, which templates are already approved in your WATI account, and how inbound replies should route. You get your own versioned build of the app installed on a staging bench first, UAT against real documents, then a scheduled production go-live with a rollback plan and the git repository handed to you. Typical delivery is one working week from confirmed scope, depending on how many event triggers and routing rules are in play.