Customer Review & Reputation Management

ECOSIRE builds a proper Frappe app that turns those transactions into a review pipeline. We add a Review Request DocType linked to the source document and customer, and a hooks.py doc_events handler (on_submit / on_update_after_submit) that spawns a request when the trigger document reaches a state you define — invoice submitted, delivery completed, ticket closed. A configurable scheduler_events job sends the request after a delay you set (for example 24 hours post-delivery) over the channel each customer prefers: WhatsApp Business API, SMS gateway, or ERPNext's native email queue, all driven by a Review Template DocType so wording, timing, and channel priority stay editable by your team without code.

The interception flow is the core of the design. Instead of pointing every customer straight at Google, the request first asks a simple 1-to-5 rating captured on a lightweight Frappe web form (a whitelisted @frappe.whitelist(allow_guest=True) endpoint writing back to the Review Request). High raters are routed onward to your public Google or Facebook review link; low raters are diverted into a private Feedback Case DocType that opens an internal ToDo / assignment for your team to resolve — so problems land in ERPNext, not on your public profile. Server-side sentiment tagging classifies incoming text and stores a sentiment field you can group and filter in a Frappe report.

On the aggregation side we build scheduled connectors that pull your published Google Business Profile and Facebook Page reviews into an External Review DocType via the respective platform APIs, deduplicated on external id, so every public review — its rating, author, text, and detected sentiment — is searchable inside ERPNext with a dashboard of rating trend, response rate, and channel breakdown. Role profiles and permissions keep private feedback restricted while letting front-line staff act on assignments.

Because this is build-to-order, you are not downloading a fixed marketplace app. We start from a scoping call, confirm which trigger documents, channels, and platforms you use, and build your version against ERPNext / Frappe v15 or v16. Typical delivery is 2 to 4 weeks from confirmed scope. You receive the installable source, UAT on a staging bench, and the git repository — details below.