Difference between revisions of "ATC/Current/AdminGuide/About actions"

From Genesys Documentation
Jump to: navigation, search
(Published)
(Published)
Line 7: Line 7:
 
|TSSection={{TSSection
 
|TSSection={{TSSection
 
|sectionheading=Overview of actions and action maps
 
|sectionheading=Overview of actions and action maps
|description=An action represents the steps you want to take to engage with users or to further related business outcomes. {{MINTYDOCSPRODUCT}} supports numerous types of actions, including content offers, webhooks, and webchats. An action map defines when and how you use a particular action.
+
|description=An action represents the steps to take to engage with users or to further related business outcomes. {{MINTYDOCSPRODUCT}} supports numerous types of actions, including content offers, webhooks, web messaging, and webchats. An action map defines when and how you use a particular action.
|relatedarticles=*{{Link-AnywhereElse|product=ATC|version=Current|manual=AdminGuide|topic=About_actions_and_action_maps}}
+
|relatedarticles=*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=About_action_maps}}
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=About_action_maps}}
 
 
}}{{TSSection
 
}}{{TSSection
 
|sectionheading=Action Library
 
|sectionheading=Action Library
|description=Use the Action Library to build a collection of reusable actions, such as content offers and webhooks, for use with action maps.
+
|description=Use the Action Library to create a collection of reusable actions, such as content offers and webhooks, for use with action maps.
 
|relatedarticles=*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Action_library}}
 
|relatedarticles=*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Action_library}}
 
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Action_library|anchor=ViewActions|display text=View actions}}
 
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Action_library|anchor=ViewActions|display text=View actions}}
Line 33: Line 32:
 
}}{{TSSection
 
}}{{TSSection
 
|sectionheading=Webhooks
 
|sectionheading=Webhooks
|description=You build webhooks to integrate with external systems. Webhooks use Genesys Cloud integrations and data actions.
+
|description=Webhooks allow you to integrate with external systems. Webhooks use Genesys Cloud integrations and data actions.
 
|relatedarticles=*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Overview}}
 
|relatedarticles=*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Overview}}
 
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Overview|anchor=FeatureDescription|display text=Video}}
 
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Overview|anchor=FeatureDescription|display text=Video}}
Line 46: Line 45:
 
}}{{TSSection
 
}}{{TSSection
 
|sectionheading=Web chats
 
|sectionheading=Web chats
|description=Web chats present simple chats to users. To build them, you define what the offer text should be and what the chat window looks like.
+
|description=Web chats allow you to present a standalone chat window to visitors.
 
|relatedarticles=*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Chat_offers|anchor=AboutWebChats|display text=Overview}}
 
|relatedarticles=*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Chat_offers|anchor=AboutWebChats|display text=Overview}}
 
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Chat_offers|anchor=AboutWebChats|display text=Video}}
 
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Chat_offers|anchor=AboutWebChats|display text=Video}}
Line 55: Line 54:
 
}}{{TSSection
 
}}{{TSSection
 
|sectionheading=Architect flow actions
 
|sectionheading=Architect flow actions
|description=Use an Architect flow action to send journey context data information to third-party systems using a special type of Architect workflow. For example, you can send information about campaign contacts to Salesforce or another CRM.
+
|description=Architect flows allow you to send journey context data to third-party systems using a special type of Architect workflow. For example, you can send information about campaign contacts to Salesforce or another CRM.
  
 
<br />
 
<br />
Line 66: Line 65:
 
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=BuildArchFlows|anchor=RefIntegrity|display text=Update referential integrity constraints}}
 
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=BuildArchFlows|anchor=RefIntegrity|display text=Update referential integrity constraints}}
 
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Use_the_Architect_flow_with_an_action_map|anchor=ArchFlowActionMap|display text=Build an action map that uses the Architect flow action}}
 
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Use_the_Architect_flow_with_an_action_map|anchor=ArchFlowActionMap|display text=Build an action map that uses the Architect flow action}}
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Use_the_Architect_flow_with_an_action_map|anchor=MapContractFields|display text=Map contract fields}}
+
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Use_the_Architect_flow_with_an_action_map|anchor=OverrideDefaultVariables|display text=Override default variables}}
 
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Use_the_Architect_flow_with_an_action_map|anchor=GoLiveChecklist|display text=Go-live checklist}}
 
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Use_the_Architect_flow_with_an_action_map|anchor=GoLiveChecklist|display text=Go-live checklist}}
 
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=MonitorArchFlows}}
 
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=MonitorArchFlows}}
Line 73: Line 72:
 
}}{{TSSection
 
}}{{TSSection
 
|sectionheading=Monitor your actions
 
|sectionheading=Monitor your actions
|description=Use {{MINTYDOCSPRODUCT}}'s analytics to evaluate the effectiveness of your actions.
+
|description={{MINTYDOCSPRODUCT}}'s analytics allow you to evaluate the effectiveness of your actions.
 
|relatedarticles=*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Action_Map_Performance|display text=Action Map Performance report}}
 
|relatedarticles=*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Action_Map_Performance|display text=Action Map Performance report}}
 
}}
 
}}
 
}}
 
}}

Revision as of 13:51, November 4, 2020

An action represents the steps you want to take to engage with users or to further related business outcomes. Actions are organized in the Action Library.


Overview of actions and action maps

An action represents the steps to take to engage with users or to further related business outcomes. Genesys Predictive Engagement supports numerous types of actions, including content offers, webhooks, web messaging, and webchats. An action map defines when and how you use a particular action.

Action Library

Use the Action Library to create a collection of reusable actions, such as content offers and webhooks, for use with action maps.

Content offers

Content offers allow you to present highly customized, personalized offers to your website visitors.

Webhooks

Webhooks allow you to integrate with external systems. Webhooks use Genesys Cloud integrations and data actions.

Web chats

Web chats allow you to present a standalone chat window to visitors.

Monitor your actions

Genesys Predictive Engagement's analytics allow you to evaluate the effectiveness of your actions.

Comments or questions about this documentation? Contact us for support!