One desk. Every channel. SLAs that actually fire.
Email, chat, WhatsApp, voice and social land as one conversation on one customer record. The triage agent classifies and drafts with the policy cited; the SLA clock escalates on its own; and the customer never repeats themselves because the channel changed.
24 minAnita Rao
1 h 12 minBilling desk
3 h 08 minService lead
ResolvedDigital support
Equipment unavailable
P1 · Plant supportPriority
00:24:18SLA remaining
Premium care · ActiveEntitlement
Customer message linkedWhatsApp report joined to the open email thread
09:36Entitlement verifiedPremium care covers asset AC-4407
09:38Evidence assembledAlarm image and controller log attached
09:41Customer response prepared, not sent
We have linked the alarm image and controller log to case SR-10482. Please keep the equipment isolated while the case owner reviews the cited restart and dispatch steps.
Reviewed by Anita Rao. Release remains with the case owner; the cited evidence and escalation path stay on SR-10482.
Service lead has acknowledged. Plant specialist is on standby for the next escalation gate.
Escalate to specialist →Prepared response cites KB-228, POL-41, and the covered asset.
Review response →Ask about this case
↑triage · P1 routedImpact, product area and skill route shown on SR-10482.
resolution-draft · evidence citedKB-228, POL-41 and asset entitlement stay attached.
Human checkpoint · Anita RaoEdit, approve or escalate; the decision remains replayable.
The customer sees continuity. The team sees the clock, the evidence and the owner.
The rows below are the ones on every service-desk evaluation sheet. What changes is who does the work between them, and whether the escalation you configured is the escalation that happens.
The issue stays one thread, even when the channel changes.
Every channel writes to one conversation on one customer record, so a WhatsApp thread and last month's call sit on the same timeline.
email · chat · WhatsApp · voice · socialThe SLA is an operating path, not a coloured timer.
SLA policies run on business calendars and pause states; breaches escalate up the real hierarchy, and the escalation is a workflow, not a notification.
business calendar · acknowledgement · re-escalationThe answer arrives prepared; the case owner still decides.
Drafts quote the article and the policy clause they used; when an answer is missing, the gap becomes a knowledge task with an owner.
cited knowledge · named owner · retained trailNothing important disappears between the queue and the reply.
The live case connects customer context, entitlement, the SLA path, cited knowledge and the named human decision. The graphic above is not a dashboard collage; it is this same record moving through the work.
“list every ticket breaching SLA in the south region and who it escalated to”Illustrative case · Aster Components · owner Anita Rao
WhatsApp report joined to the open email thread
Production stopped · Dispatch gate: owner approval
KB-228 · POL-41 · Asset AC-4407
Edit, approve, or escalate; the decision and cited evidence remain on the case.
What changes
Everything a helpdesk does, with the follow-through built in.
The familiar service-desk checklist remains. The operating difference is visible in the work between intake, escalation and resolution.
Omni-channel intake
Channels as separate inboxes, stitched by an email address.
Every channel writes to one conversation on one customer record, so a WhatsApp thread and last month's call sit on the same timeline.
Triage & assignment
Keyword rules and a queue someone watches.
The triage agent classifies intent, urgency and product area, then routes by skill and load: with its classification shown and correctable.
SLA management
A timer, and an escalation email that goes to a shared mailbox.
SLA policies run on business calendars and pause states; breaches escalate up the real hierarchy, and the escalation is a workflow, not a notification.
Knowledge & self-serve
An article library that drifts from the product.
Drafts quote the article and the policy clause they used; when an answer is missing, the gap becomes a knowledge task with an owner.
Field & parts escalation
A second system, and a phone call to dispatch.
A ticket raises a visit or a parts request against the same record, so warranty, stock and technician availability are checked before the promise is made.
CSAT & quality
A survey score, disconnected from the cause.
CSAT lands back on the ticket, the agent and the root cause, so quality review starts from the conversation itself: replayable end to end.
The reply is one step. The resolution record holds everything behind it.
Conversation, entitlement, evidence, knowledge and the escalation path stay together while the case owner decides what leaves the desk.
Use the workspace tabs, then record the case-owner review.Equipment unavailable
Diagnosis in progressWhatsApp + email linked
Customer message linkedWhatsApp report joined to the open email thread
09:36Entitlement verifiedPremium care covers asset AC-4407
09:38Evidence assembledAlarm image and controller log attached
09:41Escalation acknowledgedService lead joined the response path
09:48Attached to SR-10482 at 09:41.
Asset AC-4407 in scope
Product and symptom context match
Entitlement and approval gate cited
Case ownerAnita RaoInvestigating
09:42Service leadKabir SenAcknowledged
09:48Plant specialistR. MenonOn standby
Due 10:06SLA-watch · next gate preparedCase-owner review retainedPlant specialist standby remains visible; no automatic dispatch.Anita Rao remains responsible for release or escalation.
A complaint that moves to resolution, or escalates before the SLA breaks.
Every contribution stays legible: what arrived, what the agent classified or prepared, which policy ran, and where human authority entered.
Message inWHATSAPP · EMAIL · VOICE
↓Triage agentINTENT · URGENCY · ROUTE
↓In SLA?CALENDAR · PRIORITY
↓Service agentREVIEWS THE DRAFT
↓Resolve or dispatchANSWER · VISIT · PART
↓ClosedCSAT · CAUSE PINNED
The desk, as it arrives.
Generated with your hierarchy, your business calendars and your service catalogue in place. Each module stays connected to the conversation, entitlement, escalation and resolution trail.
Unified conversation
One thread per customer issue across channels, with agent collision detection, private notes and full history on the account.
thread · collision · historyCustomer portal
Branded self-serve for ticket raising, status, approvals and document exchange: the same portal partners and clients use elsewhere.
brand studio · ssoSLA & business calendar
First-response and resolution targets per priority, product and contract, on working calendars with holiday sets and pause states.
first response · pause · breachEscalation matrix
Time-based and event-based escalation up your real reporting hierarchy, with acknowledgement tracked and re-escalation on silence.
hierarchy · ack · re-escalateContracts & entitlement
AMC, warranty and support-plan entitlement checked when a ticket opens, so out-of-scope work is priced rather than absorbed.
amc · warranty · scopeKnowledge base
Versioned articles with review dates and owners, surfaced to agents in context and to customers in the portal.
version · review dateProblem & recurrence
Linked tickets roll up to a problem record with a cause, an owner and a fix, so the tenth report of the same fault is visible as one.
link · cause · fix ownerQuality & CSAT
Survey triggers per closure type, scorecards for conversation review, and a quality queue built from the low scores.
csat · scorecard · review
Bring one queue. Leave with its SLA policy running.
A 90-minute working session: your ticket types, SLA matrix and escalation hierarchy drafted as an FRS, approved, and generated to a staging tenant with the channels wired.
The desk is meta on the platform: the same customer record the CRM uses, durable execution under every SLA clock, and agents scoped by the same RBAC, so an escalation cannot reach a record its recipient may not see.