Genesys Cloud - Developer Community!

 View Only

Sign Up

  • 1.  Solution for Impact capture from Email Body.

    Posted 21 hours ago

    Hi Team.

    I have created one email flow that has integration with service now. 

    I able to create incident based on CX email. But i not getting impact capture from email body.

    Right now i am creating all ticket with same impact.

    My plan to automate that impact based on email body is there any way i can do that.

    Please let me know any idea it will help me lot.

    Regards

    Nikhil 


    #Architect

    ------------------------------
    Nikhil Mokhashi
    Senior IT Telecom Engineer
    ------------------------------


  • 2.  RE: Solution for Impact capture from Email Body.

    Posted 20 hours ago

    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
    ------------------------------



  • 3.  RE: Solution for Impact capture from Email Body.

    Posted 19 hours ago

    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
    ------------------------------



  • 4.  RE: Solution for Impact capture from Email Body.

    Posted 18 hours ago
    Edited by Phaneendra Avatapalli 18 hours ago

    Hi Nikhil,

    One option to consider is using a Data Table to maintain your keyword-to-impact mappings instead of hardcoding all of the logic in Decision actions.

    For example:

    • outage → Impact 1
    • critical → Impact 1
    • multiple users affected → Impact 2
    • password reset → Impact 3

    I haven't implemented this specific use case, but I have successfully used Data Tables in other solutions to maintain keyword mappings and drive flow logic. This can make the solution easier to maintain because new keywords can be added over time without redesigning the overall flow.

    The general approach would be:

    1. Inspect the email subject and/or body.
    2. Match keywords against your configured mappings.
    3. Determine the Impact value.
    4. Pass the Impact value to your ServiceNow Data Action instead of using a fixed value.

    This may be worth exploring if you expect the keyword list to grow over time.

    Hope this helps.



    ------------------------------
    Phaneendra
    Technical Solutions Consultant
    ------------------------------



  • 5.  RE: Solution for Impact capture from Email Body.

    Posted 18 hours ago

    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
    ------------------------------



  • 6.  RE: Solution for Impact capture from Email Body.

    Posted 18 hours ago

    Thank you sir let me look on it



    ------------------------------
    Nikhil Mokhashi
    Senior IT Telecom Engineer
    ------------------------------



  • 7.  RE: Solution for Impact capture from Email Body.

    Posted 16 hours ago

    Hi Nikhil,

    You can also use Email AI Intent feature to find the impact of the email. Define your Intents as the definition of impact and use 'Detect Intent' function to find the impact.



    ------------------------------
    Jyoti Sharma
    Senior Design Consultant
    ------------------------------



  • 8.  RE: Solution for Impact capture from Email Body.

    Posted 16 hours ago
    Edited by Nikhil Mokhashi 16 hours ago

    Hi Joyti,

    Good day,

    Already i am using intent to detect Incident or request. 
    As you know if i add 3 more intent to detect Impact 
    Impact --1 --low

    impact2--medium 

    impact3-- high

    But i did this challenge is flow only look incident it will not go other intent 

    If any suggestion let me know. if it not work i will go with Lambda 

    Regards



    ------------------------------
    Nikhil Mokhashi
    Senior IT Telecom Engineer
    ------------------------------



  • 9.  RE: Solution for Impact capture from Email Body.

    Posted 14 hours ago

    Hi Nikhil,

    I can see the problem now.. Few options that you can go with:

    1. Create multiple intents which is a mix of type (Incident/request) and Impact(Low/Medium/High) and accordingly assign values to be passed to ServiceNow. For eg - Define Intents as IncidentLow, IncidentMedium, IncidentHigh etc...The success rate would depend on how clearly you will be able to provide clarity in intent description.
    2. Use Intents for type classification and keyword search for impact.
    3. Use AWS Lambda like you suggested earlier.



    ------------------------------
    Jyoti Sharma
    Senior Design Consultant
    ------------------------------