From Bright Pattern Documentation
Jump to: navigation, search
(Marked this version for translation)
 
Line 1: Line 1:
<translate>= Web Callback=
+
<translate>= Web Callback= <!--T:1-->
 
Web Callback scenario entries are used to associate [[contact-center-administrator-guide/Chat|scenarios]] with services used to provide callbacks requested by customers via mobile and web applications.
 
Web Callback scenario entries are used to associate [[contact-center-administrator-guide/Chat|scenarios]] with services used to provide callbacks requested by customers via mobile and web applications.
  
 +
<!--T:2-->
 
To set up and manage such associations, select the '''Web Callback''' option from the ''Scenario Entries'' menu.
 
To set up and manage such associations, select the '''Web Callback''' option from the ''Scenario Entries'' menu.
  
  
 +
<!--T:3-->
 
[[File:Web-Callback-50.png|thumb|800px|center|Scenario Entries &gt; Web Callback]]
 
[[File:Web-Callback-50.png|thumb|800px|center|Scenario Entries &gt; Web Callback]]
  
  
  
== Web Callback Scenario Entries Screen Properties ==
+
== Web Callback Scenario Entries Screen Properties == <!--T:4-->
 
The ''Web Callback Scenario Entries'' screen properties are described as follows.
 
The ''Web Callback Scenario Entries'' screen properties are described as follows.
  
=== Name ===
+
=== Name === <!--T:5-->
 
''Name'' is the name of the web callback scenario entry. This field is mandatory and must be unique within the contact center.
 
''Name'' is the name of the web callback scenario entry. This field is mandatory and must be unique within the contact center.
  
=== Unique identifier ===
+
=== Unique identifier === <!--T:6-->
 
The ''Unique identifier'' is generated by the system for this scenario entry. This identifier must be used as ''Application ID'' in the mobile and/or web applications that will connect to your contact center via this scenario entry. For more information, see section [[mobile-web-api-specification/GeneralInformation|General Information]] of the  Bright Pattern ''Mobile/Web API Specification''.
 
The ''Unique identifier'' is generated by the system for this scenario entry. This identifier must be used as ''Application ID'' in the mobile and/or web applications that will connect to your contact center via this scenario entry. For more information, see section [[mobile-web-api-specification/GeneralInformation|General Information]] of the  Bright Pattern ''Mobile/Web API Specification''.
  
=== Scenario ===
+
=== Scenario === <!--T:7-->
 
''Scenario'' is the [[contact-center-administrator-guide/Chat|Chat scenario]] that will process chat interactions in which the customer requests a web callback.
 
''Scenario'' is the [[contact-center-administrator-guide/Chat|Chat scenario]] that will process chat interactions in which the customer requests a web callback.
  
=== Service ===
+
=== Service === <!--T:8-->
 
''Service'' refers to the service associated with the dial-in scenario entry. Such direct association between telephone number and a service can be used when your access numbers directly identify your services.
 
''Service'' refers to the service associated with the dial-in scenario entry. Such direct association between telephone number and a service can be used when your access numbers directly identify your services.
  
 +
<!--T:9-->
 
Even if you use one access number for many different services (i.e., use an interactive voice script within the associated scenario for service selection), you may still assign a default service directly to the access number in order to account for the calls abandoned before service selection and for the calls that bypass the service selection stage (e.g., someone is unable to use the keypad to enter service selection choice, or someone is confused about which option to choose).
 
Even if you use one access number for many different services (i.e., use an interactive voice script within the associated scenario for service selection), you may still assign a default service directly to the access number in order to account for the calls abandoned before service selection and for the calls that bypass the service selection stage (e.g., someone is unable to use the keypad to enter service selection choice, or someone is confused about which option to choose).
  
=== Default service for voice callback ===
+
=== Default service for voice callback === <!--T:10-->
 
The ''default service for voice callback'' is the [[contact-center-administrator-guide/Voice|voice service]] to be used to provide a callback to the customer.
 
The ''default service for voice callback'' is the [[contact-center-administrator-guide/Voice|voice service]] to be used to provide a callback to the customer.
  
=== Show chat window ===
+
=== Show chat window === <!--T:11-->
 
It is possible to view the chat interaction while a web callback is taking place. Select this checkbox to show the chat window during web callbacks.
 
It is possible to view the chat interaction while a web callback is taking place. Select this checkbox to show the chat window during web callbacks.
  
=== Hours of Operation ===
+
=== Hours of Operation === <!--T:12-->
 
Hours of operation (HOP) is a schedule that defines service hours for each day of the year.  
 
Hours of operation (HOP) is a schedule that defines service hours for each day of the year.  
 
* Choose '''from service''' to use [[contact-center-administrator-guide/PropertiesTab|HOPs of the services]] associated with interactions processed by the given scenario.   
 
* Choose '''from service''' to use [[contact-center-administrator-guide/PropertiesTab|HOPs of the services]] associated with interactions processed by the given scenario.   
Line 38: Line 41:
 
* Choose '''specify''' to define a new HOP specifically for this scenario entry.  
 
* Choose '''specify''' to define a new HOP specifically for this scenario entry.  
  
 +
<!--T:13-->
 
Unless you create an entry point for a 24/7 operation, the scenario that you have specified in the ''Scenario'' property above must define processing of interaction arriving at this entry outside as well as within the specified hours of operation. That is, the scenario should normally begin with an [[scenario-builder-reference-guide/If|If]] block that has the condition ''The current date and time is'' (or ''is not'') ''in hours of operation''. For more information, see the [[scenario-builder-reference-guide/ScenarioExample|example]] provided in the ''Scenario Builder Reference Guide''.
 
Unless you create an entry point for a 24/7 operation, the scenario that you have specified in the ''Scenario'' property above must define processing of interaction arriving at this entry outside as well as within the specified hours of operation. That is, the scenario should normally begin with an [[scenario-builder-reference-guide/If|If]] block that has the condition ''The current date and time is'' (or ''is not'') ''in hours of operation''. For more information, see the [[scenario-builder-reference-guide/ScenarioExample|example]] provided in the ''Scenario Builder Reference Guide''.
  
 +
<!--T:14-->
 
HOPs can also be [[contact-center-administrator-guide/PropertiesTab|specified at the service level]].
 
HOPs can also be [[contact-center-administrator-guide/PropertiesTab|specified at the service level]].
  
 +
<!--T:15-->
 
Note the following:
 
Note the following:
 
* If you use options ''select'' or ''specify'' to define HOP for this scenario entry, all possible HOP checks within this scenario will use the HOP defined for this entry. Any HOPs specified for any services within this scenario will be disregarded.
 
* If you use options ''select'' or ''specify'' to define HOP for this scenario entry, all possible HOP checks within this scenario will use the HOP defined for this entry. Any HOPs specified for any services within this scenario will be disregarded.
Line 47: Line 53:
 
* If you (1) use option ''from service'', (2) do not have any ''Service'' configured for this scenario entry, and (3) use an HOP check before any explicit service assignment within the scenario, all incoming interactions will be treated as if they arrived outside of the service hours.
 
* If you (1) use option ''from service'', (2) do not have any ''Service'' configured for this scenario entry, and (3) use an HOP check before any explicit service assignment within the scenario, all incoming interactions will be treated as if they arrived outside of the service hours.
  
=== Form fields ===
+
=== Form fields === <!--T:16-->
 
Customers who request a web callback will provide information (e.g., name, phone number, email, etc.) to the agent by typing into ''form fields''. To add a new form field and/or change the field's label, click '''add.''' You will be prompted to select the ''type'' of form field and to enter ''label text'' for the form field.
 
Customers who request a web callback will provide information (e.g., name, phone number, email, etc.) to the agent by typing into ''form fields''. To add a new form field and/or change the field's label, click '''add.''' You will be prompted to select the ''type'' of form field and to enter ''label text'' for the form field.
  
=== Web HTML snippet ===
+
=== Web HTML snippet === <!--T:17-->
 
The ''Web HTML snippet'' provides access to the web elements of the chat application that customers will use to access your contact center via the given scenario entry.
 
The ''Web HTML snippet'' provides access to the web elements of the chat application that customers will use to access your contact center via the given scenario entry.
  
 +
<!--T:18-->
 
To use the out-of-the-box application, click the '''HTML snippet''' button, '''copy''' the HTML snippet code, and embed it into your web page(s). Normally, it is not necessary to change the default '''client web server hostname'''. You will do so only if instructed by your service provider.
 
To use the out-of-the-box application, click the '''HTML snippet''' button, '''copy''' the HTML snippet code, and embed it into your web page(s). Normally, it is not necessary to change the default '''client web server hostname'''. You will do so only if instructed by your service provider.
  

Latest revision as of 04:31, 25 June 2020

Other languages:
English • ‎日本語
• 5.3 • 5.8

Web Callback

Web Callback scenario entries are used to associate scenarios with services used to provide callbacks requested by customers via mobile and web applications.

To set up and manage such associations, select the Web Callback option from the Scenario Entries menu.


Scenario Entries > Web Callback


Web Callback Scenario Entries Screen Properties

The Web Callback Scenario Entries screen properties are described as follows.

Name

Name is the name of the web callback scenario entry. This field is mandatory and must be unique within the contact center.

Unique identifier

The Unique identifier is generated by the system for this scenario entry. This identifier must be used as Application ID in the mobile and/or web applications that will connect to your contact center via this scenario entry. For more information, see section General Information of the Bright Pattern Mobile/Web API Specification.

Scenario

Scenario is the Chat scenario that will process chat interactions in which the customer requests a web callback.

Service

Service refers to the service associated with the dial-in scenario entry. Such direct association between telephone number and a service can be used when your access numbers directly identify your services.

Even if you use one access number for many different services (i.e., use an interactive voice script within the associated scenario for service selection), you may still assign a default service directly to the access number in order to account for the calls abandoned before service selection and for the calls that bypass the service selection stage (e.g., someone is unable to use the keypad to enter service selection choice, or someone is confused about which option to choose).

Default service for voice callback

The default service for voice callback is the voice service to be used to provide a callback to the customer.

Show chat window

It is possible to view the chat interaction while a web callback is taking place. Select this checkbox to show the chat window during web callbacks.

Hours of Operation

Hours of operation (HOP) is a schedule that defines service hours for each day of the year.

  • Choose from service to use HOPs of the services associated with interactions processed by the given scenario.
  • Choose select to select one of the preconfigured HOPs.
  • Choose specify to define a new HOP specifically for this scenario entry.

Unless you create an entry point for a 24/7 operation, the scenario that you have specified in the Scenario property above must define processing of interaction arriving at this entry outside as well as within the specified hours of operation. That is, the scenario should normally begin with an If block that has the condition The current date and time is (or is not) in hours of operation. For more information, see the example provided in the Scenario Builder Reference Guide.

HOPs can also be specified at the service level.

Note the following:

  • If you use options select or specify to define HOP for this scenario entry, all possible HOP checks within this scenario will use the HOP defined for this entry. Any HOPs specified for any services within this scenario will be disregarded.
  • If you use option from service, the HOP check will use the HOP of the service that is associated with the interaction at the time when the check is performed. By default, this is the Service configured for this scenario entry (see above). However, if the service is redefined within the scenario, a subsequent HOP check will use the HOP of that new service.
  • If you (1) use option from service, (2) do not have any Service configured for this scenario entry, and (3) use an HOP check before any explicit service assignment within the scenario, all incoming interactions will be treated as if they arrived outside of the service hours.

Form fields

Customers who request a web callback will provide information (e.g., name, phone number, email, etc.) to the agent by typing into form fields. To add a new form field and/or change the field's label, click add. You will be prompted to select the type of form field and to enter label text for the form field.

Web HTML snippet

The Web HTML snippet provides access to the web elements of the chat application that customers will use to access your contact center via the given scenario entry.

To use the out-of-the-box application, click the HTML snippet button, copy the HTML snippet code, and embed it into your web page(s). Normally, it is not necessary to change the default client web server hostname. You will do so only if instructed by your service provider.



< Previous | Next >