ServiceNow CSM Major Issue Management (CSM 9)

Every customer service team has a collective nightmare: a major data center goes down, and suddenly, a tidal wave of identical, panicked support tickets floods the queue.

If your agents handle these one by one, your resolution times will skyrocket, your team will burn out, and your customers will feel completely ignored. That is where ServiceNow’s Customer Service Management (CSM) Major Issue Management (MIM) and Targeted Communications modules come in.

Let’s break down exactly how these tools turn chaotic firefighting into a streamlined, automated science.

1. Major Issue Management: Fixing the Problem at Scale

The primary goal of Major Issue Management is simple: minimize service disruption across a wide audience. Instead of treating fifty identical customer complaints as separate problems, MIM allows you to link them together and manage them as a single unit.

The Lifecycle: From Single Case to Major Case

How does a standard glitch get elevated to a major incident? The workflow relies on a strict hierarchy to ensure only truly widespread issues get upgraded:

Step	Phase	Actor	Description / System Behavior
1	Detection & Proposal	Customer Service Agent	The agent notices a high-priority alert or multiple identical customer complaints, creates a standard case, and clicks Propose Major Case.
2	Review & Approval	Customer Service Manager / Major Issue Manager	A manager reviews the candidate. They must approve the proposal for it to proceed; if rejected, a mandatory reason is logged straight into the work notes.
3	The Major Case is Born	Automated System	The Major Case is officially established. If the original ticket contained customer data, it becomes a child of the new Major Case. If it didn’t, the original ticket itself scales up to become the Major Case.
4	Mass Automation	System / Resolution Sync	The manager attaches a Recipient List. The system automatically creates unique child cases for every affected customer, triggers notification emails, and links their resolution status directly to the parent case.

Important Guardrails: A ticket cannot become a Major Case candidate if it is already resolved, closed, cancelled, or if it is already tied to a different parent case. Furthermore, once those automated child cases are created, you cannot edit that specific recipient list.

2. Targeted Communications: Keeping Everyone in the Loop

Fixing the technical bug behind the scenes is only half the battle. You also need to control the narrative. Targeted Communications allows you to send time-sensitive, critical updates directly to external customers or internal employees.

These messages live inside Publication records and are authored by users with the Publications author or Publications admin roles.

• Where do people see them? External customers view them in the Customer/Consumer Service Portal, while internal employees see them in the Classic UI. They can also be pushed out via email.
• The Lifecycle: Publications are highly controlled. They go live at a specific time and automatically expire at a predefined date. The system even tracks exactly who received and viewed the message, giving you hard data on your reach.

How to Build and Publish an Update

1. Gather Your Audience: You can pull recipients into the publication manually, via an Excel import (.xlsx), through dynamic table filters, or using a script.
2. Compose the Content: You can write your update using standard HTML or Wiki formatting, and toggle on an optional email notification.
3. Go Live: Depending on your configuration, your publication will either use the Publication – Instant Publish workflow (default) or go through an approval loop using a modified version of Publication – Publish With Approval.

Major Case vs. Targeted Communications: What’s the Difference?

While they work hand-in-hand during a crisis, these two modules serve entirely different purposes and operate under different rules.

The biggest point of confusion usually lies in the Recipient List, but looking at the capabilities side-by-side makes the distinction clear:

Feature / Capability	Major Case Management (MIM)	Targeted Communications
Core Purpose	Tracking and resolving a technical disruption affecting multiple customers.	Sharing time-sensitive, critical information with a specific audience.
Primary Mechanism	Creates automated Child Cases linked to a Parent Case.	Creates Publication Records displayed on portals or sent via email.
Allowed Recipient Types	Accounts, Contacts, and Consumers.	Internal Users, Contacts, and Consumers.
The “Account” Rule	Exclusive to MIM. You can target whole business accounts.	Banned. You cannot target by “Account” type here.
System Update Cadence	Updates scale dynamically as the engineering/support team updates the case.	Recipient lists refresh automatically once a day via a scheduled job (though manual refresh is recommended to avoid delays).

Summary Takeaway

Think of Major Case Management as your operational shield: it structures your backend data, automates ticket creation, and ensures your engineers can focus on one fix that resolves hundreds of customer issues simultaneously.

Think of Targeted Communications as your megaphone: it ensures that while the engineers are working, your customers and internal staff aren’t left in the dark. Together, they turn an organizational crisis into a smooth, managed event.

---

Review

Core Concepts & System Rules

Feature / Concept	Major Issue Management (MIM)	Targeted Communications
Core Purpose	Tracks and resolves widespread technical disruptions affecting multiple customers.	Shares time-sensitive, critical information with an internal or external audience.
Primary Mechanism	Creates automated Child Cases linked to a Parent Case.	Creates Publication Records displayed on portals or sent via email.
Allowed Recipients	Accounts, Contacts, and Consumers.	Internal Users, Contacts, and Consumers.
The “Account” Rule	Allowed. You can target entire business accounts.	Banned. You cannot target by “Account” type.
Update Cadence	Scales dynamically as the support team updates the case.	Refreshes automatically once a day via a scheduled job (manual refresh recommended).
Workflow Lifecycle	Propose -> Review/Approve -> Major Case Creation -> Mass Automation.	Uses Instant Publish (default) or Publish With Approval workflows.
Formatting Options	Standard Case fields and resolution synchronization.	Authored in HTML or Wiki formatting.

Critical Guardrails

MIM Ticket Restrictions: A standard case cannot be proposed as a Major Case candidate if it is already in a Resolved, Closed, or Cancelled state, or if it is already tied to another parent case.

• Recipient Lists: Once automated child cases are created in MIM, you cannot edit that specific recipient list.
• Role Requirements: Targeted Communications publications must be authored by users holding the Publications author or Publications admin roles.
• Visibility: External customers view publications in the Customer/Consumer Service Portal, while internal employees see them in the Classic UI.
• Rejection Log: If a manager rejects a Major Case proposal, a mandatory reason must be logged directly into the work notes.