Skip to content

Conversation

@RaviGaurav007
Copy link
Contributor

@RaviGaurav007 RaviGaurav007 commented Oct 14, 2025

PR Description:

This project introduces an Emotion-Aware Ticket Prioritizer for ServiceNow — an AI-inspired solution that detects user emotions (like frustration or satisfaction) from ticket text and automatically adjusts priority, routing, and responses. It combines sentiment analysis with workflow automation to make ServiceNow more empathetic, intelligent, and user-focused.

Pull Request Checklist

Overview

  • Put an x inside of the square brackets to check each item.
  • I have read and understood the CONTRIBUTING.md guidelines
  • My pull request has a descriptive title that accurately reflects the changes and the description has been filled in above.
  • I've included only files relevant to the changes described in the PR title and description
  • I've created a new branch in my forked repository for this contribution

Code Quality

  • My code is relevant to ServiceNow developers
  • My code snippets expand meaningfully on official ServiceNow documentation (if applicable)
  • I've disclosed use of ES2021 features (if applicable)
  • I've tested my code snippets in a ServiceNow environment (where possible)

Repository Structure Compliance

  • I've placed my code snippet(s) in one of the required top-level categories:
    • Core ServiceNow APIs/
    • Server-Side Components/
    • Client-Side Components/
    • Modern Development/
    • Integration/
    • Specialized Areas/
  • I've used appropriate sub-categories within the top-level categories
  • Each code snippet has its own folder with a descriptive name

Documentation

  • I've included a README.md file for each code snippet
  • The README.md includes:
    • Description of the code snippet functionality
    • Usage instructions or examples
    • Any prerequisites or dependencies
    • (Optional) Screenshots or diagrams if helpful

Restrictions

  • My PR does not include XML exports of ServiceNow records
  • My PR does not contain sensitive information (passwords, API keys, tokens)
  • My PR does not include changes that fall outside the described scope

whenever a user submits a ticket (Incident, HR Case, etc.), the system analyzes the tone of the message -like frustrated, urgent, calm, confused - and automatically adjusts the ticket priority, or routes it to a specific team (like “Empathy Response Desk”)
An AI-powered ServiceNow innovation that automatically analyzes the tone and emotion of user-submitted tickets (like incidents or HR cases) to detect frustration, urgency, or satisfaction.
This Readme introduces an Emotion-Aware Ticket Prioritizer for ServiceNow -an AI-inspired solution that detects user emotions (like frustration or satisfaction) from ticket text and automatically adjusts priority, routing, and responses. It combines sentiment analysis with workflow automation to make ServiceNow more empathetic, intelligent, and user-focused.
@am-shakeel am-shakeel self-assigned this Oct 14, 2025
The **Emotion-Aware Ticket Prioritizer** is an AI-powered ServiceNow solution that automatically analyzes the **tone and emotion** of user-submitted tickets (like Incidents or HR Cases).  
It dynamically adjusts **priority**, adds **contextual work notes**, and notifies the right team based on detected emotion -improving SLA compliance and customer satisfaction.
Copy link
Contributor

@am-shakeel am-shakeel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉 Congratulations on your first approved PR!
Thank you for your persistence and for finally aligning with the contribution guidelines. Your effort is appreciated & keep up the great work and continue contributing to the community!

@am-shakeel am-shakeel merged commit 07aac64 into ServiceNowDevProgram:main Oct 14, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants