Difference between revisions of "DES/Current/Designer/ClickToCall"
m (Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2") |
(Published) |
||
| Line 8: | Line 8: | ||
|Role=Administrator | |Role=Administrator | ||
|Application=Designer | |Application=Designer | ||
| − | |||
|Section={{Section | |Section={{Section | ||
| − | |||
| − | |||
|alignment=Vertical | |alignment=Vertical | ||
| − | |||
| − | |||
|structuredtext=You can use this block to support the '''Click-to-Call-In Match''' feature. In a typical '''Click-to-Call-In Match''' scenario, a caller dials a contact center and provides some additional information during the Self Service phase, such as the reason why they are calling. They are then given a phone number to dial along with a special access code. | |structuredtext=You can use this block to support the '''Click-to-Call-In Match''' feature. In a typical '''Click-to-Call-In Match''' scenario, a caller dials a contact center and provides some additional information during the Self Service phase, such as the reason why they are calling. They are then given a phone number to dial along with a special access code. | ||
| Line 20: | Line 15: | ||
Depending on the matching criteria used, the match block then generates all combinations for the output as segmentation branches, where each segmentation has its own '''Navigation''' tab that specifies where to route the interaction. | Depending on the matching criteria used, the match block then generates all combinations for the output as segmentation branches, where each segmentation has its own '''Navigation''' tab that specifies where to route the interaction. | ||
| − | |||
| − | |||
|Status=No | |Status=No | ||
}}{{Section | }}{{Section | ||
| Line 27: | Line 20: | ||
|anchor=Usingthisblock | |anchor=Usingthisblock | ||
|alignment=Vertical | |alignment=Vertical | ||
| − | |||
| − | |||
|structuredtext=Typically, you would add a {{Link-SomewhereInThisManual|topic=UserInput|anchor=top|display text=User Input block}} ahead of this block to prompt the caller for their access code and specify the variable that will hold it. Then use the '''Click-to-Call-In Match''' block to specify the matching criteria and the variable that will hold the returned data, if a match is made. | |structuredtext=Typically, you would add a {{Link-SomewhereInThisManual|topic=UserInput|anchor=top|display text=User Input block}} ahead of this block to prompt the caller for their access code and specify the variable that will hold it. Then use the '''Click-to-Call-In Match''' block to specify the matching criteria and the variable that will hold the returned data, if a match is made. | ||
| Line 34: | Line 25: | ||
If there are no matches, you can use the '''Navigation''' tab on the '''Nothing Matched''' block to go to a specified block, skipping the '''Call Data''' block. | If there are no matches, you can use the '''Navigation''' tab on the '''Nothing Matched''' block to go to a specified block, skipping the '''Call Data''' block. | ||
| − | |||
| − | |||
|Status=No | |Status=No | ||
}}{{Section | }}{{Section | ||
| Line 41: | Line 30: | ||
|anchor=MatchCriteriatab | |anchor=MatchCriteriatab | ||
|alignment=Vertical | |alignment=Vertical | ||
| − | |||
| − | |||
|structuredtext=Use the settings on this tab to specify which criteria to compare to the original request. You must specify at least one item. | |structuredtext=Use the settings on this tab to specify which criteria to compare to the original request. You must specify at least one item. | ||
| Line 52: | Line 39: | ||
[[File:Des click to call in outcomes.png]] | [[File:Des click to call in outcomes.png]] | ||
| − | |||
| − | |||
|Status=No | |Status=No | ||
}}{{Section | }}{{Section | ||
| Line 59: | Line 44: | ||
|anchor=routing_parameters | |anchor=routing_parameters | ||
|alignment=Vertical | |alignment=Vertical | ||
| − | |||
| − | |||
|structuredtext=For Click-to-Call-In {{Link-AnywhereElse|product=PEC-CAB|version=Current|manual=Administrator|topic=CallbackScenarios|anchor=CtciDelayed|display text=delayed scenarios}}, routing parameters are returned if there is a unique match. Use the settings on this tab to specify the variables that will hold the values for each parameter. | |structuredtext=For Click-to-Call-In {{Link-AnywhereElse|product=PEC-CAB|version=Current|manual=Administrator|topic=CallbackScenarios|anchor=CtciDelayed|display text=delayed scenarios}}, routing parameters are returned if there is a unique match. Use the settings on this tab to specify the variables that will hold the values for each parameter. | ||
| Line 71: | Line 54: | ||
*Priority Increment | *Priority Increment | ||
*Maximum Priority | *Maximum Priority | ||
| − | *Notification Timestamp (when the push notification was initiated) | + | <!--*Notification Timestamp (when the push notification was initiated)--> |
For more information, see {{Link-AnywhereElse|product=PEC-CAB|version=Current|manual=Administrator|topic=CallbackScenarios|anchor=CtciDelayed|display text=Click-to-Call-In (Delayed)}}. | For more information, see {{Link-AnywhereElse|product=PEC-CAB|version=Current|manual=Administrator|topic=CallbackScenarios|anchor=CtciDelayed|display text=Click-to-Call-In (Delayed)}}. | ||
| − | |||
| − | |||
|Status=No | |Status=No | ||
}}{{Section | }}{{Section | ||
| Line 81: | Line 62: | ||
|anchor=results | |anchor=results | ||
|alignment=Vertical | |alignment=Vertical | ||
| − | |||
| − | |||
|structuredtext=Specify the variable that will hold the retrieved storage information if a match is found. | |structuredtext=Specify the variable that will hold the retrieved storage information if a match is found. | ||
| Line 88: | Line 67: | ||
[[file:des_click_to_call_in_match_results.png|400px]] | [[file:des_click_to_call_in_match_results.png|400px]] | ||
| − | |||
| − | |||
|Status=No | |Status=No | ||
}} | }} | ||
}} | }} | ||
Revision as of 14:58, September 23, 2020
Use this block to add Click-to-Call-In Match functionality to your application.
You can use this block to support the Click-to-Call-In Match feature. In a typical Click-to-Call-In Match scenario, a caller dials a contact center and provides some additional information during the Self Service phase, such as the reason why they are calling. They are then given a phone number to dial along with a special access code.
The application uses this block to compare the caller's information with the details of the original request, such as the access code they entered, the number they called from, or the number they dialed. If a match is found, the additional information that was submitted with the original request is returned to the block.
Depending on the matching criteria used, the match block then generates all combinations for the output as segmentation branches, where each segmentation has its own Navigation tab that specifies where to route the interaction.
Using this block
Typically, you would add a User Input block ahead of this block to prompt the caller for their access code and specify the variable that will hold it. Then use the Click-to-Call-In Match block to specify the matching criteria and the variable that will hold the returned data, if a match is made.
For example, if all three criteria are used, this creates eight possible outcomes (or segmentation branches), including an outcome where Nothing Matched. You can then use a Call Data block to attach the returned data to the current interaction.
If there are no matches, you can use the Navigation tab on the Nothing Matched block to go to a specified block, skipping the Call Data block.
Match Criteria tab
Use the settings on this tab to specify which criteria to compare to the original request. You must specify at least one item.
Example
Notice that Designer automatically creates child blocks for each outcome, which you can then use to specify the action to take if a match is found:
Routing Parameters
For Click-to-Call-In delayed scenarios, routing parameters are returned if there is a unique match. Use the settings on this tab to specify the variables that will hold the values for each parameter.
You can select variables for the following parameters:
- Outbound VQ
- Target Skill Expression
- Current Priority
- Priority Increment Interval
- Priority Increment
- Maximum Priority
For more information, see Click-to-Call-In (Delayed).
Results tab
Specify the variable that will hold the retrieved storage information if a match is found.
Example
