Lead Scoring & Routing Engine

核心功能

Dedicated Frappe app and module with a `Lead Scoring Rule` DocType for weighted demographic conditions on industry, company size, source, country, and any existing custom field

`Lead Behavior Event` DocType accumulating points from tracked signals (email opens, page visits, form submits) ingested via a whitelisted `frappe.whitelist()` REST method

`hooks.py` doc events on `Lead`/`CRM Lead` (`validate`, `after_insert`, `on_update`) that recompute the score server-side, never in the browser

Server script recomputes `custom_lead_score` and derives an A/B/C/D grade against configurable threshold bands

`Lead Scoring Settings` singleton so ops tune weights, thresholds, and grade cut-offs with no code change or redeploy

Configurable `Lead Routing Rule` engine with round-robin, weighted round-robin, and territory/product-based strategies

Territory and product-interest mapping that resolves the correct owner or sales team from the lead's `territory`/country fields

Routing writes native Frappe `ToDo` assignments and sets `lead_owner`, integrating with existing Assignment Rules, notifications, and Kanban

Scheduler event (`scheduler_events` in `hooks.py`) sweeps stale, unworked, or unassigned hot leads on a configurable interval

Client script on the Lead form rendering a live score, grade badge, and next-best-action indicator for reps

Whitelisted REST endpoints to push behavioral events or re-trigger scoring from your website, marketing tool, or webhooks

Full audit trail: every scoring and routing decision logged with rule name, delta, and timestamp for sales-ops review

Role profiles and DocType permissions separating rule editors (ops) from reps who only see the scored outcome

Auto-prioritization: hot leads above a threshold jump the routing queue and can trigger notification or escalation to senior closers

按需定制，全程代劳

无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。

您下单

以一次性构建价格开始。我们在启动时与您共同确定范围。

我们构建与安装

ECOSIRE 在您的 ERPNext 上构建、配置并安装。

上线 + 支持

约 2–4 周内上线，并提供上线后的支持期。

关于此产品

High lead volume exposes a real gap in ERPNext CRM out of the box: the Lead DocType has no native scoring, and Assignment Rule gives you basic round-robin ToDo assignment but no concept of demographic fit, behavioral intent, score thresholds, or grade-based prioritization. Sales-ops teams end up bolting scoring logic into spreadsheets or leaving reps to cherry-pick leads, so hot inbound sits unworked while low-fit leads soak up capacity. When you try to encode "score the lead, grade it, then route hot A-grade leads to senior closers by territory" using only stock ERPNext configuration, you run out of road fast.

ECOSIRE builds a proper Frappe app — its own module, not a pile of loose customizations — that closes that gap. We add a Lead Scoring Rule DocType (weighted conditions on industry, company size, source, country, and any custom field you already capture) and a Lead Behavior Event model that accumulates points from tracked signals such as email opens, website visits, form submissions, or webhook pings via a whitelisted REST endpoint. A hooks.py doc event on Lead (and optionally CRM Lead on v16) recomputes the total score on validate/after_insert through a server script, writes back a numeric custom_lead_score and a derived grade (A/B/C/D against configurable thresholds), and stamps the scoring timestamp. Nothing is hard-coded — thresholds, weights, and grade bands live in a single Lead Scoring Settings singleton so your ops team tunes them without a redeploy.

Routing runs the moment a lead crosses a threshold. We ship a configurable Lead Routing Rule engine supporting three strategies: round-robin across an eligible sales pool, weighted round-robin (a senior rep can carry a 3:1 share), and territory/product-based assignment that maps the lead's territory, country, or product interest to a specific owner or team. Assignment writes a standard Frappe ToDo and sets lead_owner, so it plugs into the native Assignment Rule, notifications, and Kanban views you already use — reps see it in the same inbox, no new UI to learn. A scheduler event sweeps stale or unassigned hot leads on an interval as a safety net, and every scoring and routing decision is logged for audit. Client scripts surface the live score, grade, and next-best-action badge directly on the Lead form. Role profiles and permissions gate who can edit rules versus who only sees the outcome.

Because this is built for your ERPNext, it fits your fields, your territories, and your sales structure — and it targets the version you actually run (Frappe/ERPNext v15 or v16). It is not a Frappe Cloud Marketplace download; there is no instant install. After you request a quotation we run a short scoping call, confirm your scoring dimensions and routing strategy, then build, install on a staging bench, and hand over. Typical delivery is 2–4 weeks from confirmed scope, and you receive the installable source, a git repository, documentation, training, and a post-go-live support window.

你得到什么

Installable source code for the version we build, packaged as a proper Frappe app for your v15 or v16 bench

Installation and configuration on your staging bench, including `Lead Scoring Settings`, initial rules, and routing pools wired to your real territories

Technical documentation: DocType reference, hooks and server-script logic, REST endpoints, and scheduler jobs

End-user guide plus a live training session for sales-ops on tuning weights, thresholds, and routing rules

UAT on staging with your sample lead data, sign-off checklist, and a documented rollback plan before production

Post-go-live support window for bug fixes and configuration adjustments

Git repository handover with full commit history and branch/tag for the released version

Data-migration notes and re-scoring helper to backfill scores onto your existing lead pipeline

这是给谁的

Sales Operations Manager

Owns lead distribution fairness and pipeline hygiene. Needs auditable, rule-driven scoring and routing that replaces spreadsheet triage and manual reassignment, tunable without engineering tickets.

Head of Sales / Revenue Leader

Wants reps spending time on the highest-fit, highest-intent leads. Needs grade-based prioritization so A-grade inbound reaches senior closers fast and nothing hot sits idle.

ERPNext Administrator

Runs the bench and cares about maintainability. Needs a clean Frappe app with proper DocTypes, hooks, permissions, and a git repo — not scattered customizations that break on the next v15/v16 update.

Marketing Operations Lead

Feeds behavioral signals into the CRM. Needs whitelisted REST endpoints to push email/website engagement events so lead scores reflect real intent, not just form-fill demographics.

Lead Scoring & Routing Engine 如何比较

标准	伊科西尔	定制建造	竞争对手	ERPNext 原生
Lead scoring	Rule-based + behavioral, weighted, tunable via settings singleton	Whatever you build and maintain in-house	Fixed scoring model, limited to its own fields	No native lead scoring on the Lead DocType
Grades & thresholds	Configurable A/B/C/D bands, no redeploy to change	Possible but you design and code it	Often hard-coded or absent	Not available
Routing strategies	Round-robin, weighted, and territory/product-based	Build each strategy yourself	Usually round-robin only	Basic assignment via Assignment Rule, no weighting
Behavioral signals	Whitelisted REST endpoints feed `Lead Behavior Event`	You build the ingestion and storage	Rarely supported or add-on gated	None
Fit to your fields & territories	Built around your existing custom fields and territories	Fully bespoke by definition	Fit only where its schema overlaps yours	Generic, no scoring layer to fit
Auditability	Every scoring/routing decision logged with rule and delta	Only if you build logging	Varies, often opaque	No decision log
Ownership & handover	Source code + git repo handed over to you	You own it, and all the build effort	Licensed, no source, vendor-locked	Core code, not a scoring solution
Support & delivery	Scoped, built, installed, UAT'd, with a support window	Your team's time and roadmap	Self-install, community/ticket support	No delivery — you configure it yourself

关于Lead Scoring & Routing Engine的常见问题

How long does delivery take?

This is build-to-order. After you request a quotation we run a short scoping call to confirm your scoring dimensions and routing strategy, then build, install on staging, and hand over. Typical delivery is 2–4 weeks from confirmed scope, depending on how many rules, territories, and behavioral integrations you need.

Is this an instant download from the Frappe Marketplace?

No. It is not an existing marketplace app you install yourself. ECOSIRE builds it specifically for your ERPNext instance, installs it, and supports it. You receive the source code and git repository as part of handover.

Which ERPNext versions are supported?

We build against Frappe/ERPNext v15 or v16. We target the version you actually run in production so the app installs cleanly on your bench and survives standard updates. Tell us your version on the scoping call.

How does scoring actually work under the hood?

A `hooks.py` doc event on the Lead fires a server script that evaluates your `Lead Scoring Rule` records, sums weighted points from demographic conditions and accumulated `Lead Behavior Event` signals, then writes back `custom_lead_score` and a derived grade. Thresholds and weights live in a settings singleton so your team tunes them without a redeploy.

How are leads routed, and does it work with our existing assignments?

The routing engine supports round-robin, weighted round-robin, and territory/product-based assignment. It writes standard Frappe `ToDo` records and sets `lead_owner`, so it integrates with your existing Assignment Rules, notifications, and Kanban views — reps see leads in the same inbox they already use.

Can we feed in behavioral data from our website or marketing tools?

Yes. We expose whitelisted REST endpoints so your website, marketing automation, or webhooks can push events like email opens, page visits, and form submissions. Those events accumulate as `Lead Behavior Event` records and raise the lead's behavioral score in near real time.

What support and updates do we get after go-live?

Handover includes a post-go-live support window for bug fixes and configuration adjustments, plus full documentation and the git repository. Because you hold the source, your team or ours can extend it later. Ongoing enhancement or version-upgrade retainers are available separately.