Upload
ken-greenberg
View
11
Download
0
Embed Size (px)
DESCRIPTION
SAP Contact Center 7 - Callback Functionality Overview
Citation preview
Callback Requests SAP Contact Center software version 7 Service Pack 7 (SAP CCtr 7 SP7) SAP Contact Center Product Management
2014 Public
2014 SAP AG or an SAP affiliate company. All rights reserved. 2 Public
Scheduled callback request
Note! These are sample web callback forms. Customer organizations can freely modify them or create new callback forms with customer specific functionality.
Customer fills the callback form in the web.
The web form can contain automatic detection
of country, language and local time.
Customer submits the callback request to
SAP Contact Center.
The callback functionality enables modifying
and filtering numbers if needed.
The callback request
appears in the inbound
queue when the scheduled
callback is due.
Agent accepts the callback request and the
callback call is automatically dialed.
Agent classifies the callback based on the
result.
2014 SAP AG or an SAP affiliate company. All rights reserved. 3 Public
Immediate callback request
Note! These are sample web callback forms. Customer organizations can freely modify them or create new callback forms with customer specific functionality.
Customer fills the callback form in the web.
The web form can contain automatic detection
of country and language.
Customer submits the callback request to
SAP Contact Center.
The callback functionality enables modifying
and filtering numbers if needed.
The callback request
appears in the inbound
queue asap.
Agent accepts the callback request and the
callback call is automatically dialed.
Agent classifies the callback based on the
result.
2014 SAP AG or an SAP affiliate company. All rights reserved. 4 Public
Callback request integrated with SAP CRM
Leaving a callback by phone Leaving a callback via web Callback routing Handling the callback
The callback option can be offered to customer
based on queue routing parameters.
The callback can be immediate (a.k.a. virtual
hold), or scheduled, dependent on the Callback
IVR setup.
If the callers number is recognized, the callback request is registered to that number.
Alternatively, dependent on the IVR settings,
customer can enter another number to where the
callback is done.
Customer fills the callback form
with appropriate information.
The callback can be an
immediate callback or
scheduled.
Prior accepting the callback, a check for
non-allowed callback numbers is done.
These are configurable, e.g. emergency
numbers and various service numbers
can be excluded.
The callback requests are routed to
callback request queue and further to an
available and skills matching agent.
The alerting callback event is signalized
as a call. This means that the integration
with SAP CRM enables the business
partner search based on the telephone
number.
Once accepted the actual outbound call
is made.
When finished, agent uses the CDT
scripting to classify the callback result.
Internet
SAP Contact Center
SAP
CRM
CBR Queue
Agent selection CBR Call
Call event
Call event
Customer data is shown based on A-number or
business partner ID
Call to
customer service Queue selection
CBR IVR
Callbacks
Agent classifies the success
of the callback event using
CDT scripting
Callback
form
2014 SAP AG or an SAP affiliate company. All rights reserved. 5 Public
Callback request integrated with SAP C4C
Leaving a callback by phone Leaving a callback via web Callback routing Handling the callback
The callback option can be offered to customer
based on queue routing parameters.
The callback can be immediate (a.k.a. virtual
hold), or scheduled, dependent on the Callback
IVR setup.
If the callers number is recognized, the callback request is registered to that number.
Alternatively, dependent on the IVR settings,
customer can enter another number to where the
callback is done.
Customer fills the callback form
with appropriate information.
The callback can be an
immediate callback or
scheduled.
Prior accepting the callback, a check for
non-allowed callback numbers is done.
These are configurable, e.g. emergency
numbers and various service numbers
can be excluded.
The callback requests are routed to
callback request queue and further to an
available and skills matching agent.
The alerting callback event is signalized
as a call. This means that the integration
with SAP C4C enables the business
partner search based on the telephone
number.
Once accepted, the actual outbound call
is made.
When finished, agent uses the CDT
scripting to classify the callback result.
SAP Contact Center Customer
CBR Queue
Agent selection CBR Call
Call to
customer service Queue selection
CBR IVR
Callbacks
7. Agent classifies the
success of the callback
event using CDT scripting
6. Call back to customer
4. Call data is passed to
SAP Cloud UI using
SAP Cloud CTI Adapter
5. SAP Cloud UI screen pop-up based on
call data (e.g. caller or called number
or customer entered ID in IVR service)
Internet SAP Cloud for
Sales and /or
Service
Callback
form
SAP Cloud for
Sales or Service UI
2014 SAP AG or an SAP affiliate company. All rights reserved. 6 Public
Customer can leave a callback request by phone or via web
Customer
PSTN Internet
Call queue
Option to
leave callback
Callback IVR
OII
Callbacks
Callback
queue(s)
Web
server
Callback
form
Agent
Call
Callback
Call to
Customer
Customer clicks call me now or callback link / button on corporate web pages.
The callback form opens. Customer enters his phone
number and other relevant information and submits the
callback.
The callback can be an immediate callback or it can
contain a time and date for the wished callback time.
The callback request is checked and entered to the SAP
Contact Center Callback db.
SAP Contact Center callback dialer monitors the Callback
db and activates the callbacks based on callback
schedule.
The callback request is routed to available and skilled
agents thru queue(s).
When agent accepts the callback request, the actual
outbound call is made.
Agent handles the contact and classifies the callback
request as handled.
If customer is not reached, agent can classify the callback
request accordingly, and the callback request will remain
in the db until the next callback attempt.
Customer calls the customer service. Depending on the
queue configuration, the system offers a possibility to
leave a callback request instead of queuing.
The callback request is received in Callback IVR. The
pre-built callback can be used, or alternatively the
organization can decide to build an own Callback IVR
with own prompts and voice.
Typically the IVR based callback is immediate, however,
the IVR can be configured so that it also asks when the
callback should be made.
The callback request is entered to the SAP Contact
Center Callback db.
SAP Contact Center callback dialer monitors the Callback
db and activates the callbacks based on callback
schedule.
The callback request is routed to available and skilled
agents thru queue(s).
When agent accepts the callback request, the actual
outbound call is made.
Agent handles the contact and classifies the callback
request as handled.
If customer is not reached, agent can classify the callback
request accordingly, and the callback request will remain
in the db until the next callback attempt.
2014 SAP AG or an SAP affiliate company. All rights reserved. 7 Public
Customer can leave a callback request by phone or via web
Customer clicks call me now or callback link / button on corporate web pages.
The callback form opens. Customer enters his phone
number and other relevant information and submits the
callback.
The callback can be an immediate callback or it can
contain a time and date for the wished callback time.
The callback request is checked and entered to the SAP
Contact Center Callback db.
SAP Contact Center callback dialer monitors the Callback
db and activates the callbacks based on callback
schedule.
The callback request is routed to available and skilled
agents thru queue(s).
When agent accepts the callback request, the actual
outbound call is made.
Agent handles the contact and classifies the callback
request as handled.
If customer is not reached, agent can classify the callback
request accordingly, and the callback request will remain
in the db until the next callback attempt.
Customer calls the customer service. Depending on the
queue configuration, the system offers a possibility to
leave a callback request instead of queuing.
The callback request is received in Callback IVR. The
pre-built callback can be used, or alternatively the
organization can decide to build an own Callback IVR
with own prompts and voice.
Typically the IVR based callback is immediate, however,
the IVR can be configured so that it also asks when the
callback should be made.
The callback request is entered to the SAP Contact
Center Callback db.
SAP Contact Center callback dialer monitors the Callback
db and activates the callbacks based on callback
schedule.
The callback request is routed to available and skilled
agents thru queue(s).
When agent accepts the callback request, the actual
outbound call is made.
Agent handles the contact and classifies the callback
request as handled.
If customer is not reached, agent can classify the callback
request accordingly, and the callback request will remain
in the db until the next callback attempt.
Customer
PSTN Internet
Call queue
Option to
leave callback
Callback IVR
OII
Callbacks
Callback
queue(s)
Web
server
Callback
form
Agent
Call
Callback
Call to
Customer
2014 SAP AG or an SAP affiliate company. All rights reserved. 8 Public
Customer can leave a callback request by phone or via web
Customer clicks call me now or callback link / button on corporate web pages.
The callback form opens. Customer enters his phone
number and other relevant information and submits the
callback.
The callback can be an immediate callback or it can
contain a time and date for the wished callback time.
The callback request is checked and entered to the SAP
Contact Center Callback db.
SAP Contact Center callback dialer monitors the Callback
db and activates the callbacks based on callback
schedule.
The callback request is routed to available and skilled
agents thru queue(s).
When agent accepts the callback request, the actual
outbound call is made.
Agent handles the contact and classifies the callback
request as handled.
If customer is not reached, agent can classify the callback
request accordingly, and the callback request will remain
in the db until the next callback attempt.
Customer calls the customer service. Depending on the
queue configuration, the system offers a possibility to
leave a callback request instead of queuing.
The callback request is received in Callback IVR. The
pre-built callback can be used, or alternatively the
organization can decide to build an own Callback IVR
with own prompts and voice.
Typically the IVR based callback is immediate, however,
the IVR can be configured so that it also asks when the
callback should be made.
The callback request is entered to the SAP Contact
Center Callback db.
SAP Contact Center callback dialer monitors the Callback
db and activates the callbacks based on callback
schedule.
The callback request is routed to available and skilled
agents thru queue(s).
When agent accepts the callback request, the actual
outbound call is made.
Agent handles the contact and classifies the callback
request as handled.
If customer is not reached, agent can classify the callback
request accordingly, and the callback request will remain
in the db until the next callback attempt.
Customer
PSTN Internet
Call queue
Option to
leave callback
Callback IVR
OII
Callbacks
Callback
queue(s)
Web
server
Callback
form
Agent
Call
Callback
Call to
Customer
2014 SAP AG or an SAP affiliate company. All rights reserved.
Thank you
2014 SAP AG or an SAP affiliate company. All rights reserved. 10 Public
2014 SAP AG or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG (or an SAP affiliate
company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP AG or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP AG or its
affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP AG or SAP affiliate company products and services
are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an
additional warranty.
In particular, SAP AG or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or
release any functionality mentioned therein. This document, or any related presentation, and SAP AGs or its affiliated companies strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP AG or its affiliated companies at any time for
any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-
looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place
undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.
2014 SAP AG or an SAP affiliate company. All rights reserved. 11 Public
2014 SAP AG oder ein SAP-Konzernunternehmen. Alle Rechte vorbehalten.
Weitergabe und Vervielfltigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrckliche schriftliche Genehmigung durch SAP AG oder ein SAP-Konzernunternehmen nicht gestattet.
SAP und andere in diesem Dokument erwhnte Produkte und Dienstleistungen von SAP sowie die dazugehrigen Logos sind Marken oder eingetragene Marken der SAP AG (oder von einem SAP-Konzernunternehmen) in Deutschland und verschiedenen anderen Lndern weltweit. Weitere Hinweise und Informationen zum Markenrecht finden Sie unter http://global.sap.com/corporate-de/legal/copyright/index.epx.
Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte knnen Softwarekomponenten auch anderer Softwarehersteller enthalten.
Produkte knnen lnderspezifische Unterschiede aufweisen.
Die vorliegenden Unterlagen werden von der SAP AG oder einem SAP-Konzernunternehmen bereitgestellt und dienen ausschlielich zu Informationszwecken. Die SAP AG oder ihre Konzernunternehmen bernehmen keinerlei Haftung oder Gewhrleistung fr Fehler oder Unvollstndigkeiten in dieser Publikation. Die SAP AG oder ein SAP-Konzernunternehmen steht lediglich fr Produkte und Dienstleistungen nach der Magabe ein, die in der Vereinbarung ber die jeweiligen Produkte und Dienstleistungen ausdrcklich geregelt ist. Keine der hierin enthaltenen Informationen ist als zustzliche Garantie zu interpretieren.
Insbesondere sind die SAP AG oder ihre Konzernunternehmen in keiner Weise verpflichtet, in dieser Publikation oder einer zugehrigen Prsentation dargestellte Geschftsablufe zu verfolgen oder hierin wiedergegebene Funktionen zu entwickeln oder zu verffentlichen. Diese Publikation oder eine zugehrige Prsentation, die Strategie und etwaige knftige Entwicklungen, Produkte und/oder Plattformen der SAP AG oder ihrer Konzernunternehmen knnen von der SAP AG oder ihren Konzernunternehmen jederzeit und ohne Angabe von Grnden unangekndigt gendert werden. Die in dieser Publikation enthaltenen Informationen stellen keine Zusage, kein Versprechen und keine rechtliche Verpflichtung zur Lieferung von Material, Code oder
Funktionen dar. Smtliche vorausschauenden Aussagen unterliegen unterschiedlichen Risiken und Unsicherheiten, durch die die tatschlichen Ergebnisse von den Erwartungen abweichen knnen. Die vorausschauenden Aussagen geben die Sicht zu dem Zeitpunkt wieder, zu dem sie gettigt wurden. Dem Leser wird empfohlen, diesen Aussagen kein bertriebenes Vertrauen zu schenken und sich bei Kaufentscheidungen nicht auf sie zu sttzen.