GS Departments Articles

How to manage customer queue time upon manual reassignment

Tell Digital DX how to place customers into the queue when they are reassigned by an agent rather than automatically. You can set this option independently for customers reassigned within a department as opposed to between departments.

  1. Create or edit a department, as follows:
    1. In the Web Admin Center, go to Organization > Departments. The Department Management page is displayed.
    2. Select an existing department or click Create New.

    Result: The New/Edit Department page is displayed.

  2. On the Automatic Distribution tab, choose a channel and click Override account-level distribution settings.
  3. Under Manual Reassignment, set how you want to handle transfers From the same department.

    Result:

    Move to end of queue (time is reset) Place customers at the end of the queue regardless of how long they have been waiting.
    Maintain place in queue (time is preserved) Place customers in queue based on time already spent waiting.
  4. Similarly, set how you want to handle transfers From other departments.
  5. Repeat this procedure for each channel, as required.
  6. Save your changes.

How to send chats to a rollover department

When no agents are available in the original department, agents of rollover departments take over incoming chats.

For example, Sales goes offline at 5pm, but Customer Support stays online. You set Customer Support as the rollover department for Sales. As a result, the Sales chat button is displayed as available whenever either a Sales or Customer Support agent is logged in.

Important: Chats are not assigned to the rollover department, only the original department's membership is expanded with the agents of the rollover department. The original department keeps ownership of the work item.

Rollover departments are set when creating or editing a department.

  1. Create or edit a department, as follows:
    1. In the Web Admin Center, go to Organization > Departments. The Department Management page is displayed.
    2. Select an existing department or click Create New.

    Result: The New/Edit Department page is displayed.

  2. On the Rollover departments tab, select a department.

    Result: The selected department is displayed in the table at the top of the screen.

  3. Under Rank, define the order in which the rollover department will receive rollover items.
  4. Save your changes.

How to create a department

Create a department as part of your chat distribution strategy.

  1. In the Web Admin Center, click Organization > Departments.
  2. On the Department Management page, click Create New.
  3. Enter a Name.

    When the pre-chat form includes the Department field, this name can be seen by customers.

  4. Under Language, associate the department with languages to route chats to agents with appropriate language skills.
  5. You can also set department-level business hours.

    See How to set department-level business hours.

  6. Save your changes.

How to set department-level business hours

Department-level business hours allow you to control the times, days, dates, and circumstances under which chat with a department is available.

Department-level business hours and exceptions override website-level business hours and exceptions respectively. Departments without unique business hours and/or exceptions use the same settings as associated websites.

A department cannot receive new chats outside of business hours; neither when agents are available nor when a rollover department has been selected. You may change this default behavior as described below.

  1. Create or edit a department, as follows:
    1. In the Web Admin Center, go to Organization > Departments. The Department Management page is displayed.
    2. Select an existing department or click Create New.

    Result: The New/Edit Department page is displayed.

  2. On the Department Information tab under Department Hours, select Enable business hours for chats.
  3. Optionally, to make chat buttons available within business hours even when no agents are available, select Ignore Agent Status.

    Result:

    Important: This may result in unanswered chats. Chats may continue to be queued even when no agents are available.
  4. Select the Timezone used by the business hours settings.
  5. Set your Business Hours, which are periods of time (day/time combinations) that reflect your regular hours of operation.
    1. Select the hours between which you want chat to be potentially available.

      Outside of this time period, your chat buttons display as unavailable even when agents are available. For example, if business hours are set for 9:00 AM to 5:00 PM, the Chat button associated with this website reference will become available at 9:00 AM (if agents are available) and will be disabled at 5:00 PM.

    2. Select the Days to which the From/To setting is applied.
    3. To set unique hours for the weekend (or any day of the week), click Add business hours and set the days and time as described above.

    Result: Outside of these time periods, chat is unavailable unless you set exceptions.

  6. To alter your Business Hours (opening hours) on specific dates throughout the year, such as holidays or for special events, you can add exceptions under Exceptions by date. See What are exceptions to business hours? below.
    • Same as website exceptions. The department uses the same exceptions as associated websites.
    • Override website exceptions on specific dates. On the dates specified here, department exceptions override website exceptions. Otherwise, the department uses the same exceptions as associated websites.
    • Override all website exceptions. The department uses unique exceptions and ignores all website exceptions.

    Result:

    Tip: When adding exceptions, you may find it useful to copy previously used exceptions (when available). To see these exceptions, select the Show previously expired exceptions from option.
  7. Save your changes.

What are exceptions to business hours?

An exception is valid for one day only. By defining an exception, you override normal business hours. In other words, an exception defines the time when your agents are available to chat on a specific day.

Think of a business hours exception as an exception in your daily routine: You may provide support from 9 AM to 5 PM, but on an exceptional day, like Black Friday, you may want to provide chat support for longer hours. In this case, you can define an exception for that single day by defining your availability, say, from 9 AM to 9 PM.

Similarly, if you have a meeting on November 20, from 2 PM to 3.30 PM and you are not available to support your customers, you have to change your standard business hours by setting two exceptions for the day:

  • One exception for November 20 from 9 AM to 2 PM
  • Another one for November 20 from 3.30 PM to 5 PM

This way, you can let Digital DX- and your customers - know that this is an exceptional day when you are available from 9 AM to 2 PM and from 3.30 PM to 5 PM only.

Department management

Departments are used to group agents and distribute chats.

How do departments relate to other Bold360 entities?

Departments can be associated with the following items:

  • Agents, who can be grouped in multiple departments
  • Chat Button (chats initiated from a button can be routed to a specific department)
  • Chat Window pre-chat form (customers can select a department to facilitate routing to a specific department)
  • Rules (when a chat triggers a rule, the chat is routed to a specific department)
  • Other departments as Rollover Departments

What is controlled by the department definition?

The department definition controls the following:

  • How agents are grouped
  • How chats are distributed, including the ability to override Automatic Distribution settings at the department level
  • Departments can also be associated with a specific language to help route chats to agents with appropriate language skills

Announcements

Bold360 21.10 Release Notes

Bold360 21.10 release notes

Bold360 version 21.10 contains the following new enhancements:

Enforcing HTTPS and removing HTTP across widget scripts

Going forward, there will no longer be an option to choose (non-secure) HTTP-only connections when generating widget touchpoint scripts. HTTPS will be enforced across all touchpoints going forward and HTTP-only widget configurations will no longer be supported as of December 31, 2021. Any widget script using HTTP only will need to be changed by this date in order to continue uninterrupted

Access to the Genesys DX AI management (*.nanorep.co) will only be accessible through HTTPs

In-product announcements will be present to raise awareness of this change

Important: Any widget script using HTTP only will need to be changed by this date in order to continue uninterrupted.

In-Product Rebranding

As part of the transformation to Genesys DX, the product interfaces are now rebranded to reflect this change. Logos, product names, and company links are now updated to Genesys branding and is present within each of the product interfaces.

getEstimatedWaitTime API call

Using the "getEstimatedWaitTime" API call will provide the estimated wait time that the visitor would spend waiting before starting a live chat with an agent.

Details on using this API can be located in this article.

Bold360 21.11 Release Notes

Bold360 version 21.11 contains the following new enhancements:

New KB Launchpad Intent Library for COVID-19/Vaccinations

In order to help businesses with providing just-in-time information related to updates to COVID-19 and vaccination protocols, a new entry in the KB Launchpad is now available with intents that can be used to deploy knowledge to keep your workforce informed of new policies and information that you may need to enforce.

Not familiar with the KB Launchpad? The KB Launchpad contains pre-defined intent libraries to help you add industry and use-case specific questions/intents to your KBs with your own specific responses to help with adding commonly asked questions for newly created KBs.

We will be enabling the KB Launchpad as a default setup option on all accounts shortly but contact your Account or Success Manager to get it enabled early if necessary.

ICO Cookie Compliance

In order to support ICO cookie compliance in regions that require end-user consent for allowing cookies to be set, Genesys DX now complies with this standard by making the tracking and analytics related cookies that are set through the touchpoint and visitor monitoring HTML snippets to be optional.

By default, all cookies will continue to be set upon page load. To restrict these cookies from loading automatically and only upon end-user consent, additional steps will be required on the website that the Genesys DX code is being deployed to.

You can learn more about what this compliance is and how to update your Genesys DX deployment to be compliant by reviewing the details in this article: ICO Cookie Compliance.