Case study · Digital security

A global digital security provider: from Bold360 to Genesys Cloud CX and Salesforce

A global provider of digital identity and security services ran its online support on Bold360, which Genesys was retiring. QVCCS rebuilt the whole experience on Genesys Cloud CX, with deep Salesforce integration and capabilities the old platform never had, for a team of fifteen.

At a glance

Client
Global digital identity and security provider
Sector
Digital security
Where
UK
When
2024
Users
15 concurrent
Licence
Genesys Cloud CX 3
Duration
6 months
Engagement
On behalf of a UK Genesys reseller partner

01

The challenge

The client's customers, many of them technical buyers of security products, relied on its web chat for help with orders, accounts and certificates. That chat ran on Bold360, which Genesys acquired in 2021, rebranded as Genesys DX, and then announced would reach end of life on 31 January 2024. A working, well-tuned service had to move to a new platform, with its full configuration and logic reimplemented rather than copied.

Parity was only the starting point. The client wanted enhanced reporting, quality management with full multi-monitor screen recording, a richer agent desktop, chatbots, knowledge, and a deep integration with Salesforce that created a properly populated case for every chatbot conversation. It also wanted to keep a feature its customers valued: the option to receive a transcript of their chat at the end of the session.

02

What QVCCS did

Working on behalf of a UK Genesys reseller partner, QVCCS designed and delivered the replacement on Genesys Cloud CX 3, running the full engagement with an enterprise mandate despite a team of fifteen concurrent users. Every part of the Bold360 behaviour was mapped to a Genesys Cloud equivalent or to a new design, and the gaps were closed with configuration or custom engineering.

  1. A new Messenger configuration and deployment on the client's website
  2. Digital bot flows built in Architect, with knowledge articles to answer common questions
  3. Agent scripts providing a screen pop with the customer's context
  4. A Salesforce integration creating a new case for every chatbot interaction
  5. Custom attributes, such as the visitor's location, passed from the website with the Messenger Database plugin
  6. A custom option for customers to receive a transcript of their chat when it ends
  7. Quality management, multi-monitor screen recording and an agent-offered CSAT survey
  8. Single sign-on and SCIM provisioning with Microsoft Entra ID, formerly Azure Active Directory

03

The solution

Customers start in Messenger, where a digital bot flow greets them, answers what it can from knowledge articles and gathers what an agent will need. For every chatbot interaction, a new Salesforce case is created automatically, populated with the region, language, case origin, status, contact name, email address and the order number or other reference. Custom attributes set on the website, such as the visitor's location, travel with the conversation into that case.

Genesys Predictive Engagement gives agents a live view of who is on the website now, which segments each visitor matches, and action maps based on their behaviour, so the team can see who may need help before they ask. When a conversation reaches an agent, the script opens with the customer's context; at the end, the agent can offer a satisfaction survey, and the customer can choose to receive a transcript, a capability built specially because it is not available out of the box with Genesys web messaging.

Behind the agent desktop, every interaction is recorded, including full multi-monitor screen recording, and evaluated through quality management, with enhanced reporting on top. Agents sign in through Microsoft Entra ID, and SCIM keeps users and group memberships in step with the client's identity platform.

A digital security provider's web chat rebuilt on Genesys Cloud CX with Salesforce On the left, website visitors reach Messenger, which carries custom attributes such as their location, while Genesys Predictive Engagement shows agents who is on the site now, their segments and action maps. In the middle, Genesys Cloud CX 3: a digital bot flow with knowledge articles, fifteen concurrent agents whose scripts pop the customer's context, chat transcripts on request and an agent-offered CSAT survey, and quality management with multi-monitor screen recording and reporting. On the right, Salesforce receives a new, populated case for every chatbot interaction, and Microsoft Entra ID provides single sign-on and SCIM provisioning. WEBSITE VISITORS Online support Messengerwith custom attributes Predictive EngagementLive now, segmentsand action maps Replaces Bold360, which reached end of life in 2024 GENESYS CLOUD CX 3 Bot, team and controls Digital bot flowKnowledge articles, details captured 15 concurrent agentsScripts pop the customer's context Transcript on request · CSAT survey Quality · multi-monitor recording · reports CLIENT PLATFORMS Records and identity SalesforceA new case for everychatbot interaction Region, language, origin, status, contact, email and order number Microsoft Entra IDSingle sign-on and SCIM Fifteen users, a full enterprise design: bots, Salesforce cases, custom transcripts, recording and identity.
Messenger and a bot feed every chat into a new Salesforce case, with Predictive Engagement, transcripts and recording around the agent.

04

Results

The migration was successful, and was completed on time and on budget despite its inherent complexity. The client moved off a retiring platform with its customer experience intact, and gained a Salesforce-integrated, fully recorded and measured digital service that does considerably more than the one it replaced.

  • Bold360 web chat rebuilt on Genesys Cloud CX before end of life
  • A fully populated Salesforce case for every chatbot interaction
  • Chat transcripts on request, built where no standard feature existed
  • Predictive Engagement, quality management, screen recording and CSAT in daily use

05

Why it worked

This is one more clear example that agent count has little to do with the maturity of a solution or the depth of its requirements. Fifteen concurrent users needed bots, knowledge, Salesforce case automation, custom engineering, Predictive Engagement, recording, quality, single sign-on and identity provisioning, each designed and tested properly. Treating the project by its requirements rather than its size, and aligning client, reseller and delivery team throughout, is what delivered it on time and on budget.

Last reviewed

We work by introduction

Clients, partners and people introduced to us can reach the right specialist directly.

Who to contact