Live Chat & Web Chat Widget for ERPNext

We build a proper Frappe app — its own module, DocTypes, and hooks.py wiring — that adds a real-time chat channel to ERPNext. A lightweight embeddable JavaScript widget drops onto any website (Frappe-hosted or external) with a single script tag. When a visitor opens a conversation, the widget streams to a whitelisted Frappe endpoint that creates a Chat Conversation DocType and, per your rules, spawns a Lead (sales intent) or an HD Ticket (support). Every message is stored as a child Chat Message row, and the visitor's page URL, referrer, UTM parameters, browser, and prior-visit context are captured on the conversation so an agent sees exactly what the person was looking at. Agents work the conversation from a Frappe Workspace/desk view built on the Frappe Realtime (Socket.IO) layer, so messages appear live without a refresh.

Routing and assignment are driven by ERPNext's own primitives. We use hooks.py doc events (after_insert, on_update) and server scripts to assign conversations by team, availability, round-robin, or page-based rules using Frappe's ToDo/assignment framework, and permissions are enforced through role profiles so support agents never see sales pipelines and vice versa. Agents get canned responses and slash-shortcut snippets stored as a Canned Response DocType (searchable, team-scoped, variable-interpolated). A scheduler event handles offline capture — after business hours the widget switches to a lead-capture form that still lands in ERPNext — and stale-conversation cleanup. Everything is reachable over the standard Frappe REST API and whitelisted methods, so you can extend it or wire it into other systems later.

Because this is build-to-order, nothing is a black box. After a short scoping call we confirm your exact routing rules, which DocType each conversation should create, your role profiles, and your branding, then build against your Frappe/ERPNext version (v15 or v16). Typical delivery is 2 to 4 weeks from confirmed scope. We install on a staging bench, run UAT with your team, then deploy to production with a rollback plan, and you receive the full git repository, technical documentation, a user guide, a training session, and a post-go-live support window. This is not an instant marketplace download — it is a scoped implementation you own outright.