TLDR
A reported notice has put Now Assist for ESC Pro implementations in question. The public sources reviewed don’t establish a retirement date for the named offering. Before changing your rollout, separate the AI package, the portal, and the chat integration. ServiceNow documents several paths for employee conversations, with different deployment and licensing requirements.
An IT team had already scoped its move to Employee Center Pro when a deprecation notification put the AI portion back in question. In an October 23 Reddit post, the author said the notice named Now Assist for ESC Pro and listed no replacement product. They wanted to know whether their planned portal would still have supported chat.
The post doesn’t include the notification itself, its application identifier, or an effective date. Those omissions matter when you’re deciding whether to keep building, change a dependency, or rework the implementation.
What Has ServiceNow Actually Confirmed?
ServiceNow’s EmployeeWorks Web App FAQ says Employee Center Pro has no planned deprecation and will remain supported for the foreseeable future, with most new innovation directed toward EmployeeWorks Web App.
That statement covers the portal. The Now Assist for Employee Center Pro documentation describes an offering for employee or requester conversations; other Now Assist products may be needed for AI agents and additional features.
There’s also a more recent release record than the standalone product history initially suggests. The October 8 Now Assist Suite notes list ServiceNow Otto for Employee Center Pro version 1.2.6, last updated September 3, 2026. Suite listings are cumulative, so this isn’t evidence of a new October release.
The individual product history still stops at version 1.2.4 in August. Neither record establishes a future support commitment or overrides a later customer notice, so a claim that the entire offering has already disappeared needs stronger evidence.
Making Sense of the Product Names
ServiceNow’s September 4 Otto explainer says EmployeeWorks can use either Now Assist or Moveworks underneath the assistant. The current Web App FAQ says EmployeeWorks Web App requires Moveworks.
The September product rename table helps explain the difference:
Previous Application Name | Name After the September Change |
|---|---|
Employee Slate, built for Now Assist | Unchanged |
Employee Slate, built for Moveworks | EmployeeWorks Web App |
Employee Slate Core | EmployeeWorks Web App Base |
Employee Slate Advanced | EmployeeWorks Web App Extended |
I read the later Web App guidance as referring specifically to the renamed Moveworks application. That reconciles part of the apparent conflict, though it doesn’t establish the lifecycle of the Now Assist variant.
Employee Slate built for Now Assist is also a different named application from Now Assist for Employee Center Pro. A reference to one doesn’t establish the status of the other. Ask the account team to identify the application record behind each name in its recommendation.
Can You Keep Chat in Employee Center Pro?
There are several documented components to consider, and each needs its own support and entitlement check against the notice.
ServiceNow documents Now Assist enhanced chat in Employee Center, configured through Now Assist in Virtual Agent. A configuration guide establishes how the integration works; it can’t guarantee that a later notice leaves your version supported.
There’s also a documented option to embed Moveworks in the existing portal. ServiceNow’s integration announcement covers both Employee Center and Employee Center Pro. Enabling it replaces the existing enhanced chat experience, while homepage search retains its separate configuration.
Brazil documentation now calls that application ServiceNow Otto Chat Integration, with installation requiring Moveworks purchase and appropriate entitlements. Its presence in the Store doesn’t establish that your existing subscription covers the service.
That gives you an option to evaluate without assuming the whole portal must move to EmployeeWorks. Compare the embedded assistant against your launch requirements and confirm the supported combination with ServiceNow.
Human support needs separate attention. ServiceNow’s live chat documentation directs customers away from deprecated Connect Support toward Agent Chat and Advanced Work Assignment. Don’t use an old Connect Support setup as the fallback simply because it still appears in a guide.
Test the complete interaction: an employee requests software, an approval is required, and the employee asks a person for help. Confirm what transfers with that conversation and where the request history remains available.
The Cost of Moving to EmployeeWorks
Embedding an assistant and adopting a new employee experience are separate scope decisions, and a proposal should price both against the outcomes you need.
The Web App FAQ excludes Pro Plus and Enterprise Plus alone from eligibility. It specifies an EmployeeWorks SKU or an eligible AI business-unit SKU with Moveworks entitlements. It also notes Assist consumption, though not every conversation consumes an Assist.
For migration, the same FAQ describes a new deployment with no migration tooling, reusable configuration tables, and widget rebuilds where equivalents aren’t available. Running the two experiences alongside each other is supported.
The October implementation guide adds concrete prerequisites. That month’s Web App release requires Zurich Patch 13, Australia Patch 7, or Brazil Patch 1. Announcements and App Launcher require the Extended application and the corresponding entitlement.
The guide describes automatic reuse of existing taxonomy, inbox, profile, and org chart configurations, which reduces part of the implementation effort. Your partner still needs to assess each custom portal widget for the new experience.
When you review the backlog, keep work moving on request ownership and knowledge quality. Price each custom homepage component for the experience where you intend to use it, including the effort to test it with employees.
Ask your partner to show what carries over, what needs rebuilding, and which requirements remain unproven in a demonstration. Use the release and patch combination you plan to deploy, because the latest announcement may describe a different configuration.
Deprecation Phases and Support
ServiceNow’s plugin lifecycle definitions distinguish three relevant states. Planned deprecation can restrict new activation while support continues. Maintenance mode also retains support, without new enhancements or activations. A deprecated application is no longer deployed, enhanced, or supported.
Those are general definitions, not a verified lifecycle assignment for the application in the Reddit report. The phrase about no replacement doesn’t supply the missing phase, effective date, or treatment of existing customers.
A working test instance answers whether a configuration runs today, but your project also needs confirmation of support through launch and the next planned upgrade.
Get These Answers Before Changing the Rollout
Take the original notice to your account team and implementation partner, with the relevant application inventory and order form:
Which application, version, or commercial SKU is affected? Record its identifier, lifecycle phase, effective date, and the notice or knowledge article reference.
What changes for an existing activated instance versus a new deployment? Confirm the support window, upgrade treatment, and any activation restrictions.
Which supported configuration covers the planned conversations? Include knowledge answers, request submission, approvals, and human handoff wherever they are in scope.
Can the required assistant stay inside Employee Center Pro? Compare that option with a Web App deployment, including subscriptions, usage charges, and licensed users.
Which completed work survives each option? Get a specific estimate for widgets, integrations, acceptance testing, and the change to the launch date.
Put the answers beside the affected backlog items. If support is unresolved, hold new spending tied to that component and keep independent work moving. A dated decision record will be more useful at the next project review than another slide showing the newest product name.
Keep the Employee’s Request in View
A communications hub and faster resolution of routine IT requests can sit within the same program, but they need different acceptance criteria. Use this review to check which problem is driving the investment.
For teams focused on everyday IT support, Ravenna’s AI ITSM approach brings requests and automated resolution into Slack and Microsoft Teams. Evaluate that against the support portion of your requirements, while assessing employee communications and intranet needs separately.
Bring a real request to the evaluation and follow it through approval, resolution, and an exception that needs a person. Apply the same test to Ravenna and the ServiceNow options you’re considering.
We’re happy to walk through that with your team’s requests. The next implementation decision should connect a supported product, a clear cost, and an employee outcome you can demonstrate.
Frequently Asked Questions
Is Employee Center Pro Being Deprecated?
ServiceNow’s current FAQ says it has no plans to deprecate Employee Center Pro. The reported Now Assist notice concerns a separately named offering and still needs verification against the original notification.
Does Moveworks Require a Move to EmployeeWorks Web App?
ServiceNow documents a Moveworks integration inside Employee Center and Employee Center Pro. Check the current Otto Chat Integration prerequisites and your entitlements before treating it as an available option for your deployment.
What Is Still Unconfirmed About the Notice?
The exact application or SKU, lifecycle phase, support end date, and replacement entitlement remain unverified from the public report. Publishing a universal retirement date or claiming every customer must migrate would go beyond the available evidence.
