1. Flag high-priority support tickets for escalation
| Ticket ID | Priority | Opened | Closed | Agent | CSAT |
| T001 | High | 2026-09-01 | 2026-09-02 | Alice | 5 |
| T002 | Low | 2026-09-02 | 2026-09-05 | Bob | 3 |
| T003 | Medium | 2026-09-03 | 2026-09-04 | Carol | 4 |
=IF(NE(B2,"Low"),"Escalate","Standard")
Result: Escalate, Standard, Escalate
NE(B2,"Low") returns TRUE for T001 (High≠Low) and T003 (Medium≠Low), triggering "Escalate". For T002, NE returns FALSE because Priority is exactly "Low", so it shows "Standard". This pattern routes tickets by priority level without using complex nested IFs.
2. Identify tickets handled by agents other than Alice
| Ticket ID | Priority | Opened | Closed | Agent | CSAT |
| T001 | High | 2026-09-01 | 2026-09-02 | Alice | 5 |
| T002 | Low | 2026-09-02 | 2026-09-05 | Bob | 3 |
| T003 | Medium | 2026-09-03 | 2026-09-04 | Alice | 4 |
| T004 | High | 2026-09-04 | 2026-09-06 | Carol | 2 |
=IF(NE(E2,"Alice"),"Other agent","Alice's ticket")
Result: Alice's ticket, Other agent, Alice's ticket, Other agent
For each row, NE compares the Agent to "Alice". When the agent IS Alice (T001, T003), NE returns FALSE and shows "Alice's ticket". When the agent differs (T002 Bob, T004 Carol), NE returns TRUE and shows "Other agent". This helps track workload distribution across your support team.
3. Find tickets that missed perfect customer satisfaction
| Ticket ID | Priority | Opened | Closed | Agent | CSAT |
| T001 | High | 2026-09-01 | 2026-09-02 | Alice | 5 |
| T002 | Low | 2026-09-02 | 2026-09-05 | Bob | 3 |
| T003 | Medium | 2026-09-03 | 2026-09-04 | Carol | 5 |
| T004 | High | 2026-09-04 | 2026-09-06 | Alice | 2 |
| T005 | Low | 2026-09-05 | 2026-09-07 | Carol | 4 |
=NE(F2,5)
Result: FALSE, TRUE, FALSE, TRUE, TRUE
NE(F2,5) returns FALSE only when CSAT is exactly 5 (T001, T003 get perfect scores). Every other CSAT—3, 2, 4—is not equal to 5, so NE returns TRUE. This flags underperforming tickets for coaching or follow-up investigations.