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

From Genesys Documentation
Jump to: navigation, search
(Published)
(Published)
Line 51: Line 51:
 
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Chat_offers|anchor=ChatWindow|display text=Chat window}}
 
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Chat_offers|anchor=ChatWindow|display text=Chat window}}
 
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Chat_offers|anchor=WCMonitor|display text=Monitor a web chat's performance}}
 
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Chat_offers|anchor=WCMonitor|display text=Monitor a web chat's performance}}
 +
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Chat_offers|anchor=ExWebChatMetrics|display text=Progression of web chat metrics}}
 +
}}{{TSSection
 +
|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.
 +
 +
<br />
 +
|relatedarticles=*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=OverviewArchFlows|display text=Overview of Architect flow actions}}
 +
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=ScenarioArchFlows|display text = Salesforce lead creation and campaign attribution integration}}
 +
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=PreparePCArchFlows|anchor=PCConfigure|display text=Configure a PureCloud integration}}
 +
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=PreparePCArchFlows|anchor=ConfigurePCDataAction|display text=Configure PureCloud data actions}}
 +
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=BuildArchFlows|display text=Campaign parameters}}
 +
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=BuildArchFlows|anchor=AFWorkflow|display text=Prepare the workflow}}
 +
*{{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=MapContractFields|display text=Map contract fields}}
 +
*{{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}}
 +
 +
<br />
 
}}{{TSSection
 
}}{{TSSection
 
|sectionheading=Monitor your actions
 
|sectionheading=Monitor your actions

Revision as of 16:24, March 13, 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 you want to take to engage with users or to further related business outcomes. Genesys Predictive Engagement supports numerous types of actions, including content offers, webhooks, and webchats. An action map defines when and how you use a particular action.

Action Library

Use the Action Library to build 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

You build webhooks to integrate with external systems. Webhooks use PureCloud integrations and data actions.

Web chats

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.

Architect flow actions

Monitor your actions

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

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