Section II – Functional Modules > Context Services > Overview Bottom of Page
| Genesys 8.0 SCXML Technical Reference
Object Model >

## Overview

The customer view is a data repository that provides real-time and historic customer-centric data to applications through an interface that allows the application users to make important business decisions, for example, it might allow you to determine whether a customer should be offered a given service.The Customer View system has a set of RESTful APIs to access the customer view data. An orchestration application will access these APIs through the `<fetch>` action. The following diagram shows an example of the kind of customer view–related processing that an orchestration application would use for processing a customer's session or service.

1. The first step that an orchestration application must carry out in order to use the customer view is to collect the appropriate information from the customer so as to be able to identify him or her so that we can query the customer view system to find the customer's customer view record.
2. Once you have found the customer's record, the orchestration application then needs to find if there are any active services associated with this customer.
3. If none are found, the orchestration application would create a new service.
4. Once the new service is created, the application must associate it with the customer profile.
5. At this point, the customer would then create or transition to a service state and the associated logic.
6. In this case, the service state is updating the customer's profile with [what?]
7. [Can steps 7 and 8 be filled in now???]

Section II – Functional Modules > Context Services > Overview Top of Page
| Genesys 8.0 SCXML Technical Reference
Object Model >