Genesys Cloud CX for business and technology services contact centres

An outsourcer may run customer service for twenty brands at once, each with its own contract, processes, reporting and integrations. Running a separate platform for each is expensive and hard to support; running them all together without separation risks one client's team seeing another's data. Genesys Cloud divisions resolve that tension. Genesys explains that a division is a way to group and segregate configuration objects while keeping them in the same organisation, and that roles then grant users access to the divisions they need.

For a North American outsourcer with more than 2,000 seats, we moved over twenty client operations from on-premises Cisco to one Genesys Cloud CX organisation in nine months, a few at a time, with each client operation as its own division. Each client team sees and manages only its own queues, flows and users, while the business runs one platform, one subscription and one set of standards.

When you answer calls, chats and emails on behalf of a client, you are usually processing its customers' personal data on its instructions. The ICO explains that a processor may only process personal data on a controller's instructions, must have a binding contract with the controller, may not engage another processor without the controller's written authorisation, and must protect the data with appropriate technical and organisational measures. It also notes that its guidance is under review following the Data (Use and Access) Act.

Those duties run through the contact centre's design: who can hear which recordings, how long they are kept, which systems each client's data flows into, and how access ends when a contract does. Clients will also look at your suppliers. The National Cyber Security Centre's supply chain guidance sets out twelve principles across four stages, from understanding the risks to continuous improvement, and outsourcers should expect to answer questions shaped by it.

Service businesses live by their tickets, jobs and cases. A caller who already has an open ticket should not have to explain it again, and the agent who owns the work should hear about it first. Genesys Cloud data actions let a flow look the caller up in your ticketing or CRM system during the call, establish what they are entitled to see, and route accordingly. Work automation goes further, turning non-conversational tasks into workitems that Genesys Cloud routes to agents like any other interaction.

For a global healthcare software company, we designed one support solution across every region with a deep Zendesk integration: each caller is identified as a Zendesk contact, told only about the tickets they are entitled to see, and asked whether the call is about one of them, so existing work returns to the people already handling it. For a global digital security provider, every chatbot conversation creates a Salesforce case automatically, populated with what the agent needs.

Field services firms take every kind of contact: customers reporting faults, engineers calling in from site, large accounts chasing jobs, branches rescheduling visits and finance queries about invoices. These usually arrive on dozens of regional, customer-specific and out-of-hours numbers, each needing its own route and treatment, and shared mailboxes that need the same care as the phones.

For a UK field services company, we took 315 agents, more than 20 teams, 89 service numbers, 113 queues and 48 email addresses from a Mitel contact centre to Genesys Cloud CX in 13 weeks, from kickoff to a single big-bang cutover, a month ahead of the contract deadline. Ten business workshops and five technical workshops ran in parallel to compress the design without skipping it.

Migrating a services business is rarely one project. Every client contract, team or region has its own obligations, and each must move without a gap in service. The work that makes it safe is the plan: detailed requirements for every operation, a firm order of events setting which operations move together and what must be true before each one does, and a pattern proven early and repeated.

That is how the outsourcer's twenty client operations moved in waves, and how the healthcare software company's regions followed one another in rapid, back-to-back go-lives once the common design was proven in the first. Our migration checklist sets out the same discipline for any contact centre move.