From Bright Pattern Documentation
< 3.11:Scenario-builder-reference-guide
Revision as of 07:43, 28 July 2016 by Sasha (talk | contribs) (Scenario Example)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
• 3.10 • 3.11 • 3.12 • 3.13 • 3.14 • 3.15 • 3.16 • 3.17 • 3.18

Scenario Example

This section provides a simplified example of a typical scenario for processing of inbound service calls.

Imagine contact center operations of a security equipment company called All Safe. The contact center provides two services: one for product sales and the other for support. Both services are provided within typical business hours and are available in two languages, English and Spanish. The company’s contact center has one general service number and uses interactive voice response for language and service selection before distributing calls to qualified agents. The following resources are configured in the system to support the above operation:

  • services Sales for sales calls, Support for support calls, and General for unqualified calls and general inquiries
  • an auxiliary skill group Languages with skills English and Spanish
  • a team of agents specializing in product sales, associated with services Sales and General, where all agents have the corresponding default service skills, all have the English skill, and some also have the Spanish skill
  • a team of agents specializing in product support, associated with services Support and General, where all agents have the corresponding default service skills, all have the English skill, and some also have the Spanish skill
  • hours of operation (HOP) for the above services
  • an access number that customers will use to call the above services


A simplified scenario for processing of calls made to the above service number may look like this:

  1. First the call arrival time is checked against the contact center operational schedule. If the call arrives outside of the business hours, an announcement is played back prompting the caller to call again during the business hours. The call is then disconnected.
  2. If the call arrives within the business hours, a general greeting is played first.
  3. The caller is prompted to select the language.
  4. Based on the caller’s input, the corresponding language skill is set as one of the agent selection criteria and the language of the subsequent voice prompts is set to match the caller’s preference. If the caller does not provide any input within a timeout, the English language is set for both the language skill and voice prompts.
  5. The caller is prompted to select the service.
  6. Based on the caller’s input, the corresponding service skill is set as one of the agent selection criteria. If the caller does not provide any input within a timeout, the General Service skill is selected.
  7. The call is then queued while the system looks for an available agent who has both selected skills.
  8. As soon as such an agent becomes available, the system delivers the call to the agent extension. (If other calls are waiting for the same skill set, they are distributed to agents in the order of their arrival.)
  9. If the selected agent does not answer, the call is returned to the service queue to wait for the next available agent with the matching skills.


When translated into the ServicePattern scenario language, the above scenario will look like this:


Scenario-guide-image3.png


Once the scenario is defined, a dial-in scenario entry will have to be created in the configuration in order to associate this scenario with the corresponding external access number.


< Previous
< Previous