Merge pull request LivePersonInc#1874 from LivePersonInc/co091322a

Add alt text to images in the Conversational Orchestrator docs

pages/Documents/ConversationalAI/ConversationOrchestrator/ConversationContextService/attributes.md

@@ -32,7 +32,7 @@ Conversation context attributes are those attributes of a conversation, such as
 * conversation.consumerId
 * conversation.groupId
 
-<img class="fancyimage" width="800" src="img/convorchestrator/co_ccs_convcontextattributes.png" alt="">
+<img class="fancyimage" width="800" src="img/convorchestrator/co_ccs_convcontextattributes.png" alt="The Conversation page where you can enable conversation attributes and copy conversation context attributes">
 
 #### Structured Data Entities (SDEs)
 
@@ -66,7 +66,7 @@ Personal info:
 * sde.visitorinfo.personalinfo.language
 * sde.visitorinfo.personalinfo.company
 
-<img class="fancyimage" width="800" src="img/convorchestrator/co_ccs_sdes.png" alt="">
+<img class="fancyimage" width="800" src="img/convorchestrator/co_ccs_sdes.png" alt="The Structured Data Entities page where you can enable the CCS to store SDE values and more">
 
 ### Custom attributes
 
@@ -81,12 +81,12 @@ Static variables are useful for storing constant data or lists that can be used
 1. Log in to Conversation Orchestrator using your Conversational Cloud credentials, and navigate to **Conversation Context Service → Custom**.
 2. Click the **Add New** button, and select "static."
 
-    <img class="fancyimage" width="400" src="img/convorchestrator/co_ccs_static.png" alt="">
+    <img class="fancyimage" width="400" src="img/convorchestrator/co_ccs_static.png" alt="Selecting ‘static’ as the type for a new attribute">
 
 3. Enter the name and the value of the new variable in the text input area.
 4. Click **Save**.
 
-    <img class="fancyimage" width="800" src="img/convorchestrator/co_ccs_staticvar.png" alt="">
+    <img class="fancyimage" width="800" src="img/convorchestrator/co_ccs_staticvar.png" alt="An example of a saved static variable">
 
 {: .important}
 When creating *custom* attributes in the Context Session Service, ensure that you are following naming conventions that avoid spaces in the name (use camel case, snake case, pascal case, etc.). While having an attribute name that contains spaces will not trigger an error message, you will be unable to properly access these attribute’s values from within the policies you will be creating.
@@ -104,10 +104,10 @@ Once you have created a function, you can now use that as an attribute in the Co
 1. Log in to Conversation Orchestrator using your Conversational Cloud credentials, and navigate to **Conversation Context Service → Custom**.
 2. Click the **Add New** button, and select "function."
 
-    <img class="fancyimage" width="400" src="img/convorchestrator/co_ccs_function.png" alt="">
+    <img class="fancyimage" width="400" src="img/convorchestrator/co_ccs_function.png" alt="Selecting ‘function’ as the type for a new attribute">
 
 3. Select the FaaS function using the user credentials that you created.
 
-    <img class="fancyimage" width="400" src="img/convorchestrator/co_ccs_faasfunction.png" alt="">
+    <img class="fancyimage" width="400" src="img/convorchestrator/co_ccs_faasfunction.png" alt="Selecting a FaaS function from the Function list">
 
 4. Click **Save**.

pages/Documents/ConversationalAI/ConversationOrchestrator/ConversationContextService/getting-started.md

@@ -21,7 +21,7 @@ Everything that is stored in the Conversation Context Service (CCS) consists of
 
 *Session properties* are those where the property belongs to one namespace and one session, and *namespace properties* are those where the property belongs to one namespace and does not belong to any session.
 
-<img width="400" src="img/convorchestrator/co_ccs_properties.png">
+<img width="400" src="img/convorchestrator/co_ccs_properties.png" alt="A diagram illustrating namespace and sessions properties, both within a namespace">
 
 Since properties cannot be moved to other namespaces or sessions, if you want to change the affiliation, you must delete the property and create a new one.
 

pages/Documents/ConversationalAI/ConversationOrchestrator/ConversationContextService/overview.md

@@ -46,15 +46,15 @@ CCS attributes can be used in a variety of ways to enhance the conversational ex
 
 * **Power contextual continuity between bots** - In this example, the intent and email is being saved into the CCS by one bot and is being retrieved by another bot to continue the conversation.
 
-  <img class="fancyimage" width="700" src="img/convorchestrator/co_ccs_usecase1.png" alt="">
+  <img class="fancyimage" width="700" src="img/convorchestrator/co_ccs_usecase1.png" alt="An example conversation with a consumer that illustrates use of the CCS to maintain contextual info as the conversation is transferred from one bot to another">
 
 * **Perform context-based dynamic routing at scale** - In this example, a concierge bot saves the intent into the CCS. The CCS links to an external CRM to get customer tier information. A Dynamic Routing policy then makes use of the intent and tier information to power a routing decision.
 
-  <img class="fancyimage" width="700" src="img/convorchestrator/co_ccs_usecase2.png" alt="">
+  <img class="fancyimage" width="700" src="img/convorchestrator/co_ccs_usecase2.png" alt="An example conversation with a consumer that illustrates use of the CCS to perform context-based, dynamic routing at scale">
 
 * **Perform human-bot tango** - In this example, bots continue to build context about the consumer and the context information can be exposed to human agents through an agent-facing widget.
 
-  <img class="fancyimage" width="700" src="img/convorchestrator/co_ccs_usecase3.png" alt="">
+  <img class="fancyimage" width="700" src="img/convorchestrator/co_ccs_usecase3.png" alt="An example conversation with a consumer that illustrates use of the CCS to maintain contextual info as the conversation is transferred from bot to human agent">
 
 ### How to use the Conversation Context Service
 

pages/Documents/ConversationalAI/ConversationOrchestrator/DynamicRouting/advanced-routing.md

@@ -31,11 +31,11 @@ The Expression Editor is only available to brands that are upgraded to Conversat
 
 **Launch the Expression Editor**: Open Conversion Orchestrator, and select **Manage Policies** under the Dynamic Routing module. To view the policy editor, select an existing policy, or click **Add Policy**. Switch to the **Write an expression** tab to view the expression-based editor.
 
-<img class="fancyimage" width="800" src="img/convorchestrator/co_dr_advrouting1.png" alt="">
+<img class="fancyimage" width="800" src="img/convorchestrator/co_dr_advrouting1.png" alt="The Write an expression tab in the expression editor">
 
 **Write expressions**: You can write expressions using logical operators, any SDEs, context variables or conversation attributes.
 
-<img class="fancyimage" width="800" src="img/convorchestrator/co_dr_advrouting2.png" alt="">
+<img class="fancyimage" width="800" src="img/convorchestrator/co_dr_advrouting2.png" alt="An example expression">
 
 The following operations are possible:
 
@@ -67,7 +67,7 @@ namespace.varP == (namespace.varX || namespace.varY)
 
 **Use custom variables and LivePerson Functions**: Add custom variables and LivePerson Functions to extend your use cases.
 
-<img class="fancyimage" width="800" src="img/convorchestrator/co_dr_advrouting3.png" alt="">
+<img class="fancyimage" width="800" src="img/convorchestrator/co_dr_advrouting3.png" alt="An example expression using custom variables">
 
 **Remember the following when writing expressions**
 
@@ -85,11 +85,11 @@ namespace.varP == (namespace.varX || namespace.varY)
 
 Use predefined templates to create date-based or time-based routing policies.
 
-<img class="fancyimage" width="800" src="img/convorchestrator/co_dr_advrouting4.png" alt="">
+<img class="fancyimage" width="800" src="img/convorchestrator/co_dr_advrouting4.png" alt="Using predefine templates to create a routing policy">
 
 Add the required template to the editor.
 
-<img class="fancyimage" width="800" src="img/convorchestrator/co_dr_advrouting5.png" alt="">
+<img class="fancyimage" width="800" src="img/convorchestrator/co_dr_advrouting5.png" alt="The template added to the policy">
 
 Update the template to create your rule.
 
@@ -135,7 +135,7 @@ Combine date and time to create policies:
 | --- | --- |
 | VIP customers during work hours on weekdays in the month of September in New York | orchestrator.phoneNumber in custom.VipList<br>and isDateRange('09/01/21', '09/30/21', ‘America/New_York')<br>and isTimeRange('09:00:00', '18:00:00', '‘America/New_York', ['MON','TUE','WED', 'THU','FRI'] )) |
 
-<img class="fancyimage" width="800" src="img/convorchestrator/co_dr_advrouting6.png" alt="">
+<img class="fancyimage" width="800" src="img/convorchestrator/co_dr_advrouting6.png" alt="An example expression using date and time with other attributes">
 
 ##### Use the right formats for days and time zones
 
@@ -147,13 +147,13 @@ Combine date and time to create policies:
 
 Use [policy logs](conversation-orchestrator-dynamic-routing-policy-logs-for-v2.html) to debug your policies.
 
-<img class="fancyimage" width="800" src="img/convorchestrator/co_dr_advrouting7.png" alt="">
+<img class="fancyimage" width="800" src="img/convorchestrator/co_dr_advrouting7.png" alt="Using the policy logs to debug policies">
 
 #### Nesting multiple expressions for more complex conditions
 
 Write nested statements to combine multiple logical conditions to arrive at routing decisions. Enclose every block with brackets “( )”.
 
-<img class="fancyimage" width="800" src="img/convorchestrator/co_dr_advrouting8.png" alt="">
+<img class="fancyimage" width="800" src="img/convorchestrator/co_dr_advrouting8.png" alt="An example of a complex condition that nests multiple expressions">
 
 ### Combine other products to power more complex routing use cases
 
@@ -167,7 +167,7 @@ Routing to a different skill if the primary skill is experiencing a high load. T
 **Solution:**
 This can be solved using a combination of [Dynamic Routing](conversation-orchestrator-dynamic-routing-overview.html), [Context Service](conversation-orchestrator-conversation-context-service-overview.html), [LivePerson Functions](liveperson-functions-overview.html) and the [Queue Health API](operational-realtime-api-methods-queue-health.html). A LivePerson Function can be configured to run every 2-5 mins and update the “average wait time” for every skill into the Context service. Dynamic routing policies can then be configured to check average wait time for every skill and fall over to a different skill as appropriate.
 
-<img width="800" src="img/convorchestrator/co_dr_advrouting9.png" alt="">
+<img width="800" src="img/convorchestrator/co_dr_advrouting9.png" alt="The architectural diagram illustrating the flow between the components involved">
 
 {: important}
 The above solution can be deployed relatively quickly. However, it does require a few hours of coding effort for the LivePerson function. This method cannot be used to check queue health in real time for every conversation, but we believe that checking the queue every 2-5 mins will help solve this specific use case. Most conversations live much beyond 2-5 mins and queue stats are unlikely to change significantly during this time frame.
@@ -182,7 +182,7 @@ This can be solved using [SDE](engagement-attributes-types-of-engagement-attribu
 
 While SDEs are captured directly for conversations originating from web-engagements, they have to be manually set when conversations originate on other channels such as whatsapp or mobile apps. For this use case a routing bot will check for the customers’s VIP status through a CRM (or relevant application) and then update the SDE value for VIP customers. LivePersons Queue prioritization updates queue priority in real time whenever the SDE is updated. Next SDE based routing policies can be configured on Dynamic Routing to route VIP customers to the appropriate skill.
 
-<img width="800" src="img/convorchestrator/co_dr_advrouting10.png" alt="">
+<img width="800" src="img/convorchestrator/co_dr_advrouting10.png" alt="The architectural diagram illustrating the flow between the components involved">
 
 #### Other scenarios