Every request in one pipeline: a self-service portal with a knowledge base, a WhatsApp intake bot with agent replies and delivery ticks, social channels, and an agent desk with SLAs and a live dashboard.
How the module fits together end to end. Colours mark who acts: navy = staff/admin, cyan = external user, green = organisation, orange = the system.
A member of the public logs an issue and watches it to resolution — the desk works it under an SLA.
Every case with status, priority and SLA position; the dashboard (/ServiceDesk/Cases/Dashboard) shows the desk at a glance.

Categories, queues, SLAs and channel configuration.
The requester-facing side: browse knowledge articles (/Knowledge, /Article), submit a case, see your cases (/MyCases) and track one by reference (/Track).

Conversations arriving on the desk's WhatsApp number: the guided intake bot logs cases; agents read the thread and reply inside the 24-hour window. Outbound replies show delivery ticks (sent / delivered / read / failed).

Messages from connected social channels flow into the same case pipeline; configure at /ServiceDesk/Social/SocialSetup.
The assets the desk supports — servers, laptops, licences, printers, network gear — each as a configuration item with its type, status, criticality, owner and location. Cases can be linked to the item they are about, so an asset carries its own history.
The webhook validates a cryptographic signature; check Setup and that the provider's webhook URL matches the configured one exactly.
One tick sent, two delivered, blue read, red warning failed — reported by the provider's status callbacks.
Yes — /ServiceDesk/Portal/Track takes the case reference.