Inside-sales and SDR teams running outbound on ERPNext quickly hit a wall. ERPNext's core CRM gives you Lead, Opportunity, ToDo tasks, and Email Templates, but it has no concept of a structured, timed sequence: a rep manually decides who to touch next, on which channel, and when. There is no native "Day 1 email, Day 3 call, Day 5 WhatsApp, Day 8 LinkedIn-style task" engine, no automatic exit when a prospect replies or books a meeting, and no send-time optimization. Reps drown in spreadsheets and manual reminders, follow-ups slip, and pipeline coverage becomes guesswork. ERPNext runs out of road exactly where modern outbound needs a cadence engine.

We build that engine as a proper Frappe app installed on your bench, with its own module and DocTypes rather than fragile customizations. A Sales Cadence DocType defines the sequence; a child table of Cadence Step rows holds each touch (channel, delay in days/hours, template, task subject, and business-hour constraints). Enrolling a Lead, Contact, or Opportunity creates a Cadence Enrollment record that tracks current step, next-action datetime, and status. A frappe.utils.background_jobs scheduler event (registered in hooks.py under scheduler_events) wakes on a cron cadence, finds due enrollments, and materializes the right action: an outbound Email via ERPNext's Email Queue/Notification layer with merge fields resolved from the linked document, or a ToDo/task assigned to the enrolled rep for call/WhatsApp/SMS touches, complete with reminders. WhatsApp and SMS dispatch route through your configured gateway (ERPNext's built-in SMS Settings, or a provider webhook we wire via a whitelisted method).

Reply and meeting detection drives auto-exit. Using hooks.py doc events on Communication (inbound email) and on Event/Opportunity (meeting booked or stage change), server scripts detect that a prospect has engaged and transition the enrollment to Replied or Meeting Booked, halting further touches so nobody gets an automated email after they've already answered. Everything is permission-aware: cadences, enrollments, and reporting respect ERPNext role profiles and user permissions, so an SDR only sees and acts on their own enrollments while managers get a workspace of cadence-level analytics. A whitelisted Frappe REST API (@frappe.whitelist() methods) and client scripts expose "Enroll in Cadence", "Pause", and "Skip Step" actions directly from the Lead/Opportunity form, and from list-view bulk actions for batch enrollment.

Because this is build-to-order, nothing ships until we agree on scope. We start with a scoping call to map your channels, gateways, cadence templates, business hours, and exit rules, then build against your Frappe/ERPNext version (v15 or v16). You get the installable source for your version, deployed and configured on your bench, validated on staging through UAT before it touches production, with training and a post-go-live support window. Typical delivery is one working week from confirmed scope.