---
sourceDocument: Australia Customer Success Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/acct-lifecycle-events

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Customer Success Management

ft:clusterId :

    - actle

bundleId :

    - actle

workflow :

    - Customer and Industry


---

# Sample risk definitions

# Sample risk definitions {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

These are sample risk definitions available with the base system and can configured based on your requirements.

## Drop in NPS health {#account-lifecycle-risk-demo-data__section_nwp_jzn_zdc}

This is a metric based risk definition and generates a risk signal if the NPS score falls below a specified threshold. In this case, if the Daily collection of NPS metric score falls below 30, a risk signal is generated.
Additionally, override conditions with different threshold values and ranking that can impact specific engagements are defined.  

<br />

## SLA achievement in less than 90% {#account-lifecycle-risk-demo-data__section_nyt_y14_zdc}

This is a metric based risk definition and generates a risk signal if the SLA achievement score falls below a specified threshold. In this case, if the Daily collection of % achieved incident SLA metric falls below 90, a risk
signal is generated. An override condition with a different threshold value that can impact specific engagements has been defined. Additionally, a filter condition has been defined in the Applicable engagements field. This filter
condition is applied along with the override condition when the risk signal is generated.  

<br />

Hinweis:  
For metric based definitions, the data source and the context engine mapping must be defined. See [Data Context Engine](https://servicenow-prod.fluidtopics.net/y5PLBXWzvitoRxO0iwWvfg "The Data Context Engine breaks down silos by aggregating data from multiple sources—both internal and external—collecting it in one place to enable data-driven, actionable decisions.") for details.

## Missing renewal date in contract {#account-lifecycle-risk-demo-data__section_k4j_jb4_zdc}

This is a table based risk definition and generates a risk signal if the contract renewal date are missing. In this case, the Source table is the Contract table. This table must be mapped to the Engagement table. See [Configure the Context Engine Mapper](https://servicenow-prod.fluidtopics.net/shYcwsGhR8uKShje8H~RCw "After you have defined the data source, use the Context Engine Mapper to specify the record in the context table for which it is applicable.") for details. If the renewal start and end dates are missing in the Contract table, a risk signal is generated.  

<br />