Difference between revisions of "WID/Current/SDK/CallUs-combined"

From Genesys Documentation
Jump to: navigation, search
(Published)
(Published)
 
(6 intermediate revisions by 3 users not shown)
Line 5: Line 5:
 
|Context=Learn how to display an overlay screen showing one or more phone numbers for customer service, as well as the hours that this service is available.
 
|Context=Learn how to display an overlay screen showing one or more phone numbers for customer service, as well as the hours that this service is available.
 
|ComingSoon=No
 
|ComingSoon=No
|Platform=PureEngage
+
|Platform=GenesysEngage-cloud
 +
|Role=Developer
 
|Section={{Section
 
|Section={{Section
 +
|alignment=Vertical
 +
|structuredtext={{Video|id=548087059}}
 +
|Status=No
 +
}}{{Section
 
|sectionHeading=Overview
 
|sectionHeading=Overview
 +
|anchor=overview
 
|alignment=Vertical
 
|alignment=Vertical
 
|structuredtext=The CallUs Widget provides an overlay screen showing one or more phone numbers for customer service, as well as the hours that this service is available. The arrangement of numbers in this layout starts with a main phone number, which can be followed by alternative or additional phone numbers. Each number can be named, and there is no limit to the number of phone numbers you can include. If the list of numbers doesn't fit in the widget, the user can scroll down to see the rest.
 
|structuredtext=The CallUs Widget provides an overlay screen showing one or more phone numbers for customer service, as well as the hours that this service is available. The arrangement of numbers in this layout starts with a main phone number, which can be followed by alternative or additional phone numbers. Each number can be named, and there is no limit to the number of phone numbers you can include. If the list of numbers doesn't fit in the widget, the user can scroll down to see the rest.
  
[[File:CallUs Dark Desktop.png|600x600px]]
+
[[File:CallUs Dark Desktop.png|600x600px|alt=The CallUs Widget in dark theme listing customer service hours and phone numbers.]]
 
===Usage===
 
===Usage===
 
Launch CallUs manually by using the following methods:
 
Launch CallUs manually by using the following methods:
Line 22: Line 28:
  
 
{{AnchorDiv|cobr}}
 
{{AnchorDiv|cobr}}
===Co-browse link===
 
Co-browse is integrated into CallUs and can be indicated on the bottom right of the CallUs Widget. CallUs will detect if Co-browse is available based on your configuration. If Co-browse is available the link will be visible, if not the link will not be visible.
 
[[File:CallUs Dark Desktop Cobrowse.png|center|thumb|500x500px|Desktop overlay view with Co-browse]]
 
 
 
===Customization===
 
===Customization===
 
You can customize and {{Link-SomewhereInThisVersion|manual=Developer|topic=GWCInternat|display text=localize}} all of the text, titles, names, and numbers shown in the CallUs Widget by adding entries into your {{Link-SomewhereInThisVersion|manual=SDK|topic=CallUs-combined|anchor=config|display text=configuration}} and {{Link-SomewhereInThisVersion|manual=SDK|topic=CallUs-combined|anchor=localize|display text=localization}} options. There are no formatting requirements. Text will appear as you entered it.
 
You can customize and {{Link-SomewhereInThisVersion|manual=Developer|topic=GWCInternat|display text=localize}} all of the text, titles, names, and numbers shown in the CallUs Widget by adding entries into your {{Link-SomewhereInThisVersion|manual=SDK|topic=CallUs-combined|anchor=config|display text=configuration}} and {{Link-SomewhereInThisVersion|manual=SDK|topic=CallUs-combined|anchor=localize|display text=localization}} options. There are no formatting requirements. Text will appear as you entered it.
Line 45: Line 47:
 
{{!}}{{!}}callus
 
{{!}}{{!}}callus
 
{{!}}-
 
{{!}}-
{{!}}{{!}}CXBus—{{Link-SomewhereInThisVersion|manual=SDK|topic=CallUs-combined|anchor=commands|display text=API Commands}} & {{Link-SomewhereInThisVersion|manual=SDK|topic=CallUs-combined|anchor=events|display text=API Events}}
+
{{!}}{{!}}CXBus—{{Link-SomewhereInThisVersion|manual=SDK|topic=CallUs-combined|anchor=commands|display text=API commands}} & {{Link-SomewhereInThisVersion|manual=SDK|topic=CallUs-combined|anchor=events|display text=API events}}
 
{{!}}{{!}}CallUs
 
{{!}}{{!}}CallUs
 
{{!}}-
 
{{!}}-
Line 53: Line 55:
  
  
===Mobile Support===
+
===Mobile support===
CallUs supports both desktop and mobile devices. Like all Genesys Widgets, there are two main modes: Desktop & Mobile. Desktop is employed for monitors, laptops, and tablets. Mobile is employed for smartphones. When a smartphone is detected, CallUs switches to special fullscreen templates that are optimized for both portrait and landscape orientations.  
+
CallUs supports both desktop and mobile devices. Like all Genesys Widgets, there are two main modes: Desktop & Mobile. Desktop is employed for monitors, laptops, and tablets. Mobile is employed for smartphones. When a smartphone is detected, CallUs switches to special full-screen templates that are optimized for both portrait and landscape orientations.  
  
 
Switching between desktop and mobile mode is done automatically by default. You may configure Genesys Widgets to switch between Desktop and Mobile mode manually if necessary.  
 
Switching between desktop and mobile mode is done automatically by default. You may configure Genesys Widgets to switch between Desktop and Mobile mode manually if necessary.  
 
===Screenshots===
 
===Screenshots===
  
'''"Dark" theme'''
+
'''Dark theme'''
<gallery>
+
 
CallUs_Dark_Desktop.png|Desktop overlay view
+
[[File:CallUs_Dark_Desktop.png|150x150px|alt=The CallUs Widget in dark theme in the desktop overlay view.]]
CallUs_Dark_Mobile_Portrait.png|Mobile fullscreen view in portrait orientation
+
[[File:CallUs_Dark_Mobile_Portrait.png|150x150px|alt=The CallUs Widget in dark theme in mobile full screen view in portrait orientation.]]
CallUs_Dark_Mobile_Landscape.png|Mobile fullscreen view in landscape orientation
+
[[File:CallUs_Dark_Mobile_Landscape.png|150x150px|alt=The CallUs Widgets in dark theme in mobile full screen view in landscape orientation.]]
CallUs_Dark_Desktop_Cobrowse.png|Desktop overlay view with Co-browse
+
 
CallUs_Dark_Mobile_Portrait_Cobrowse.png|Mobile fullscreen view with Co-browse in portrait orientation
+
'''Light theme'''
CallUs_Dark_Mobile_Landscape_Cobrowse.png|Mobile fullscreen view with Co-browse in landscape orientation
+
 
</gallery>
+
[[File:CallUs_Light_Desktop.png|150x150px|alt=The CallUs Widget in light theme in desktop overlay view.]]
 +
[[File:CallUs_Light_Mobile_Portrait.png|150x150px|alt=The CallUs Widget in light theme in mobile full screen view in portrait orientation.]]
 +
[[File:CallUs_Light_Mobile_Landscape.png|150x150px||The CallUs Widget in light theme in mobile full screen view in portrait orientation.]]
  
'''"Light" theme'''
+
<br />
<gallery>
 
CallUs_Light_Desktop.png|Desktop overlay view
 
CallUs_Light_Mobile_Portrait.png|Mobile fullscreen view in portrait orientation
 
CallUs_Light_Mobile_Landscape.png|Mobile fullscreen view in landscape orientation
 
CallUs_Light_Desktop_Cobrowse.png|Desktop overlay view with Co-browse
 
CallUs_Light_Mobile_Portrait_Cobrowse.png|Mobile fullscreen view with Co-browse in portrait orientation
 
CallUs_Light_Mobile_Landscape_Cobrowse.png|Mobile fullscreen view with Co-browse in landscape orientation
 
</gallery>
 
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
Line 151: Line 147:
 
|anchor=localize
 
|anchor=localize
 
|alignment=Vertical
 
|alignment=Vertical
|structuredtext={{NoteFormat|For information on how to set up localization, please refer to the  {{Link-SomewhereInThisVersion|manual=Developer|topic=GWCInternat|display text=Localization Guide}}|1}}
+
|structuredtext={{NoteFormat|For information on how to set up localization, please refer to {{Link-AnywhereElse|product=WID|version=Current|manual=Developer|topic=GWCInternat|display text=Localize widgets and services}}.|1}}
 
===Usage===
 
===Usage===
 
Use the '''callus''' namespace when defining localization strings for the CallUs plugin in your i18n JSON file.
 
Use the '''callus''' namespace when defining localization strings for the CallUs plugin in your i18n JSON file.
Line 163: Line 159:
 
"SubTitle": "You can reach us at any of the following NUMBERS...",
 
"SubTitle": "You can reach us at any of the following NUMBERS...",
 
"CancelButtonText": "Cancel",
 
"CancelButtonText": "Cancel",
"CoBrowseText": "<span class='cx-cobrowse-offer'>Already on a call? Let us <a class='cx-cobrowse-link'>browse with you</a></span>",
 
"CoBrowse": "Start Co-browse",
 
"CoBrowseWarning": "Co-browse allows your agent to see and control your desktop, to help guide you. When on a live call with an
 
Agent, request a code to start Co-browse and enter it below. Not yet on a call? Just cancel out of this screen to return to Call Us page.",
 
 
"AriaWindowLabel": "Call Us Window",
 
"AriaWindowLabel": "Call Us Window",
 
"AriaCallUsClose": "Call Us Close",
 
"AriaCallUsClose": "Call Us Close",
 
"AriaBusinessHours": "Business Hours",
 
"AriaBusinessHours": "Business Hours",
 
"AriaCallUsPhoneApp": "Opens the phone application",
 
"AriaCallUsPhoneApp": "Opens the phone application",
"AriaCobrowseLink": "Opens the Co-browse Session",
+
"AriaCancelButtonText": "Cancel"
"AriaCancelButtonText": "Call Us Cancel"
 
 
}
 
}
 
}
 
}
Line 178: Line 169:
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
|sectionHeading=API Commands
+
|sectionHeading=API commands
 
|anchor=commands
 
|anchor=commands
 
|alignment=Vertical
 
|alignment=Vertical
 
|structuredtext=Once you've registered your plugin on the bus, you can call commands on other registered plugins. Here's how to use the global bus object to register a new plugin on the bus.
 
|structuredtext=Once you've registered your plugin on the bus, you can call commands on other registered plugins. Here's how to use the global bus object to register a new plugin on the bus.
  
{{NoteFormat|The global bus object is a debugging tool. When implementing Widgets on your own site, do not use the global bus object to register your custom plugins. Instead, see {{Link-SomewhereInThisManual|topic=GWCBusExtensions|anchor=top|display text=Widgets Extensions}} for more information about extending Genesys Widgets.|1}}
+
{{NoteFormat|The global bus object is a debugging tool. When implementing Widgets on your own site, do not use the global bus object to register your custom plugins. Instead, see {{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=GWCBusExtensions|display text=Genesys Widgets Extensions}} for more information about extending Genesys Widgets.|1}}
  
 
<source lang="javascript">var oMyPlugin = window._genesys.widgets.bus.registerPlugin('MyPlugin');
 
<source lang="javascript">var oMyPlugin = window._genesys.widgets.bus.registerPlugin('MyPlugin');
Line 211: Line 202:
 
{{!}}-
 
{{!}}-
 
{{!}}{{!}}resolved
 
{{!}}{{!}}resolved
{{!}}{{!}}When CallUs is successfully opened
+
{{!}}{{!}}CallUs is successfully opened
 
{{!}}{{!}}n/a
 
{{!}}{{!}}n/a
 
{{!}}-
 
{{!}}-
 
{{!}}{{!}}rejected
 
{{!}}{{!}}rejected
{{!}}{{!}}When CallUs is already open
+
{{!}}{{!}}CallUs is already open
 
{{!}}{{!}}'Already opened'
 
{{!}}{{!}}'Already opened'
 
{{!}}}
 
{{!}}}
Line 243: Line 234:
 
{{!}}-
 
{{!}}-
 
{{!}}{{!}}resolved
 
{{!}}{{!}}resolved
{{!}}{{!}}When CallUs successfully closed
+
{{!}}{{!}}CallUs successfully closed
 
{{!}}{{!}}n/a
 
{{!}}{{!}}n/a
 
{{!}}-
 
{{!}}-
 
{{!}}{{!}}rejected
 
{{!}}{{!}}rejected
{{!}}{{!}}When CallUs is already closed
+
{{!}}{{!}}CallUs is already closed
 
{{!}}{{!}}'Already closed'
 
{{!}}{{!}}'Already closed'
 
{{!}}}
 
{{!}}}
Line 304: Line 295:
 
{{!}}-
 
{{!}}-
 
{{!}}{{!}}resolved
 
{{!}}{{!}}resolved
{{!}}{{!}}When CallUs configuration is provided
+
{{!}}{{!}}CallUs configuration is provided
 
{{!}}{{!}}n/a
 
{{!}}{{!}}n/a
 
{{!}}-
 
{{!}}-
 
{{!}}{{!}}rejected
 
{{!}}{{!}}rejected
{{!}}{{!}}When no configuration provided
+
{{!}}{{!}}No configuration is provided
 
{{!}}{{!}}'Invalid Configuration'
 
{{!}}{{!}}'Invalid Configuration'
 
{{!}}}
 
{{!}}}
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
|sectionHeading=API Events
+
|sectionHeading=API events
 
|anchor=events
 
|anchor=events
 
|alignment=Vertical
 
|alignment=Vertical
 
|structuredtext=Once you've registered your plugin on the bus, you can subscribe to and listen for published events. Here's how to use the global bus object to register a new plugin on the bus.
 
|structuredtext=Once you've registered your plugin on the bus, you can subscribe to and listen for published events. Here's how to use the global bus object to register a new plugin on the bus.
  
{{NoteFormat|The global bus object is a debugging tool. When implementing Widgets on your own site, do not use the global bus object to register your custom plugins. Instead, see {{Link-SomewhereInThisManual|topic=GWCBusExtensions|anchor=top|display text=Widgets Extensions}} for more information about extending Genesys Widgets.|1}}
+
{{NoteFormat|The global bus object is a debugging tool. When implementing Widgets on your own site, do not use the global bus object to register your custom plugins. Instead, see {{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=GWCBusExtensions|display text=Genesys Widgets Extensions}} for more information about extending Genesys Widgets.|1}}
  
 
<source lang="javascript">var oMyPlugin = window._genesys.widgets.bus.registerPlugin('MyPlugin');
 
<source lang="javascript">var oMyPlugin = window._genesys.widgets.bus.registerPlugin('MyPlugin');

Latest revision as of 12:32, October 12, 2021

This topic is part of the manual Widgets API Reference for version Current of Widgets.

Learn how to display an overlay screen showing one or more phone numbers for customer service, as well as the hours that this service is available.

Related documentation:

Overview

The CallUs Widget provides an overlay screen showing one or more phone numbers for customer service, as well as the hours that this service is available. The arrangement of numbers in this layout starts with a main phone number, which can be followed by alternative or additional phone numbers. Each number can be named, and there is no limit to the number of phone numbers you can include. If the list of numbers doesn't fit in the widget, the user can scroll down to see the rest.

The CallUs Widget in dark theme listing customer service hours and phone numbers.

Usage

Launch CallUs manually by using the following methods:

  • Call the CallUs.open command
  • Configure ChannelSelector to show CallUs as a channel
  • Create your own custom button or link to open CallUs (using the "CallUs.open" command)
Important
By default a user has no way of launching the CallUs Widget. You must choose a suitable method for launching this widget.

Customization

You can customize and localize all of the text, titles, names, and numbers shown in the CallUs Widget by adding entries into your configuration and localization options. There are no formatting requirements. Text will appear as you entered it.

Important
If you do not configure the CallUs Widget it will appear as an empty overlay. You must configure this Widget before using it.

CallUs supports themes. You can create and register your own themes for Genesys Widgets.

Namespace

The CallUs plugin has the following namespaces tied up with each of the following types:

Type Namespace
Configuration callus
i18n—Localization callus
CXBus—API commands & API events CallUs
CSS .cx-call-us


Mobile support

CallUs supports both desktop and mobile devices. Like all Genesys Widgets, there are two main modes: Desktop & Mobile. Desktop is employed for monitors, laptops, and tablets. Mobile is employed for smartphones. When a smartphone is detected, CallUs switches to special full-screen templates that are optimized for both portrait and landscape orientations.

Switching between desktop and mobile mode is done automatically by default. You may configure Genesys Widgets to switch between Desktop and Mobile mode manually if necessary.

Screenshots

Dark theme

The CallUs Widget in dark theme in the desktop overlay view. The CallUs Widget in dark theme in mobile full screen view in portrait orientation. The CallUs Widgets in dark theme in mobile full screen view in landscape orientation.

Light theme

The CallUs Widget in light theme in desktop overlay view. The CallUs Widget in light theme in mobile full screen view in portrait orientation. The CallUs Widget in light theme in mobile full screen view in portrait orientation.


Configuration

CallUs uses the _genesys.widgets.callus configuration property. You must specify all of the numbers and labels that appear in the CallUs UI.

Example

window._genesys.widgets.callus = callus: {

	contacts: [

		{
			displayName: 'Payments',
			i18n: 'Number001',
			number: '1 202 555 0162'
		},
		{
			displayName: 'Local',
			i18n: 'Number002',
			number: '202 555 0134'
		},
		{
			displayName: 'International',
			i18n: 'Number003',
			number: '0647 555 0131'
		}
	],

	hours: [

		'8am - 8pm Mon - Fri',
		'10am - 6pm Sat - Sun'
	]
};

Options

Name Type Description Default Required
contacts array An array of objects that represent phone numbers and their labels. The first number in this list will display as the larger, main number. Phone labels can be set directly using the 'displayName' property or you can use String Names from your localization file by setting the String Name in the 'i18n' property. 'i18n' overrides 'displayName'.

Example

{
	"displayName": "Payments",
	"i18n": "Number001",
	"number": "1 202 555 0162"
}
[] true
hours array Array of strings to show stacked in the business hours section. Strings here are freeform. See screenshots for ideas. []  

Localization

Important
For information on how to set up localization, please refer to Localize widgets and services.

Usage

Use the callus namespace when defining localization strings for the CallUs plugin in your i18n JSON file.

The following example shows how to define new strings for the en (English) language. You can use any language codes you wish; there is no standard format. When selecting the active language in your configuration, you must match one of the language codes defined in your i18n JSON file. Please note that you must only define a language code once in your i18n JSON file. Inside each language object you should define new strings for each widget.

Example i18n JSON

{
	"en": {
		"callus": {
			"CallUsTitle": "Call Us",
			"SubTitle": "You can reach us at any of the following NUMBERS...",
			"CancelButtonText": "Cancel",
			"AriaWindowLabel": "Call Us Window",
			"AriaCallUsClose": "Call Us Close",
			"AriaBusinessHours": "Business Hours",
			"AriaCallUsPhoneApp": "Opens the phone application",
			"AriaCancelButtonText": "Cancel"
		}
	}
}

API commands

Once you've registered your plugin on the bus, you can call commands on other registered plugins. Here's how to use the global bus object to register a new plugin on the bus.

Important
The global bus object is a debugging tool. When implementing Widgets on your own site, do not use the global bus object to register your custom plugins. Instead, see Genesys Widgets Extensions for more information about extending Genesys Widgets.
var oMyPlugin = window._genesys.widgets.bus.registerPlugin('MyPlugin');

oMyPlugin.command('CallUs.open');

open

Opens the CallUs UI.

Example

oMyPlugin.command('CallUs.open').done(function(e){

	// CallUs opened successfully

}).fail(function(e){

	// CallUs failed to open
});

Resolutions

Status When Returns
resolved CallUs is successfully opened n/a
rejected CallUs is already open 'Already opened'


close

Closes the CallUs UI.

Example

oMyPlugin.command('CallUs.close').done(function(e){

	// CallUs closed successfully

}).fail(function(e){

	// CallUs failed to close
});

Resolutions

Status When Returns
resolved CallUs successfully closed n/a
rejected CallUs is already closed 'Already closed'


configure

Internal use only. The main App plugin shares configuration settings to widgets using each widget’s configure command. The configure command can only be called once at startup. Calling configure again after startup may result in unpredictable behavior.

Example

oMyPlugin.command('CallUs.configure', {

	contacts: [
		{
			displayName: 'Payments',
			i18n: 'Number001',
			number: '1 888 436 3797'
		}
	],
	hours: ['8am - 8pm Mon - Fri']

}).done(function(e){

	// CallUs configred successfully

}).fail(function(e){

	// CallUs failed to configure
});

Options

Option Type Description
contacts Array An array of objects that represent phone numbers and their labels. The first number in this list will display as the larger, main number.
hours Array Array of strings to show stacked in the business hours section. Strings here are freeform.


Resolutions

Status When Returns
resolved CallUs configuration is provided n/a
rejected No configuration is provided 'Invalid Configuration'

API events

Once you've registered your plugin on the bus, you can subscribe to and listen for published events. Here's how to use the global bus object to register a new plugin on the bus.

Important
The global bus object is a debugging tool. When implementing Widgets on your own site, do not use the global bus object to register your custom plugins. Instead, see Genesys Widgets Extensions for more information about extending Genesys Widgets.
var oMyPlugin = window._genesys.widgets.bus.registerPlugin('MyPlugin');

oMyPlugin.subscribe('CallUs.ready', function(e){});
Name Description Data
ready CallUs is initialized and ready to accept commands  
opened CallUs UI has been opened  
closed CallUs UI has been closed  
Retrieved from "https://all.docs.genesys.com/WID/Current/SDK/CallUs-combined (2024-11-09 12:58:04)"
Comments or questions about this documentation? Contact us for support!