Your people live in Slack or Microsoft Teams all day, but ERPNext HR lives behind a login they open twice a month. So leave applications sit unfiled, check-ins get skipped, and managers only notice a pending Leave Application when payroll asks. ERPNext core ships solid HR DocTypes — Leave Application, Employee Checkin, Attendance, Expense Claim — and even email notifications, but it has no first-class Slack or Teams presence: no slash commands, no interactive approval buttons, no way for a manager to approve from a mobile notification. The notification doctype can push to a webhook, but that is a one-way fire-and-forget message, not a conversation. Bridging that last mile with off-the-shelf iPaaS glue ends in brittle Zapier chains that break every time your leave workflow changes.

We build a proper Frappe app — its own module, DocTypes, hooks.py doc events, and whitelisted API methods — that turns your existing ERPNext HR data into a two-way chat assistant. On the inbound side, Slack slash commands and Teams message-extension actions post to signed, whitelisted endpoints (@frappe.whitelist()), which we verify (Slack signing secret / Teams JWT) before creating the matching ERPNext document under the correct employee's permissions and role profile. /leave 2026-08-10 2026-08-12 Annual creates a real Leave Application linked to the requester's Employee record; /checkin writes an Employee Checkin with the chat-reported timestamp and optional geolocation. Interactive approve/reject buttons call back into ERPNext to run the standard workflow transition, so the audit trail, leave-ledger entries, and balances stay 100% native — the bot never becomes a shadow system of record.

On the outbound side we wire hooks.py doc_events and Frappe scheduler_events to push the right message to the right person. A new Leave Application in the Open state DMs the approving manager with inline buttons; a submitted leave notifies the employee's channel. Scheduled jobs fan out the daily/weekly digests: pending-approval reminders to managers, birthday and work-anniversary announcements to a team channel, upcoming public-holiday notices from the Holiday List, payslip-ready pings after a Salary Slip is submitted, and review-due nudges from the appraisal cycle. Workspace/channel routing, message templates, and quiet-hours are all configurable through a Chat HR Settings single DocType plus per-event mapping — no code edits to change who gets what.

Everything runs on your Frappe bench against Frappe/ERPNext v15 or v16, respecting your existing permissions: the bot can only do what the linked ERPNext user is already allowed to do, and unmapped Slack/Teams identities are refused rather than silently escalated. Client scripts add a small "Notify in chat" affordance where it helps inside the Desk, but the heavy lifting is server-side and testable.

Because this is build-to-order, we start from your actual leave types, approval hierarchy, and which platform (Slack, Teams, or both) you run. After a short scoping call we confirm the command set, notification matrix, and channel routing in writing, then build, test on a staging bench, and hand over. Typical delivery is one working week from confirmed scope. You receive the installable app source for your version, install and configuration on your environment, technical and end-user documentation, a training session, and a post-go-live support window — not a marketplace download you have to wire up yourself.