Another approach that may be worth exploring is whether ServiceNow can perform the impact classification after the incident is created. I'm not a ServiceNow expert, so I can't confirm the specific capability, but many ITSM platforms support business rules, workflows, or similar logic that can evaluate the incident description and automatically set fields such as Impact, Priority, or Category.
If that capability exists in your ServiceNow environment, it could be another option to consider, especially if you prefer to keep incident classification logic within the ITSM platform rather than Genesys Cloud.
------------------------------
Phaneendra
Technical Solutions Consultant
------------------------------
Original Message:
Sent: 06-09-2026 06:19
From: Nikhil Mokhashi
Subject: Solution for Impact capture from Email Body.
Hello Sir,
Good day,
I am using Email Flow. I have done integration with service now.
I am using data action to create Incident on Service now.
Right now Impact variable i am passing to service now its 2 for all emails.
Just i want to automate this may because all time emails are not same, some time CX will tell on there email impact or many people have same issue.
on this situation what we can automate ?
Regards
------------------------------
Nikhil Mokhashi
Senior IT Telecom Engineer
------------------------------
Original Message:
Sent: 06-09-2026 05:48
From: Phaneendra Avatapalli
Subject: Solution for Impact capture from Email Body.
Hi Nikhil,
Could you share a little more about how the ServiceNow incident is being created today?
For example:
- Are you using an Inbound Email Flow?
- A Workflow?
- The native ServiceNow integration?
- A custom Data Action?
The answer will depend on where the Impact field is currently being set and whether the email content is available to your logic before the incident is created.
------------------------------
Phaneendra
Technical Solutions Consultant
------------------------------