PE-GPR/9.0.0/Deployment/GPRbilling - Revision history

Vivian: Published

2020-09-22T13:26:52Z

Published

WikiSysop: Text replacement - "\|Platform=([^\|])GenesysEngage-onpremises([\|])" to "|Platform=$1GenesysEngage-cloud$2"

2020-07-25T02:30:11Z

Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2"

WikiSysop: Text replacement - "\|Platforms?=([^\|])PureEngage([\|])" to "|Platform=$1GenesysEngage-onpremises$2"

2020-07-15T11:44:43Z

Text replacement - "\|Platforms?=([^\|]*)PureEngage([\|]*)" to "|Platform=$1GenesysEngage-onpremises$2"

Vivian: Published

2020-03-06T17:59:44Z

Published

WikiSysop at 13:45, January 17, 2020

2020-01-17T13:45:57Z

Vivian: Published

2019-12-20T22:15:56Z

Published

New page

{{Article
|Standalone=No
|DisplayName=How GPR Reports Data for Billing
|Platform=PureEngage
|TocName=How GPR Reports Data for Billing
|ComingSoon=No
|Context=GPR generates data that is used to determine which interactions are billable.
|Section={{Section
|sectionHeading=What is Billed?
|Type=Unstructured
|freetext=GPR Billing counts only successfully routed interactions. If an interaction is not delivered to an agent, it is not be billed, even if it was routed using GPR. The following points describe how GPR handles some specific scenarios:

*If your routing strategy is configured to ask GPR to score agents multiple time for a single interaction, you are billed for each score request that was successfully processed, routed, and answered. For example, your strategy might transfer an interaction using GPR, resulting in scoring for the initial agent and a second scoring request to locate the agent to which the interaction is transferred. Or your routing might use queue chains, with multiple calls to GPR for agent scores.
*If a consult call has the same ConnectionID as the main one, the consult is to be billed as only one call. If the consult call results in two ConnectionIDs, it is billed as two calls.
*An interaction scored in queue by GPR that ends up being routed using skills-based routing—for example, because it remained in queue long enough to trigger default routing—the interaction '''is''' charged because GPR is statistically contributing to the lift of the whole queue by the fact that ''all'' interactions are scored. Details on this scenario (and all others) is captured in the gpmMode, gpmResult, and gpmUse KVPs.
|Status=No
}}
}}

@@ Line 5: / Line 5: @@
 |Context=GPR generates data that is used to determine which interactions are billable.
 |ComingSoon=No
-|Platform=GenesysEngage-cloud
+|Platform=GenesysEngage-onpremises
 |Section={{Section
 |sectionHeading=What is billed?

@@ Line 5: / Line 5: @@
 |Context=GPR generates data that is used to determine which interactions are billable.
 |ComingSoon=No
-|Platform=GenesysEngage-onpremises
+|Platform=GenesysEngage-cloud
 |Section={{Section
 |sectionHeading=What is billed?

@@ Line 1: / Line 1: @@
 {{Article
 |Standalone=No
-|DisplayName=How GPR Reports Data for Billing
+|DisplayName=How GPR reports data for billing
 |Platform=PureEngage
 |Section={{Section
-|sectionHeading=What is Billed?
+|sectionHeading=What is billed?
 |alignment=Vertical
 |structuredtext=GPR Billing counts only successfully routed interactions. If an interaction is not delivered to an agent, it is not be billed, even if it was routed using GPR. The following points describe how GPR handles some specific scenarios:

PE-GPR/9.0.0/Deployment/GPRbilling - Revision history

Vivian: Published

WikiSysop: Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2"

WikiSysop: Text replacement - "\|Platforms?=([^\|]*)PureEngage([\|]*)" to "|Platform=$1GenesysEngage-onpremises$2"

Vivian: Published

WikiSysop at 13:45, January 17, 2020

Vivian: Published

WikiSysop: Text replacement - "\|Platform=([^\|])GenesysEngage-onpremises([\|])" to "|Platform=$1GenesysEngage-cloud$2"

WikiSysop: Text replacement - "\|Platforms?=([^\|])PureEngage([\|])" to "|Platform=$1GenesysEngage-onpremises$2"