A permitted customer task completes, with context available for human handover.
See it taking shape ↓
Keep the journey coherent across people and systems.
84% of customers using the agentic experience resolved requests through self service.
Earlier chatbot resolution was 30%.
The named deployment, not a guarantee for other customers.
Selected Genesys Cloud AI with staged automation and workforce plans.
Growing service demand required a different operating approach.
May 2026 Korean announcement; future work stays a plan.
Genesys connects customer intent with controlled actions across people, AI and enterprise systems.
Connect voice and digital channels.
Read customer history and approved knowledge.
Use integrations and configured instructions.
Preserve context and inspect the outcome.
Genesys works at the point where a customer asks an organization to do something. A request might begin on a phone call, in a message, or through a digital service. The difficulty is that an answer often needs customer history, a company policy, an authorized transaction and sometimes a human decision. Genesys Cloud connects voice and digital interactions with routing, workforce operations and AI capabilities. Its current product materials describe a sequence of perceiving context, reasoning, acting, optimizing and governing. That sequence is useful because recognizing a question does not itself complete a task. An agent still needs access to the correct system and a permitted next action. The rental car illustration on the product page shows this distinction: a virtual agent uses loyalty points and booking context to offer a specific transaction. It is an official example of the intended workflow, rather than an independently measured customer result. Signet reads the core proposition as connecting a customer request to a controlled outcome across systems and people.
Agentic Virtual Agent and human assistance perform different jobs. The virtual agent is intended to complete permitted tasks autonomously, while Copilot supplies knowledge and suggested actions to the employee handling an interaction. A business therefore has to decide which customer intentions can be resolved automatically, what information is sufficient, and when a person must take over. Knowledge management helps ground an answer in approved material. AI Studio lets teams configure and manage AI behavior, and the developer platform provides a route to connected applications and data. Signet's reading is that the important unit of design is one customer task with clear completion and escalation conditions. A demonstration that merely sounds fluent does not establish that the account was updated correctly. A useful evaluation would trace the input, permissions, system action and resulting state. This is an interpretation of the product architecture and its control requirements, not a universal implementation recipe promised by Genesys. Specific capabilities still depend on the product package, connected systems and the customer's deployment choices.
Customer stories provide a more concrete view than a broad automation claim. The current Electrolux Group story reports that agentic AI supports more than 65 percent of service demand and reaches complete containment on selected journeys. Those statements have different denominators: support for demand is not the same as autonomous resolution of every request. The September 2026 Riachuelo announcement reports that 84 percent of customers using its agentic experience resolved requests through self service, compared with 30 percent under its earlier chatbot approach. The release also reports customer satisfaction and technology cost improvements for that deployment. These are customer case outcomes, not company-wide guarantees or a controlled comparison of all AI products. Signet reads the practical lesson as defining the population and baseline before using a result in a sales discussion. The candidate should be able to distinguish assistance, containment and completed work. Those distinctions matter when contact center operations, finance and IT review whether a deployment has changed the actual customer journey.
Genesys Cloud is the platform around which the company organizes its customer experience products. Its role is broader than supplying a chatbot. Voice and digital channels connect to routing, customer context, workforce tools and analytics, while AI capabilities operate within that environment. A buyer evaluating the platform may therefore involve contact center leadership, customer operations, IT, security and business owners. Pricing materials describe product editions and AI related consumption, so a candidate should establish the purchased capabilities instead of assuming that every announced feature is included in a basic license. Integrations and the partner ecosystem connect the platform to other enterprise applications. That does not mean every partnership announcement has already produced a generally available integration. Signet reads the platform sale as a decision about how customer work moves between channels and systems. The official interface illustrations show example profiles, conversations and guidance; they are company product visuals, not screenshots of a named customer's live environment or evidence of that customer's performance.
Agentic Virtual Agent is designed for tasks that require more than a static answer. The September announcement says it became generally available in March 2026, clarifying the status of a product first announced in February. AI Studio supports configuring, testing and managing AI, while approved knowledge and instructions shape how a task is handled. Copilot serves a different user: the employee who needs assistance during customer work. The current product illustration shows a suggested recall response alongside a flag for potential churn. It illustrates guidance within a conversation, without proving that the suggested action was executed or that the customer was retained. Signet reads these products as complementary choices in a workflow. Some requests can end with an autonomous action; others should end with an informed employee decision. A technical candidate can demonstrate fit by explaining the boundary, the information handed across it, and how the team would observe mistakes. This reasoning should follow the specific customer's risks and available capabilities rather than a blanket promise of full autonomy.
The September 2 releases describe a wider agentic orchestration architecture, but its pieces have different delivery dates. Contextual Intelligence and AI Control Plane are described as available at the announcement. Navigator is expected in the fourth quarter of fiscal 2027, and Orchestrator in the first quarter of fiscal 2028. On the company's fiscal calendar those are November 2026 through January 2027 and February through April 2027. The virtual agent release describes APT-2, developer tools and Deepgram as available, while ElevenLabs integration is expected during the third fiscal quarter. An October research date alone is not proof that a scheduled feature has shipped. Native voice, A2A and further AI assisted authoring are described as later fourth quarter work. Signet reads this timeline as a sales and implementation discipline: identify the feature required for the customer outcome, then verify its actual availability before building a commitment around it. The future architecture is useful context, but a candidate should still be able to explain a solution using the capabilities that are confirmed now.
Cloud fiscal quarter revenue, including committed amounts and usage, multiplied by four; not total annual revenue. All points are reported as nearly. These are dated disclosures, not a continuous growth record.
| Date | Value | Basis |
|---|---|---|
| 2025-04-30 | $2,100,000,000 USD | Nearly; fiscal quarter end. |
| 2026-01-31 | $2,600,000,000 USD | Nearly; fiscal quarter end. |
| 2026-07-31 | $2,900,000,000 USD | Nearly; fiscal quarter end. |
Genesys
Native platform integration was scheduled separately.
Control functions are available; Navigator and Orchestrator remain later fiscal quarter plans.
Resolution, satisfaction and costs describe its specific deployment.
Genesys is privately held, and the research does not supply a current public market capitalization. Its March 2026 announcement reports nearly three billion dollars of total revenue for fiscal 2026, with thirteen percent growth, and nearly 2.6 billion dollars of Genesys Cloud ARR at the end of January. These figures are related but measure different scopes and periods. The company's ARR definition is Genesys Cloud fiscal quarterly revenue, including committed contractual amounts and usage based revenues, multiplied by four. It is a company defined annualized measure, not the same figure as recognized total annual revenue across Genesys. The chart here therefore uses Cloud ARR with the definition attached and preserves the word nearly. A July 2025 announcement reported nearly 2.1 billion dollars for the earlier fiscal quarter; the September 2026 release reports nearly 2.9 billion at July 31. Signet shows these disclosed observations without filling missing years or turning a quarterly annualization into an audited yearly revenue series.
The pricing pages and financial releases show a mix of recurring platform relationships and usage related revenue. The September results say more than 7,500 organizations use Genesys Cloud, while the broader company description refers to more than 8,000 Genesys customers. Those populations should not be substituted for one another. More than 600 Cloud customers generate over a million dollars of ARR, according to the same release. The March announcement says more than seventy percent of Cloud customers used Cloud AI at January 31 and that AI accounted for twenty percent of new business annual contract value during the fiscal year. Annual contract value from new business is not a share of total recognized revenue. Signet reads the commercial model as land, deployment and continued expansion within a customer's operations, with the original denominators preserved. The Korean sales role makes pipeline and revenue quota explicit, while the customer success architecture role focuses on implementation outcomes and reusable work. A candidate should distinguish the purchase decision from the later evidence that a customer has successfully broadened use.
The December 2021 release announced 580 million dollars of funding at a 21 billion dollar valuation. That is a historical transaction value, not a fresh valuation established by the 2026 operating results. The July 2025 announcement describes 1.5 billion dollars of commitments from Salesforce and ServiceNow in equal portions, intended to repurchase shares from existing shareholders. It says Hellman and Friedman and Permira would remain majority shareholders and gives an expected closing schedule. The research does not convert that commitment into new growth cash received by the company or claim a subsequent closing without evidence. The September 2026 results report first half revenue growth above twenty percent, operating margins above thirty percent and over five hundred million dollars of free cash flow over six months. These are different metrics again, with GAAP and non-GAAP scope described by the source. Signet keeps the annual, quarterly and six month observations distinct. This helps a reader discuss operating scale and financial durability without manufacturing a continuous revenue history or a current market value.
Former leadership at Cisco, Skype and Microsoft; current executive, not labeled a founder.
Connects agentic AI with enterprise scale customer work.
Joined in 2016 after serving as chief architect at Interactive Intelligence.
Leads the technical direction connecting agentic work with enterprise automation.
“Agentic AI is changing how companies operate around the customer”
Tony Bates · Official announcement, excerpt · 2026-09-02
The current leadership pages identify Tony Bates as chairman and chief executive officer, Glenn Nethercutt as chief technology officer, and Scott Cravotta as chief customer officer. Bates is a current executive, not presented here as a founder of Genesys. His official biography describes leadership roles at Cisco, Skype and Microsoft and his service on the Okta board. Those experiences place communications infrastructure and enterprise software in his background, but do not by themselves establish how every present team operates. In the September results announcement, Bates connects agentic AI with coordinating people, systems and workflows around customer intent. Signet reads that statement alongside the actual product releases rather than treating a leadership quote as evidence of a shipped feature. The leadership page also identifies Mike Szilagyi in product leadership and Brian Swartz in finance. These are current company roles visible in the sources at the research date. The chapter describes executive decisions and responsibilities instead of constructing an unsupported founder origin story or inferring personal motives from a photograph.
Nethercutt's official biography says he joined Genesys in 2016 after serving as chief architect at Interactive Intelligence. As chief technology officer he is responsible for technical direction across the platform. The June 2026 Pinkfish announcement supplies a concrete example of that direction: Genesys completed an acquisition aimed at connecting agentic customer work with enterprise automation. The release distinguishes the acquired technology from the schedule for bringing it into Genesys products. It describes an expected AppFoundry offering and a later native platform integration. Completion of an acquisition is therefore different evidence from completion of product integration. The same distinction applies when a partner joins an ecosystem announcement. Signet reads the technical problem as making an AI initiated action usable in the enterprise's actual systems while preserving governance. A candidate can ask which integration exists today, who owns it and how failed actions are handled. Those are practical questions inferred from the architecture, not unpublished instructions from the executive team or evidence of a particular customer's deployment.
Cravotta's biography describes responsibility for customer outcomes and experience across a substantial part of the company. He joined Genesys in 2015 and previously worked at organizations including OpenText GXS and ADP. The Riachuelo release places his current role beside a named customer's operating results, making customer success part of the agentic story rather than an optional step after selling software. The Korean architecture posting reinforces that connection: it asks for work with strategic APAC customers, reusable assets, mentoring and a handover from prototypes into production. The Korean sales posting describes an overlay working with account executives, solution consultants, architects, value consulting, customer success and partners. These postings show required collaboration; they do not publish the complete Korean organization chart or report every local employee to one person. The May Korean announcement names Kim Dong Uk as Korea country manager. Signet keeps that dated fact separate from the unnamed Head of Sales Korea in the sales job. A reference to local leadership does not by itself establish a reporting line.
Counts are current postings, not employees; collaboration does not establish reporting lines.
Korea country manager
Open posting count
Open posting count
Counts are current postings, not employees; collaboration does not establish reporting lines.
Local customer operations need AI sales and implementation.
The May 2026 Korean announcement identifies Ajungdang as a Genesys Cloud customer and names Kim Dong Uk as Korea country manager. It describes a growing consumer services business choosing AI capabilities for its customer experience operations, with staged automation and workforce improvements. Plans for deeper autonomous interactions remain plans in that release; they are not all measured results at publication. This provides specific Korean evidence beyond the fact that a global product can support Korean users. The current official Workday board shows two Korean postings, both based in Seoul Flexible, with an additional Seoul location on the enterprise sales posting. Signet counts postings here, not local employee headcount. The architecture role describes work with strategic customers across APAC and possible international travel, so the Korean base does not make every customer Korean. The source also requires legal eligibility to work in Korea. These details help a reader separate the local business context, the place of employment and the geographic reach of the work before interpreting the apparent size of the team.
The first posting has the ATS title Senior Account Executive, Enterprise, but its body labels the job AI Sales Specialist. It places the role on the sales team, reporting to Head of Sales Korea, and describes an AI focused overlay alongside other account resources. Signet preserves the exact official title and full description and makes the mismatch visible instead of silently replacing one with the other. The role asks for at least eight years in enterprise software sales or business development, with relevant experience in AI, generative AI, cloud, SaaS or transformation. Responsibilities include creating opportunities, connecting business value with executive conversations, building AI pipeline and achieving a revenue quota. It is not simply an existing account caretaker position. The source lists collaboration with account executives, solution consultants, AI architects, value consulting, customer experience advisory, customer success and partners. Contact center, CCaaS, AICC, CRM and virtual agent familiarity appear in preferred context. A reader should check that distinction rather than promoting every product preference into a mandatory qualification or attaching it to the separate architecture opening.
The second opening is Principal AI Solutions Architect, Customer Success. It asks for at least twelve years of relevant experience or equivalent, including five years implementing CX, CRM or AI platforms and three years in architecture, integration or process design. Those are technical experience requirements, not a twelve year sales rule. Native Korean and business English, APIs, data and cloud are part of the described work. The architect creates prototypes and minimum viable solutions, connects CRM or ERP systems, develops reusable accelerators and helps move the work into production. The description names operational measures such as handling time, satisfaction, containment and revenue outcomes. Its references to GDPR, PDPA, PCI and HIPAA are applicable governance contexts, not a claim that every Korean customer is subject to all of them. Signet reads the first months as understanding the customer workflow, defining a permitted pilot and proving a reliable handover. That preparation is an editorial interpretation, not a promise of an official onboarding schedule. The full posting remains available for the precise travel, education and eligibility conditions.
Current Signet catalog · 2026-10-19
Exact titles stay intact; sales title and body differ.
Native platform integration was scheduled separately.
Control functions are available; Navigator and Orchestrator remain later fiscal quarter plans.
Resolution, satisfaction and costs describe its specific deployment.
Genesys completed the Pinkfish acquisition on June 30, 2026 to extend agentic customer work into enterprise automation. The release gives separate expected dates for AppFoundry access and native integration. Those schedules should be verified before they become customer commitments. The September ecosystem announcements add another layer of collaborators around models, voice and enterprise systems. They show the direction of the platform, while each capability still has its own availability and implementation conditions. Signet reads the change as expanding the work that can follow a conversation rather than treating an acquisition or partner list as proof that every end to end workflow already exists.
September 2 combines operating results with product announcements. Nearly 2.9 billion dollars of Cloud ARR and more than four hundred million dollars of AI related Cloud ARR describe financial scope, while Contextual Intelligence and AI Control Plane describe available platform functions. Navigator and Orchestrator remain scheduled for later fiscal quarters in those releases. The enhanced virtual agent has a similarly staged roadmap, with current features separated from expected voice and interoperability work. A useful customer conversation should connect the required outcome with the confirmed product state and identify which planned capability would change the scope. Signet does not infer a release merely from the passage of time after an announcement.
The September 30 Riachuelo announcement adds a named operating example to the broader agentic strategy. It reports self service resolution for 84 percent of customers using the experience, a sixty percent satisfaction increase and a twenty six percent reduction in technology costs for that deployment. The comparison with the prior chatbot provides context, but it does not make the result transferable to every customer or prove that AI alone caused every reported improvement. The current Korean roles offer two ways to participate in this transition: a seller who develops AI opportunities and an architect who connects prototypes with customer success. Signet reads both through the same question: what permitted customer task can this team complete, and how will the customer know it worked?
Genesys connects customer intent with controlled actions across people, AI and enterprise systems.
Counts are current postings, not employees; collaboration does not establish reporting lines.
Employer postings were checked on 2026-10-10. Availability can change. Mock applications request a review from Signet.
Follow the company from its vision through products, evidence and people to the Korea team and current roles. Use the table of contents to move within the page, and expand the sections for more context.