AI Copilot for ERPNext — Custom DocType Query, Work Order Reasoning, Helpdesk Automation

No. The copilot uses only stock ERPNext primitives — outgoing webhooks configured in the Webhook DocType, and the standard REST API with an API token you generate from your ERPNext User settings. Nothing is added to your ERPNext instance beyond configuration. This makes the copilot safe for Frappe Cloud (where you cannot install custom apps freely), safe for restricted production environments with strict change control, and immune to the app-collision issues that come from installing multiple third-party Frappe apps.

The copilot introspects the schema of every DocType in your instance during the initial connect and on every subsequent redeploy — including your Custom DocTypes and any Custom Fields you have added to stock DocTypes. Natural-language queries resolve against those Custom Fields the same way they resolve against stock fields — a question referencing your "priority_tier" custom field on Sales Invoice returns answers grounded in that field. This preserves the value of every ERPNext customisation your implementation partner built.

Every incoming HD Ticket is classified by DocType and topic against your own knowledge base (your Wiki, past resolved tickets, and any documentation you have wired in). The copilot produces a confidence score for its proposed first response. High-confidence responses (above a threshold you configure) can be sent autonomously, tagged as copilot-generated in the ticket Communication history. Lower-confidence responses are queued as drafts for your agents to review. The confidence threshold is per-DocType and per-support-team, so critical tickets (say, Sales Invoice disputes) can require human review even at high confidence, while routine ones (password resets, integration setup questions) can auto-respond.

Yes, Frappe Cloud is fully supported and is often the fastest install path because outbound HTTPS is pre-configured and there is no server-side firewall to open. All the copilot needs is an API token and the ability to configure outgoing webhooks — both of which Frappe Cloud allows without any restriction. Self-hosted deployments (v14 and v15) require your ERPNext server to be able to reach the Perimattic ingest endpoint over HTTPS on the standard port; most self-hosted setups already allow outbound HTTPS, so this typically requires no firewall change.

The scanner watches Sales Order → Material Request → Work Order → Delivery Note → Sales Invoice progression across your production cycle. When invoicing on a delivered order is lagging longer than your own historical median for the same item group, customer segment, or salesperson, the scanner flags the order with a proposed reason — for example, missing dispatch documentation, unresolved credit hold, disputed line item. This catches the "revenue leaked because nobody chased the invoice out the door" pattern that costs manufacturing shops a surprising percentage of their annual revenue.

Nothing by default — every autonomous action is off unless you explicitly enable it, per DocType and per user role. Common opt-in actions include: sending HD Ticket first responses above a confidence threshold, creating Purchase Orders from approved Material Requests using your standard supplier and terms, chasing Payment Entry against overdue Sales Invoices through WhatsApp on your aging schedule, and drafting Sales Invoices from Delivery Notes ready for a human sign-off. Every action writes a Communication record against the acted-on Doc so your audit trail is complete inside ERPNext itself.

ERPNext supports multi-company under one instance, and the copilot respects that boundary strictly. Each Company DocType binds to its own query scope, its own anomaly baseline, and its own autonomous-action permission set. A query about "our top vendors" resolves within the active company only; a cross-company question requires explicit permission for the querying user against every company in scope. This matches how Indian group structures actually operate — shared master data but separate books and separate compliance.

Early access. The copilot is running in pilot with ERPNext customers who volunteered from our existing ERPNext-WhatsApp and ERPNext-Razorpay base. Because ERPNext is highly customised per implementation, we prioritise pilot customers who have their Custom DocTypes documented and can spare an hour a week during the first month for feedback on how the copilot performs against their specific customisations. Contact us to join the pilot.