Support & maintenance

Genesys Cloud support and maintenance is what protects the investment you made in your contact centre once the project team has moved on. Genesys operates the platform as a cloud service, but your solution is more than the platform: it is your telephony, Architect flows, routing, integrations, scripts, reports, permissions and the data that flows between them. When any of those break, customers wait longer, agents lose context and revenue is put at risk. A specialist support partner keeps the whole solution healthy, not only the parts that a vendor support desk can see.

How we support you depends on how you procure, consume and contract Genesys Cloud CX, and who you buy it through. Where you contract support with QVCCS directly, we provide SLA-based support and maintenance covering incident, problem and change management, up to 24x7x365 for mission-critical operations. Our monitoring and alarms watch your flows, integrations and telephony and trigger automated engineer callout, so many faults are being worked on before users report them. Service levels, priorities and escalation routes are agreed in the support model before the first incident, so contact centre leaders get fast recovery and clear communication, and technical teams get engineers who can read a flow, trace a failing data action and explain exactly what happened.

Many organisations buy Genesys Cloud CX with support from Genesys itself, a systems integrator or a managed service provider that runs the service desk and first-line incident management. In that case QVCCS works inside their service delivery model rather than around it. We become the specialist professional services, change and escalation layer, typically through the managed professional services tiers – Bronze, Silver, Gold and Diamond – set out on our Managed Services page, each with a monthly bucket of hours for complex change, release readiness and expert escalation. When we deliver a project, hypercare and warranty end with a warm handover to your provider's support team, backed by the operational handover pack, so first-line support starts with full context and knows when to call us.

Incident management is about restoring service quickly and keeping people informed, whoever holds the first line. Where QVCCS is your support provider, incidents raised by your team or by our monitoring and alarms are triaged against the agreed priorities; where your provider runs the service desk, we take its escalations. Either way our engineers investigate across Genesys Cloud CX and connected systems, using tools such as the Operational Console and Architect replay mode to see what the platform and flows actually did. Where the cause lies with Genesys, the case is raised and managed through the Genesys My Support portal with the technical evidence needed, and we track the Genesys Cloud status page, so you are not coordinating several suppliers during an outage.

Problem management stops incidents repeating. We analyse recurring faults and significant incidents, identify root causes and recommend permanent fixes, whether that is a redesigned flow, a more resilient integration, a permissions correction or a change of process. Change management keeps the platform stable as it evolves. Requests such as new queues, users, prompts, routing rules or integrations are impact-assessed against the as-built design, built to an updated LLD, peer reviewed, tested in a non-production organisation where licensing allows, approved through your change control and released with a rollback plan, and the as-built documentation is updated every time.

Genesys Cloud receives frequent updates, which is one of its strengths: new features arrive continually without upgrade projects. Genesys publishes release notes every Monday, with deprecations listed alongside their announcement and planned removal dates, and separate announcements covering user interface, platform and deprecation updates. Maintenance must keep your configuration in step. QVCCS runs a release readiness review each week, assessing what is changing against your flows, integrations, scripts, reports, telephony and agent experience, and produces a release impact assessment that states what affects you, what to test and what to change, and by when.

Deprecations show why this matters. Genesys has announced end of life for the BYOC Premises Genesys Hardware Solution on 1 June 2027, after which those edge devices become inoperative. A client running that hardware needs the impact identified early, an options analysis, a design, a tested migration and a cut-over runbook, not a surprise in the final month. Our release readiness work turns platform change from a source of anxiety into a planned roadmap, reduces technical debt and makes it easier to adopt new channels, AI and analytics capabilities when your business is ready.

Genesys Cloud faults rarely respect team boundaries, so we muster a support team from our own bench that covers the whole estate. Support Engineers work on a rota sized to the hours you contract, up to 24x7x365. A Solution Architect owns the as-built design, a Senior Developer handles flow, data action and code fixes, an IT Systems, Telecoms & SIP Engineer takes carrier, trunk and call-quality faults, and a Systems Integration Tester regression-tests changes. Managed professional services subscriptions add a named Lead Engineer, Technical Account Manager or Managed Service Delivery Manager according to tier, under our Managed Services Lead. The Senior Platform Practice Lead sets engineering standards and is the technical escalation point, so the right specialist is one call away.

Every support engagement begins with onboarding. If QVCCS built your solution, we already hold the HLD, LLD and handover pack. If we are taking over from another team, our engineers run an existing-org configuration audit, exporting configuration with CX as Code where appropriate, review flows, integrations and telephony, document what they find in as-built form and agree any immediate risks with you. We set up access with least-privilege roles, connect to your service management processes or your provider's service desk, agree priorities, contacts and escalation paths, and write support runbooks so any engineer can act with full context.

Regular health checks keep the platform in good order between incidents. We review unused or duplicated configuration, permission sprawl, flow versions, integration credentials and certificate expiry dates, error trends in the Operational Console, queue and routing design, and recording and retention settings. Each health-check report ranks findings by risk and value. Service reviews then bring together incidents, problems, changes, health findings and upcoming Genesys releases and deprecations, so leaders see how the platform is performing and technical teams see what needs attention next, captured in a continuous-improvement roadmap that we maintain with you.

We also make sure your own people stay in control. Our engineers share what they learn through clear incident reports, knowledge articles and updated runbooks, so your administrators understand the platform better after every case rather than becoming dependent on us. Where we hold the support contract, proactive monitoring and alarms with automated engineer callout mean issues can be worked on before users report them; where your provider holds it, our managed professional services extend into day-to-day administration and complex change. Whether we support you directly or as the specialist partner behind Genesys, a systems integrator or a managed service provider, the commitment is the same: a dependable Genesys Cloud CX solution, maintained by certified people who care about detail.