Automation
WhatsApp Bot ↔ ManageEngine ServiceDesk Plus
A WhatsApp chatbot wired into ManageEngine ServiceDesk Plus that lets employees raise, track, and update IT tickets from the messaging app they already use — with n8n orchestrating the conversation.
FIG. 01 — SYSTEM FLOW
Constraint in → contract out. Every integration lands in a single system of record.
01
Problem
IT tickets lived in ServiceDesk Plus, but employees lived in WhatsApp. Raising a ticket meant opening a portal nobody wanted to open, so issues arrived as unstructured messages to whoever in IT happened to be online. Tickets went unlogged, priorities were guessed, and response time depended on who got the message.
02
Architecture
A WhatsApp conversational layer built on the WhatsApp Business API, orchestrated by n8n workflows that translate natural chat into structured ServiceDesk Plus tickets — and ServiceDesk events back into WhatsApp updates. The bot handles ticket creation with guided triage, status lookups, and updates; n8n manages the conversation state, retry logic, and the mapping between chat sessions and ticket records. ServiceDesk Plus remains the system of record; WhatsApp is the interface employees actually want.
03
Trade-offs
Conversational input is messy, so the bot guides rather than guesses: structured options with free-text fallback, always landing on a well-formed ticket. n8n was chosen for the orchestration layer deliberately — it gives observability and error handling out of the box, which matters when a failed workflow means a lost ticket. The trade-off is that every conversational edge case has to be designed, not discovered.
04
Impact
Ticket creation moved to where employees already are, so issues get logged instead of lost in chat threads. Triage became structured from the first message, response times improved, and the IT team works from ServiceDesk Plus with complete, traceable tickets.