Once a deal is won, the relationship doesn't end — it shifts from selling to supporting. That's the job of the Customer Service module, built from three ideas that fit tightly together: the Case (one customer issue), the queue (where unassigned Cases wait), and the SLA (Service Level Agreement, the response-time promise).
This chapter covers all three at a conceptual level — no pricing or licensing detail, just how the pieces work together.
- A Case (also called an incident) tracks one issue from open to resolved
- A queue holds unassigned Cases until a qualified rep picks them up
- An SLA tracks a running timer: on track, at risk, or breached
- Organizations often run several queues side by side, split by team or issue type
Picture a busy deli counter
Picture a deli counter with a "take a number" machine. Customers arrive with all kinds of requests — a simple order, a complicated catering question, a complaint. Each pulls a numbered ticket the moment they arrive, and it waits in a holding area until a free staff member calls the next number. Nothing is lost; it's just waiting its turn.
Dynamics 365 CE's Customer Service module works the same way. Every request becomes a ticket (a Case), every ticket waits in a holding area (a queue), and the deli's implicit promise — "we'll get to you quickly" — becomes an explicit, tracked promise (an SLA).
The Case: one ticket, one issue
A Case — also called an incident, both terms used interchangeably in menus and documentation — represents one specific support issue, from open to resolved. A customer can have several Cases open at once if they've reported several unrelated problems; each is tracked and closed independently, the same way a deli wouldn't merge two regulars' orders onto one ticket.
A Case typically records:
- What the issue is
- Who reported it, and which product or Account it relates to
- Its current status (Active, On Hold, Resolved)
- A running history of notes, emails, and call summaries
Anyone who opens the record later — even a different rep — sees the full story without asking the customer to repeat themselves.
Queues: where unassigned work waits
A queue is a holding area for Cases that haven't been picked up yet — exactly like the deli's ticket bin. A new Case often lands in a queue first, visible to the whole team qualified to handle it, rather than landing directly on one rep's desk. A rep with capacity picks the next Case off the queue, the same way a free counter worker calls the next number.
Organizations often run several queues side by side — billing, technical, a specific product line — so a Case naturally lands in front of the team best equipped to handle it, rather than every request funneling through one overloaded general queue.
| Concept | Deli counter equivalent |
|---|---|
| Case | One customer's numbered order ticket |
| Queue | The bin of unclaimed tickets waiting for the next free staff member |
| SLA | The shop's promise of how long a reasonable wait should be |
SLAs: tracking the clock
An SLA, or Service Level Agreement, sets an expectation for how quickly a Case should be responded to or resolved — for example, "first response within one hour" or "resolved within two business days." Once an SLA applies, Dynamics 365 CE tracks a running timer, and a rep or manager can see at a glance whether it's:
- On track
- At risk of being missed
- Breached — already missed
This timer turns a vague intention ("we should get back to people quickly") into something visible and measurable — the same way a deli posting "average wait: 4 minutes" turns a promise into something a customer, and the staff, can actually watch and react to.