Skip to content
Tutorials Center
My learning

Topics

Lesson 17 of 36 ยท CRM Concepts

Customer Service and Support

Understand the CRM service module: cases and ticket life cycle, priorities and SLAs, queues and escalation, knowledge base, omnichannel support and metrics such as first response time, CSAT and NPS.

Selling is half the relationship. When something goes wrong after the sale, the customer meets the service side of the company, and the quality of that encounter decides whether they stay. The CRM service module (also called a helpdesk) records every request as a case or ticket, routes it, tracks the clock against promised response times and keeps the answers in a knowledge base so the next customer is helped faster.

This lesson covers the case life cycle, priorities and SLAs, queues and escalation, knowledge management and the metrics managers watch. Real service software cannot run on this site, so we model its logic in Python.

The case life cycle

flowchart LR
  A["Request arrives"] --> B["Case created"]
  B --> C["Assigned"]
  C --> D["In progress"]
  D --> E["Resolved"]
  E --> F["Customer survey"]
  E --> G["Closed"]
  D --> H["Escalated"]
  H --> D

A ticket moves from creation to resolution, sometimes via escalation.

A case typically holds: subject, description, customer (contact and account), channel (email, phone, chat, portal, social), priority, category, owner, status, timestamps, attachments and a threaded conversation. Linking it to the account means an agent sees open deals, past cases and purchased products without asking.

Channels and omnichannel

Customers use many channels. Omnichannel service keeps one history across them: a chat that continues by email stays one case. Common channels: email-to-case, web form or customer portal, live chat and messaging apps, phone with call logging, social media, and in-product help.

Service channels

Email Turns into a case
Chat Fast, real time
Phone Logged calls
Portal Self-service

One history across all channels

1 / 2

Priority and SLAs

A service level agreement (SLA) promises response and resolution times by priority (and perhaps by customer tier). The system starts a clock when the case is created and warns before a breach.

Python SLA deadlines by priority

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Real SLAs often count only business hours and pause while waiting for the customer; the calculation above is the simplest version.

Queues, assignment and escalation

Cases land in queues (by product, language, tier). Assignment can be manual pick-up, round-robin, skill-based or load-based. Escalation rules fire when a case ages or a customer is important: notify the team lead, raise priority, reassign to a specialist.

Python Escalation rule check

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Knowledge base

A knowledge base stores articles that answer common problems. Agents search it while working, link articles in replies and, when no article exists, create one. Published to a customer portal it enables self-service, which deflects cases. Good articles have a clear title, symptoms, cause, steps and a review date; unused or outdated ones are retired.

Automation and assistance

Modern service tools classify incoming email, suggest articles and draft replies, and bots handle simple requests. Still, rules must be reviewed: a wrong automatic answer is worse than a slow correct one, and customers need a clear path to a human.

Metrics

  • First response time (FRT) and time to resolution.
  • First contact resolution (FCR): share solved without follow-up.
  • Backlog: open cases and their age.
  • Reopen rate: quality of fixes.
  • CSAT (customer satisfaction, a survey after the case, often a 1-5 scale).
  • NPS (net promoter score, "how likely are you to recommend us?" on 0-10; promoters 9-10 minus detractors 0-6).
  • SLA compliance.
Python CSAT and NPS

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Connecting service to the rest

Service data feeds sales ("this account has three open critical cases, delay the upsell") and the ERP (returns, warranty claims, replacement shipments). Field service adds appointments, technicians and parts from the inventory module, a good example of CRM and ERP working together as covered in ERP vs CRM.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does an SLA define in a service module?

    An SLA promises how quickly cases will be answered and resolved.
  2. 2. What is omnichannel support?

    Omnichannel keeps context when customers switch channels.
  3. 3. NPS is calculated as

    Promoters (9-10) minus detractors (0-6), divided by all respondents.
  4. 4. A knowledge base mainly helps by

    Reusable articles speed up answers and deflect repeat cases.

Summary

  • A service case captures a request with channel, priority, owner and history.
  • SLAs, queues and escalation rules keep cases moving; breaches trigger alerts.
  • A knowledge base enables faster answers and customer self-service.
  • Track first response, resolution, FCR, backlog, CSAT and NPS.
  • Service data should feed sales and the ERP.

Next: Marketing Automation and Segmentation