You already bought Genesys Cloud. Managed services is how you get the most out of that investment.
The right partner keeps three things aligned: your business outcomes, what your customers expect, and where Genesys is taking the platform.
That third one moves on its own schedule. Genesys releases new features weekly, your business keeps moving, and without someone connecting the two, your environment drifts away from both.
Put three managed services proposals side by side and they will look the same. Platform administration. Incident response. Reporting support. Business reviews. Two tiers, maybe three. The service catalog is not the decision. Every partner can write that list.
The decision is the partner.
Evaluate a Genesys managed services partner on ten things: platform focus, who answers your call, where their people work and whether they are employees, which certifications those people hold, service levels in writing, how long their clients stay, how clearly they separate covered work from projects, whether they keep you aligned with the Genesys roadmap, what their business reviews cover and how often, and how easily you can flex or leave. The service catalog will look the same across every proposal. These ten will not.
Just as important as choosing an implementation partner
Buyers spend months selecting an implementation partner and an afternoon selecting a managed services partner. The second decision deserves the same rigor.
An implementation is a project. It has a start, an end, and a deliverable you can judge within months. Managed services runs for years, and it is where the value of the platform is either realized or quietly left on the table. Every feature you paid for and never configured, every routing rule that no longer matches the business, every Genesys capability released after you went live, all of it lives in this relationship.
Can it be the same partner?
Yes, and often it should be. The team that designed and built your environment already knows why every queue and flow works the way it does. That knowledge is worth a lot on day two, and keeping it is the simplest path.
The case for a different partner is equally clear: if the implementation went badly, there is no reason to assume support will go better. A missed timeline, a design built from a demo rather than your business, or a team that disappeared at cutover are all reasons to evaluate the market rather than default to renewal.
Either way, evaluate. Defaulting because it is easier is how organizations end up three years into a relationship nobody would choose again.
Related: How to Choose a Genesys Implementation Partner
The ten things to evaluate
1. Is Genesys Cloud their focus, or one of many platforms?
Many partners sell several contact center platforms. That breadth is sometimes useful before you choose a platform. After you have chosen, it means your environment competes for attention with four other products.
Ask what share of their business is Genesys Cloud, and whether the people supporting you work on anything else.
AskWhat percentage of your business is Genesys Cloud? Do the engineers on our account work on other platforms?
2. Who answers, and do they already know your environment?
A shared pool looks faster on paper and is slower in practice, because every ticket starts with you explaining how your routing works. That explanation is your time, and it never appears on an invoice.
The strongest answer is a named team that already knows why your queues are built the way they are. The next strongest is a named team that invests in learning it up front.
AskWho will answer when we call? Is it a named team or a queue? Will they have seen our environment before the first ticket?
3. Where are the people, and are they employees?
Two separate questions, often blurred together.
Location affects how fast decisions happen. A twelve hour gap turns a ten minute question into a next day answer. In regulated industries, data handling and access need their own review.
Employment affects what happens to knowledge. Contractors are assembled per engagement, and what they learned about your environment leaves when they do. Subcontracted delivery means the company you signed with is not the company doing the work.
AskAre the engineers on our account full time employees? Do you subcontract any part of delivery?
4. Which certifications do the people on your account hold?
Most partners quote a company certification count. That number tells you nothing about who is on your account.
Ask which certifications your assigned engineers hold, and in which areas. Support requests do not arrive sorted by discipline. A workforce management question on Tuesday and an outbound compliance question on Wednesday should reach someone who knows the answer, not someone who has to go find out.
Breadth matters more than count here: routing and Architect, workforce management, quality, outbound, analytics, and AI.
AskName the engineers on our account and list their current Genesys Cloud certifications. When were they last updated?
5. Are the service levels in writing, by severity?
Every proposal lists response times. Fewer put them in the agreement.
Two things matter. First, whether the targets are contractual or a statement of intent. Second, how each severity level is defined, because a partner who defines the top severity narrowly can report excellent response times and still leave your urgent request in a queue.
Ask to see the definitions, not just the numbers. Then ask who decides which severity a request receives, you or them.
Coverage hours matter as much as the target. A four hour response means something different at 9am Tuesday than at 6pm Friday if the agreement only covers business hours.
AskAre these targets contractual? How is each severity defined, and who assigns it? What hours are covered, and what happens when a target is missed?
6. Do their clients stay?
This is the question buyers almost never ask, and it tells you more than any reference call.
Winning a client and keeping one are different skills. Plenty of partners are good at the first. A partner whose clients stay for a decade is telling you something no proposal can: that the value kept showing up after the contract was signed.
Ask for the numbers. Client retention rate. Average length of client relationship. How many clients they have lost in the last two years and why. A partner who tracks customer lifetime value will have these ready. A partner who does not will change the subject.
Then ask for a reference who has been with them more than three years. Any partner can produce a happy customer from a project that closed last quarter.
AskWhat is your client retention rate? What is your average client relationship length? Can I speak with a customer who has been with you more than three years?
7. Is the line between covered work and projects written down?
This is the single most common source of friction in a support relationship, and it is entirely preventable before signing.
Do not accept categories. Ask for five examples of work that is covered and five that would be quoted as a project. If a partner cannot produce ten examples in a meeting, they have not thought about it, and you will be the one discovering the line.
A workable rule, and one you can hold a partner to: if it is a daily task or change, it is covered. If it is a new build or integration, it is a project with a statement of work, quoted up front.
| Should be covered | Reasonably a project |
|---|---|
| Add or remove agents and skills | A new department, queue set, or digital channel |
| Update routing or IVR prompts | Custom integrations with CRM, APIs, or databases |
| Modify wrap up codes and templates | Secure payment or compliance workflows |
| Add queues or adjust overflow logic | Custom reporting and analytics builds |
| Update existing flows or recordings | New modules such as WFM, QA, Agent Assist, or Gamification |
| Configuration tuning and minor changes | Infrastructure or staging environment changes |
AskGive me five examples of covered work and five you would quote as a project. What rate applies to project work, and is there a discount?
8. Do they keep you aligned with the Genesys roadmap?
Genesys Cloud updates continuously. Nothing for you to install, nothing to schedule. That is one less thing to manage, and it creates a different problem.
Genesys publishes release notes every week. Nobody on your team has time to read all of that, and most of it will not apply to you. But some of it will, and the ones that matter look exactly like the ones that do not unless someone reading them knows your configuration.
Three things happen when nobody is doing that reading:
- You pay for capability you never turn on. Features arrive inside a tier you already license, and they sit there.
- Your environment drifts. Routing built three years ago still runs, while better ways to do it shipped eighteen months ago.
- Decisions get made on old information. Something you evaluated and rejected in 2024 may have changed twice since.
A reactive partner waits for your ticket. A partner maximizing your investment does four things:
- Translates the roadmap for your environment. Not a release note forward. What changed, whether it affects you, and what is worth turning on.
- Reviews what you own and do not use. Capability inside a tier you pay for every month that was never configured.
- Reviews licensing. Seats assigned to people who moved on, or tiers higher than the role needs.
- Maintains AI and outbound. If you run a virtual agent or outbound campaigns, tuning and compliance upkeep are ongoing work. Make sure they sit inside the agreement.
AskGenesys publishes release notes every week. How do you decide which of those matter to us, and how do we hear about them?
One useful test: ask whether the partner does this work in public. A partner who publishes a regular summary of Genesys releases is already doing the reading, and you can judge the quality before you sign anything. VDS publishes Genesys release note highlights every release cycle, free to anyone, client or not.
9. Are business reviews included, and how often?
Start with the simplest question: are reviews part of the agreement, or something you have to ask for? Then ask how often. Quarterly, twice a year, and annually produce very different relationships.
Then ask what gets reviewed. A ticket count summary is not a business review. A real one covers what was accomplished since the last one, business outcomes against the KPIs you agreed, Genesys updates and roadmap items that matter to you, how your environment is being used, and what projects come next.
Ask to see a sample agenda from a real review, with the client details removed. A partner who runs these regularly will have one. A partner who does not will offer to build you one.
AskAre business reviews included, and how often? Who attends from your side? Show me a sample agenda.
10. How easy is it to flex, and how easy is it to leave?
A partner should be as easy to fire as they are to hire.
Long lock ins exist to protect partners from losing accounts they are not serving well. A partner who earns the relationship every quarter does not need one.
Flex matters as much as exit. Support needs are not flat. A migration, a new line of business, or a peak season raises the load for a quarter. A quiet stretch lowers it. An agreement that cannot move with your business is priced for the partner, not for you.
What good terms look like:
- A reasonable notice period, and no multi year commitment required to get a fair rate
- The ability to move between tiers as your needs change
- The ability to scale down without a penalty
- Your documentation, configuration notes, and credentials handed back, not held
- No exit fee
AskCan we move between tiers when our needs change? What is the notice period, is there an exit fee, and what do we get back if we leave?
Red flags
Any one of these is worth a direct conversation. Two or more and you should keep looking.
- They forward release notes and call it roadmap guidance. Reading them against your configuration is the job. Forwarding them to you is not.
- They cannot tell you their retention numbers. A partner who does not measure whether clients stay is not managing for it.
- They quote from your agent count alone. Support work is driven by how often your environment changes, not by how many seats you have. A quote built on headcount has not been scoped.
- Scope is written in categories. "Administration and support" is not scope.
- They will not name the people. Unwillingness to name your assigned engineers usually means they do not know yet.
- Certifications are quoted at the company level only. Ask about your account. If the answer stays at company level, that is the answer.
- Service levels have no consequence. Targets nobody is accountable for are marketing.
- Everything is included. No partner covers everything. A proposal that claims it has either not defined the boundary or plans to define it later, when you have less leverage.
- The agreement is long and the exit is hard. A three year term with a punitive exit tells you how confident they are that you would stay otherwise.
- They will not connect you with a customer past year one. Any partner can produce a happy reference from a project that just closed.
The scorecard
Score each partner from 1 to 5. Use it as written or adapt it.
| Criterion | What a 5 looks like | Score |
|---|---|---|
| Platform focus | Genesys Cloud is the focus. Your engineers do not split across platforms. | |
| Who answers | A named team that already knows your environment. | |
| People | Full time employees, based where your decisions happen, no subcontracting. | |
| Certifications | Named engineers, current certifications, breadth across routing, WFM, outbound, analytics, and AI. | |
| Service levels | Contractual targets by severity, clear definitions, stated coverage hours. | |
| Client retention | Retention and tenure numbers offered without hesitation, plus a reference past year three. | |
| Scope clarity | Five examples each side of the covered and project line, in writing. | |
| Roadmap alignment | Weekly Genesys releases filtered down to what matters for your environment, plus license and usage review. Bonus if they publish release summaries you can read before you sign. | |
| Business reviews | Included, quarterly, tied to your KPIs, with a sample agenda you have seen. | |
| Flex and exit | Move tiers as needs change, short notice period, no exit fee, documentation returned. |
If one proposal is far cheaper, find the row where it scores low. There is always one.
Already have a partner and considering a change?
A bad implementation is a legitimate reason to change for day two. So is a partner who went quiet after launch. Neither requires you to start over on the platform.
Switching does not mean reimplementing. Your Genesys Cloud organization, configuration, and data stay in place. What changes is who supports it.
The best time to evaluate is 90 to 120 days before your renewal, while you still have leverage and time to run a real process.
Related: How to Change Your Genesys Partner of Record
Related: Your Genesys Partner Disappeared After Go Live. Here Is What to Do.
How VDS answers these ten questions
It would be strange to publish this list without answering it ourselves.
| Criterion | VDS |
|---|---|
| Platform focus | Genesys Cloud is the only platform we implement and support. |
| Who answers | A group of Technical Account Engineers aligned to your account, reachable by email or phone. The engineers who implement your environment stay to support it. |
| People | Full time employees, all based in the US. We do not subcontract implementation or managed services delivery. |
| Certifications | Every engineer is a certified Genesys Cloud Professional. The team also holds Genesys Cloud Developer and Specialist certifications across Architect, workforce management, scripting, quality management, outbound, and speech and text analytics, plus AI certifications. |
| Service levels | Published and applied to both tiers: 30 minutes for Priority 1, 4 hours for Priority 2, 2 business days for MACD. Coverage 24 hours a day, 7 days a week, 365 days a year. |
| Client retention | We manage to customer lifetime value. The goal is not to win a client, it is to keep them for twenty years, and clients stay because value keeps arriving. |
| Scope clarity | Published. Daily tasks and changes are covered. New builds and integrations are projects, quoted up front, with a 10% professional services discount on Platinum and 30% on Platinum+. |
| Roadmap alignment | We read the weekly Genesys releases so you do not have to. We publish Genesys release note highlights, free and open to anyone, and for clients we go further: which of those features matter to your configuration and what is worth turning on. Release guidance, roadmap planning, and feature ideation are on both tiers. Platinum+ adds admin and supervisor coaching, WEM guidance, and an AI optimization roadmap. |
| Business reviews | Included on both tiers. Twice a year on Platinum, quarterly on Platinum+, tied to your KPIs. Each review covers what we accomplished, business outcomes, Genesys updates and roadmap, usage review, and projects. |
| Flex and exit | Move between Platinum and Platinum+ as your needs change, and scale down if your needs shrink. We think a partner should be as easy to fire as they are to hire. |
See the full offering: Genesys Cloud managed services
Frequently asked questions
What should I look for in a Genesys managed services partner?
Platform focus, who answers your call and whether they know your environment, whether the people are full time employees and where they work, which certifications your assigned engineers hold, service levels in writing by severity, whether their clients stay, a written line between covered work and projects, whether they keep you aligned with the Genesys roadmap, whether business reviews are included and how often, and how easily you can flex or leave.
What questions should I ask a Genesys partner before signing a support agreement?
Ask who will answer when you call, whether those engineers are full time employees, which certifications they hold, whether service levels are contractual and how severity is defined, what their client retention rate is, for five examples each of covered work and project work, what they bring you in a month when you open no tickets, whether business reviews are included and how often, and what the notice period and exit terms are.
Does my Genesys managed services partner have to be the one who implemented our system?
No. Your configuration and data stay in place regardless. Many customers move support to a different partner, often at renewal, without reimplementing anything.
Should my managed services partner be the same as my implementation partner?
Often yes. The team that built your environment already knows why every queue and flow works the way it does, and that knowledge is valuable on day two. The case for a different partner is a bad implementation. If the project missed timelines, was designed from a demo rather than your business, or the team disappeared at cutover, evaluate the market rather than default to renewal.
How do I keep up with Genesys Cloud releases?
Genesys publishes release notes weekly at help.genesys.cloud. Reading all of them is more than most teams can absorb, and most items will not apply to your environment. A managed services partner should filter them for you. VDS publishes Genesys release note highlights free to anyone, and for clients goes further by identifying what matters to their specific configuration.
Why does client retention matter when choosing a Genesys partner?
Winning clients and keeping them are different skills. A partner whose clients stay for years is showing you that value kept arriving after the contract was signed. Ask for their retention rate, their average client relationship length, and a reference who has been with them more than three years.
Should a Genesys partner work on other platforms too?
Breadth can help before you choose a platform. After you have chosen, it means your environment competes for attention. Ask what share of their business is Genesys Cloud and whether your engineers work on anything else.
How long should a Genesys managed services agreement be?
Long enough for the partner to learn your environment, short enough that they have to keep earning it. Look for a reasonable notice period rather than a multi year lock in, the ability to move between tiers, and no exit fee.
What is the difference between Genesys support and a partner managed services agreement?
Genesys supports the platform itself. If Genesys Cloud is down, that is Genesys. If your routing, reporting, or configuration is wrong, that is your environment, and your partner handles it.
When is the best time to evaluate a new Genesys partner?
Around 90 to 120 days before renewal, while you still have leverage and time to run a real process.
Talk to us, or use the scorecard on someone else
VDS is a Genesys Cloud Elite Partner based in Grand Rapids, Michigan, and a back to back Genesys Mid-Market Partner of the Year. Genesys Cloud is the only platform we implement and support.
If you are evaluating partners, take the scorecard and use it on all of them, including us.
Talk to a Genesys Cloud expert
Not sure what shape your environment is in before you start? A Genesys Cloud health check gives you findings you keep, whoever you hire.
And if you want to see how we read the platform before you talk to us, subscribe to our Genesys release note highlights. Free, no commitment, and a fair sample of the work.
About the author
Nick Glimsdahl is a Senior Account Executive at VDS. He has spent more than 30 years in contact center technology, starting with Avaya and Mitel, and specializes in CCaaS, CRM integration, AI implementation, and CX strategy.