---
sourceDocument: Xanadu Account Lifecycle Events
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/acct-lifecycle-events

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Account Lifecycle Events

ft:clusterId :

    - actle

bundleId :

    - actle

workflow :

    - Customer and Industry


---

# Customer success tables

# Customer success tables {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

This section includes the customer success tables.
{#account-lifecycle-success-tables__table_q53_q3h_dcc__entry__2}

| Table | Description |
|-|-|
| Engagement | As a provider, delivering value to an enterprise customer \[account\] is not a 'one-time'' event, it is a journey with multiple activities, both internal and external during its lifecycle. |
| Success objective | Success objectives represents the value that the provider has sold to an enterprise customer. This value can be defined for one or more products. |
| Success outcome | Success outcomes are measurable components of success objectives. They can be monitored through analytics within the ServiceNow Platform or through a 3rd Party integration tools. |
| Success initiative | Success initiatives are a planned set of actions (workflows) that the provider and enterprise customer agree to take and complete on the customer's value realization journey. |
| Success case | Success cases are an unplanned set of actions a provider takes to support a customer engagement activity. |
| Success task | Success tasks are planned or unplanned actions that either the provider or enterprise customer must complete in support of a success initiative (planned) or a success case (unplanned). |
| Touchpoint | A touchpoint captures and supports conversations such as scheduling calls, sharing reports, and presentation material. |
| Internal play | Internal plays are planned or unplanned actions tied to the engagement lifecycle. Internal plays often require internal sub-tasks and follow a playbook with pre-defined activities. |
| Internal play task | Internal play tasks are actions that are created as result of a specific internal plays being created. These tasks must have a clear purpose and if possible, must be created through playbook automation \[automatic, optional, or conditional\]. |
| Risk signal and issue | Risk signals and issues are a way of recording and managing risks tied to an engagement or onboarding so that the provider can take appropriate actions. |
| Definition record | The ALE definition record is used to specify categories that can be used to launch success play workflows that can create records and trigger playbooks automatically. |
| Success launcher notifier | The success launcher notifier tracks the status of the success play. |
[ ]

{#account-lifecycle-success-tables__table_q53_q3h_dcc}