Marketing and growth-ops teams running on ERPNext quickly hit a wall. ERPNext core gives you Email Campaign, Newsletter and basic CRM lead tracking, but there is no true journey orchestration: no visual canvas, no branching if-then logic, no way to react to a Lead or Contact behavioral event and fan out across email, SMS and WhatsApp in the same flow. Marketers end up stitching together Notification rules, manual campaigns and spreadsheets, and the moment a journey needs "wait 3 days, check if they opened, then branch" it becomes unmaintainable. That gap is exactly where this build-to-order app lives.

ECOSIRE builds a dedicated Frappe app (its own module, not a fragile patch of ERPNext core) that adds a visual drag-and-drop journey canvas on top of ERPNext. The journey definition is stored in first-class DocTypes — a parent Marketing Journey with child Journey Step and Journey Branch tables — so every automation is versioned, permission-controlled and reportable like any other ERPNext record. Steps are typed: send-email, send-SMS, send-WhatsApp, wait/delay, condition/branch, update-field, and enroll-in-journey. Enrollment and step execution are driven by hooks.py doc events (after_insert, on_update, on_submit) on Lead, Contact, Customer or any DocType you choose, plus a scheduler_events cron worker that advances time-based waits and evaluates re-check conditions on the enqueued background job queue rather than blocking the web workers.

Technically, behavioral and time-based triggers are implemented with server scripts and controller hooks so that a field change or form event enrolls a contact and stamps a Journey Enrollment record tracking current step, next-run time and branch history. Branching conditions are evaluated with safe, sandboxed server-script logic (open-rate, click, field value, lead score threshold). Channel steps call pluggable delivery backends: ERPNext's native email queue for email, and configurable SMS and WhatsApp Business API gateways behind whitelisted methods so credentials live in a single Marketing Settings singleton. Lead scoring integrates by reading and writing a lead_score field, so a journey can gate a step on score or push a scored lead into a sales pipeline. Everything is exposed over the Frappe REST API and whitelisted methods, and access is governed by dedicated Role Profiles (Marketing Manager vs. Marketing Analyst) so analysts can build drafts but only managers can activate a live journey.

Because this is build-to-order, we start from your real ERPNext data model and channel providers rather than a one-size-fits-all download. After a short scoping call we confirm the journey types, trigger DocTypes, SMS/WhatsApp gateways and permission model, then build against Frappe/ERPNext v15 or v16 to match your instance. You receive the installable app source, we install and configure it on your staging site for UAT, and only promote to production once you have signed off. Typical delivery is one working week from confirmed scope, and you own the git repository and the running app at the end — no vendor lock-in and no per-contact SaaS metering.