Slate vs. Employee Center Pro: The Future of Employee Experience

Christine Morris

We'll go ahead and get started. I think everybody can see my screen.

Just some quick intros before we dive in. I am Christine Morris. I am Vice President of Consulting here at Ondaro. Been in the ServiceNow ecosystem since about 2015. I was a customer, I did an RFP, and I fell in love with the tools and was like, this is all I want to do. So excited to be here with you guys today. Nate, you want to do a quick intro?

Nate Aiken

Sure. Good morning everyone — good afternoon, wherever you might be. My name is Nate Aiken. I'm the Practice Strategy Lead for all things Moveworks and EmployeeWorks here at Ondaro. Been around the ServiceNow ecosystem for about 13 years — I think it was about the Berlin release. I've been in the consulting space for about 20 years now. I'm excited to share this content with you today and answer some of the questions you might have. Jon.

Jon Merchant

Yeah. Jon Merchant. I've been in the ecosystem probably since 2013 or 2014. I remember my first Knowledge was in San Francisco — however long ago that's been. I've done portals probably since day one, worked with the old CMS system and then into Service Portal and EC Pro. I've been doing portals for a lot of years.

Christine Morris

And Jon is very modest. What he didn't say in his intro is that he has built award-winning portals. Many of his portals have made first place with ServiceNow — Portal of the Year, second place, lots of top ten. He is our genius behind the magic.

Today we're really going to cut through the confusion — what is EC Pro, what is Slate, and where each really fits. We'll cover some of the foundational work that matters regardless of which path you choose, especially content and taxonomy. You'll get to see Slate in action, not just hear about it. And then we want to leave you with some practical ways to think about what comes next.

A little bit about Ondaro before we dive in. We are the only pure-play ServiceNow partner with fully certified resources across the entire platform. ServiceNow isn't just one of the things we do — it's all we do. And that breadth matters, because our clients' needs rarely stay in one product area. On the left you can see all the products that we cover — if it's on the platform, we support it.

We also support the full lifecycle — from strategy and transformation, with a big focus on governance, through architecture, implementations, and of course as we just introduced Jon, we've got amazing employee experience folks, UI/UX designers, and integrations galore. We really don't want to disappear at go-live. We want to help our clients operate, enhance, and optimize the platform as their business evolves. The result is one partner that can help clients envision it, build it, and continuously make it better.

A little housekeeping — we want this session to be interactive. If you've got a question, we'd love for you to enter it in the chat. If this is your first webinar with us, we like polls — it's always nice to see how everyone else is feeling about the topic. If you need captions, click on More and you can turn those on. The bottom line is we want this to be as engaging as possible. And of course I'm going to kick us off with a poll.

Do you know the difference between Slate and EC Pro? Put your responses in the chat. A: I can confidently say yes. B: a little bit here and there — I know the communication has been a little confusing. C: nope, that's why I'm here today.

Lots of C's. All right, well we love it and we're going to help you through this today. And if you want to hear more, we're always happy to have another session.

Now I'm going to dive into what EC Pro is and what Slate is. Employee experience is changing — employees don't care what systems they're using anymore. They care about getting something done. Employee Center Pro represents the modern digital workplace — personalized content, navigation, search, journeys, and self-service. And then Slate kind of shifts that model from navigation to interaction. Employees start with intent rather than figuring out where to go. This isn't about which UI is better — it's about two fundamentally different employee experience models and where each one fits best.

A quick distinction I want to mention — if you're an Employee Center client, you have what's called Employee Center, which is really that base portal experience of searching for services and knowledge. And then EC Pro, which comes with HRSD licensing, takes that much further into a true digital workplace.

EC Pro brings together services, knowledge, news, communications, events, personalized content, and that one employee destination. Content can be targeted by role, location, department, audience, and any other employee attribute you can think of — so different employees can have very different experiences. It supports a much richer intranet and communications experience with curated content, campaigns, announcements, topic pages, and that overall branded experience.

Employee Journeys are a major differentiator here. Onboarding, transitions, leave of absence — other moments that matter to the employee — require coordinated tasks, content, and communication over time. EC Pro is also strong for discovery and engagement. Employees can browse benefits, programs, policies, news, or resources they might not have known to specifically ask for. And that's really the strength of EC Pro. It isn't just about completing a transaction — it gives the organization a place to inform, engage, guide, and serve employees.

And that last point becomes really important when we look at Slate, because Slate is optimized around a very different behavior — starting with a conversation instead of a destination. Slate is not the next version of EC Pro. It represents a fundamentally different approach to employee experience. Instead of navigating menus and pages, employees can simply express what they need in natural language. The experience is personalized based on employee context and intent, and an employee can also personalize their own page — we'll show you that a little in the demo coming up, choosing what information and widgets are most useful to them.

Slate brings tasks, approvals, requests, information, and actions directly into that experience — including work that needs attention. It's highly action-oriented, moving employees from asking a question to actually getting work done with fewer clicks and less navigation. The big shift is from "here's your digital workplace" to "tell me what you need to accomplish and what matters to you most."

Before you start debating EC Pro versus Slate, you really want to define the employee experience you're trying to create. You start with employee needs, not technology. And I've always said for my entire career — the technology is the easy part, the people are the hard part. What are employees actually trying to accomplish? Where are they struggling today? What are the high-volume interactions, but also the high-value moments that matter — like onboarding, leaves, relocations, transitions?

Think about the experience model — not everything should be conversational, and not everything belongs on a portal either. Some things are perfect for a quick question and action. Some benefit from browsing and discovery. Others need a guided, multi-step journey.

You also have to think cross-functionally. Employees don't think in terms of HR, IT, finance, or legal — they think "I'm starting a new job," "I'm having a baby," "I need a laptop," "I'm moving." That experience really should cross those organizational boundaries and not necessarily be visible to them.

Then we get into what I think is the biggest prerequisite for anything — for a good portal, for Slate. Content and service readiness. AI does not marginally fix bad content. If you have five versions of the same policy, outdated knowledge, confusing catalog items, or taxonomy built around your organizational structure instead of employee language, you're going to carry those problems into the new experience. This applies to your workflows too. If the employee gets a beautiful conversational experience but it hands them off to a 25-field form or a broken process, you haven't transformed the experience — you've just put a better front door on it.

Personalization also needs intention. What should I see because of my role, my location, my business unit, my lifecycle? And what should employees be able to personalize for themselves? Somebody has to own this after launch — quite often governance is left behind, and it's critically important from a content perspective. Service ownership, experience ownership, measuring success, and focusing on continuous improvement. Employee experience is a product, not a project. And it never ends.

That's why we say the technology decision actually comes later. Once you understand the moments, the channels, the content, the services, the personalization, and the governance — the EC Pro versus Slate decision becomes much clearer.

A few things to leave you with before I hand this over. Slate is not EC Pro 2.0, and EC Pro is not going away. Both experiences are supported on the ServiceNow platform. There is no announced deprecation of EC Pro. Those of us — Jon and myself — who have been on the platform for ages can recall when we went from the CMS portal to Service Portal, and we still encounter clients that are still using their CMS portal today. So we really don't expect EC Pro to go away.

There also isn't a migration path from EC Pro to Slate. With that said, the content within ServiceNow is still valid and relevant. Moving to Slate is an experience strategy decision, not necessarily a platform upgrade. And ServiceNow's innovation is clearly leaning towards Slate, particularly around conversational, AI-driven, and action-oriented experiences.

But existing EC Pro investments are not stranded. The underlying services, knowledge, catalog, workflows, data — all those platform capabilities still matter. Customers shouldn't ask "when do we have to move to Slate?" The better question is: which experience model best supports what our employees need?

Before I turn it over to Nate, another poll for you. How many employees actually open your portal? A: over 50% — a bad migration is a real risk for you. B: 20 to 50% — usually concentrated in a few populations and a few different tasks. C: under 20% — an adoption problem that no platform choice fixes on its own. D: we don't know — the most common answer, and the first thing to fix.

Lots of D's. A few folks at 20 to 50% — great. And if you have migrated to Employee Center or EC Pro, there are a lot of pre-built metrics you can activate and track. We've got some big users with A's — love it. With that I'm going to turn it over to Nate.

Nate Aiken

Awesome, thanks Christine. It's great to see that people are able to measure how many folks are really using portals and have that insight. Jumping in — I want to start by level-setting, because there's a lot of potential misunderstanding about what these different terms mean when we start talking about EmployeeWorks, Otto, Slate, and Moveworks, and how it all relates.

This slide brings together the full stack and explains what each of these are. Starting wide — EmployeeWorks is the product, the SKU that you're buying from ServiceNow that includes all of these things.

ServiceNow Otto is basically the AI brand within ServiceNow — think Google Gemini, Anthropic Claude, or OpenAI ChatGPT. ServiceNow Otto is the equivalent to that. And then Employee Slate is the actual UI — the experience we'll see during the demo. That's what people are actually using. Behind that, you can power Employee Slate in different ways.

You can use Moveworks, which is the recommended method, or you can use Now Assist, which gives you more of that traditional Now Assist experience — you don't have the full reasoning engine of Moveworks, so some of the capabilities of Slate are going to be a little more limited if you go the Now Assist path. And each of those paths is a different implementation. So if you start off with Now Assist and decide later you want to go the Moveworks route, you would need to re-implement Slate using Moveworks. That's an important decision upfront — determining which path you want to take in powering Slate.

Moveworks is going to give you a more robust experience, the ability to integrate with more enterprise platform systems, and greater language support. We'll talk about how this is all sold and bundled a little bit later.

There are two layers of Slate packaging. Slate Foundation gives you a lot of what most people are looking for — the conversational AI is probably the biggest part of that, along with a lot of the basic tasks you would perform through a chat interface. And then with Employee Slate Advanced, you're really adding on some of the employee experience elements like the communications pieces, microsites, topics, and the app launcher.

The app launcher is a way for you to connect to Entra ID and actually gather the applications assigned to users and make them available within Slate, so they can launch directly to those applications from a single location. One of the biggest questions is how is this all bundled. There are a couple of different ways to get Slate. First is through the EmployeeWorks SKU — that gives you Employee Slate Advanced, the complete bundle. The other method is through the HRSD AI packages.

That will give you everything as well. If you go through some of the other business unit AI products or the new AI-native SKUs, you will end up with Foundation only. So to get the full experience, you need either the EmployeeWorks SKU or the HRSD AI package.

Looking at the roadmap — what are you getting now versus later — Employee Slate is still relatively new. It was announced by ServiceNow at Knowledge 2026 back in May. So a lot of the things you might see in Employee Center Pro are maybe not quite yet in Slate.

There's a roadmap to get to full feature parity, looking out to 2027. ServiceNow has said that a lot of what we call critical components or pieces of the experience will be available by the end of 2026, but we're looking at full feature parity later into next year.

Looking at the implementation — as Christine mentioned, there's not really a migration from one to the other. They're built on two different tech stacks. That's really the most important part. EC Pro is portal and Angular-based. And then Slate is built on a whole new tech stack with AI, UX and JS. For those that aren't technical — it's a completely different code base, completely different back end.

So while the data in the tables that you might be exposing is the same, things like widgets you've developed on EC Pro will not directly come into Slate and be usable the way you may have been able to go from Service Portal into EC Pro. The upgrade cadence — Slate is being updated monthly through store releases, which is very nice. They're trying to make the catch-up to feature parity from EC Pro to Slate very regular, releasing things monthly.

Another big difference — with EC Pro, your external users, like customer support scenarios, are not supported on Slate yet. Slate is really intended to be internal, employee-facing. So you're not going to power any of your customer service solutions that you may have built on platform through Slate. We'll see how that shakes out later in the year and into next year.

On widgets — there's no migration currently. There is a set of out-of-the-box widgets. You can configure those, determine whether or not you expose certain widgets, and how they're arranged on the home page — we'll look at that a little bit during the demo. EC Pro is very highly customizable. With Slate, custom widgets are on the roadmap — they're looking at a widget builder coming soon. Those are some of the biggest highlights.

There's no upgrade path, so deciding what gets rebuilt and what carries over automatically is important. All your custom EC Pro widgets will not be available in Slate. Page layouts and navigation — we're on a different tech stack and a different experience, so you're not going to have the same look and feel you had with EC Pro. Branding and theming does not come over. With Slate right now, branding and theming is fairly limited — things like logo, primary and secondary color. There's a selection of Slate color palettes to choose from, so you can shift the color palette of the background somewhat, choose your primary and secondary color, and add a logo. It's not as robust in terms of branding and theming customization yet — that is still to come.

But things like the unified inbox, the org chart, employee profiles, and your catalog items — that was one of the biggest things I remember going from CMS into Service Portal, there was a lot you had to do to transition your catalog items to get them ready for the portal. With the current release of Slate, things like catalog client scripts and policies, variables — all of those work out of the box. So that's good news. You don't necessarily have to go through and restructure or rebuild your catalog items. You'll obviously want to go through and test and validate that things are working as part of your Slate deployment, but they are supported today.

Christine Morris

And the other thing I'll just mention — knowledge as well. It's not on the slide, but you're still able to access all of your knowledge content through Slate.

Nate Aiken

Yeah, absolutely.

Every customer is standing at the same fork in the road here, and there are really three — I'd almost say four — viable paths. You can stay on EC Pro and continue the experience you have today. If you're using EC Pro, you have the full support of everything that's there. You can look to adopt Slate and bring in that conversational UI, maturing on the journey with Slate as it continues to develop.

You could look at EC Pro plus the Moveworks chatbot. If you go with EmployeeWorks, you are entitled to both EC Pro and Moveworks. You can integrate the Moveworks chatbot into EC Pro to get a lot of the same chat experience — it can still take action, answer questions, and take action. You have the ability to tie the two together.

The third option is running EC Pro and Slate in parallel — bringing both experiences to the table for your employees. Maybe certain populations within your organization prefer the chat-based UI experience, and you work through that adoption and implementation in a more targeted way.

Christine Morris

And I think a lot of this depends on where you are on your journey with the platform. We've got clients that have invested greatly in EC Pro and are using Journeys — and Journeys aren't coming to Slate until 2027. So very clearly, you've got to maintain at least that component of EC Pro. It's going to be a different journey for each organization. And that's why our starting point is always: let's take a step back from the technology and figure out what employee experience we're actually driving toward.

With that I'm going to stop sharing, and Nate is going to give us a demo of Slate.

Nate Aiken

What we're looking at here is the Employee Slate home page. This is where users will land when they open it. You can see it looks greatly different than EC Pro — if you've seen that experience, like we've talked about, it's very chat-focused. We have the ability to create and configure quick prompts. You could have one that checks your last pay statement, maybe one that checks your PTO — you can create, customize, and configure some quick prompts for your users.

There's also a series of widgets — these are all admin-configurable and accessible through an admin console. You can configure which widgets land where and what the content is. Employee communications can be put in here, providing some configuration of links. Maybe you want to expose certain catalog items and surface your most highly utilized or requested items to the front of the page.

The second part is the canvas. The canvas is a bit different than what we've experienced in the past with EC Pro — canvas is end-user configurable, with a caveat. Maybe we don't want employees to have access to all widgets, but an admin can go in and expose or allow users to add certain widgets to their canvas.

So as an end user, I can come in and add additional widgets that have been made available to me. I can resize them, reposition them, put them in a different order — so I can customize, within reason, the configuration of my canvas.

Christine Morris

For folks that have more modern intranet experiences, there are a lot of platforms out there today that allow you to do this. This is a step forward from a ServiceNow perspective. It's a question Jon and I have heard over the years of building portals — can employees manage their own experience, can they put what they want on it? With EC Pro we've got great favorites, but this really takes that to the next level.

Nate Aiken

I've added the request widget to the canvas, along with the featured apps widget. If I had this tied to Otto and had applications entitled to me, I could actually access those applications directly from here — I would see the applications assigned to me in those systems and launch them right from Slate.

I can access all of my tasks and requests from the canvas as well. Here I've got a couple of universal tasks and an approval, so I can make my approval or rejection of this change request. I can click on it, get the details for the change request — all from a single location. I'm going to jump back to the home page and go through a couple of things we can do as an end user.

I want to find out how much PTO I have. This instance is connected to Workday and it's using the Moveworks engine on the back end. So it's reached out to Workday and collected my PTO balance. I can see I've got 80 hours of vacation and 40 hours of sick time. I've got some time off I need to burn, so I'll ask — I want to take next Friday off.

I didn't give it a date — fairly ambiguous request. It's now reasoning through that, determining what actions it needs to take. It's realized it needs to submit a Workday PTO request, so it's asking how I want to use my time off. I'm going to use some vacation time. It's going through and reasoning through everything it needs to understand in order to properly submit this request to Workday. It's going to submit it as vacation.

Christine Morris

Going fishing.

Nate Aiken

It's making sure it's got everything it needs and now it's going to handle submitting that. It's going to validate and verify with me that this is correct. I'll say yes — and it's successfully submitted. Let's check what days I have scheduled, just to validate. It's going to go back out to Workday, looking at past and future requests. And there I can see that August 31st — I've got my approved PTO request.

Something a little more tricky — I have a dinner receipt for a team dinner. I want to submit it. I didn't tell it it was an expense — all I said is I have a receipt. It's going to reach out to Moveworks. It's telling me it can help me submit this to Concur. It's going to set the description to "team dinner." I'll bring up the receipt so we can take a quick peek. I've got this itemized receipt for a team dinner. We'll go ahead and submit that receipt, and it's going to parse it for me — pulling out all of the details. It's determined it's going to launch creating an expense report. What do I want to name it? August Sales Team. Now it's analyzing the receipt from the image I uploaded, pulled out all of the details, and it's confirming it wants to submit this to Concur. Sure.

Christine Morris

I think we all want this right now — everyone hates expense reports.

Nate Aiken

It actually gave me a link so I could drill out and look at this expense report. Confirmation that I now have an expense entry and expense report for my team dinner. In just a couple of minutes I checked my PTO balance, submitted a PTO request, submitted a team dinner receipt, and created the expense report — and it's off to my manager for approval. I've never left this interface.

With Slate and Moveworks, it's not just about asking questions and getting answers. It's about getting answers and getting things done at the same time.

Maybe I need to understand more about my benefits. It's going to go out and use ServiceNow Knowledge. It's provided me a quick summary of what my benefits are. One of the nice things with Slate and Moveworks — all of these are cited. I can understand what the source of the information is, click into those, and get the actual knowledge article.

Christine Morris

And this is a good example of what we were talking about earlier — what does your content look like today? If you've got six benefits policies for six different global regions, they're not documented properly, or you've got outdated policies — it's not going to help. It's going to potentially present the wrong information. That's why before you make this jump, you really have to have consistent content. You've got to have a structure and a methodology. Over the years, many of us just add knowledge, add knowledge, create more and more articles. We don't always go back and make sure that what's being replaced is retired. And then our AI friend is going to be confused.

Nate Aiken

Absolutely. And one of the nice things about using the Moveworks engine is that we got all of those cited sources for the information it's giving us. But it's also honoring all of the things like user criteria — what do I have permission to see within ServiceNow? Moveworks uses all of the data on my user record to understand context. I'm a US-based employee, so I should have the US policy. And within your organization, that might even be limited down at the user criteria level so that I only see the US policy. But it's going to reason through that baseline information from my user record — a US benefit is going to apply to me based on my location. Which is awesome.

Christine Morris

Any questions for Nate before we jump back to the deck? Was this helpful?

And you know, what Nate has shown here is just the tip of the iceberg. If you're using EmployeeWorks, there are a tremendous number of options — similar to the ServiceNow Store, there's a Moveworks Store where you can see tons of pre-built content around common applications like Workday, Concur, and all the other systems the vast majority of our clients use. It really is powerful functionality.

Nate Aiken

One question in chat — can employees escalate to a request and still see the lifecycle of that request coming from EC Pro? Within the interface, if I started down a path and maybe wasn't getting the answers I needed, I could actually click the Get Help button. I could open an incident, put in my description — maybe this was giving me a response I wasn't expecting, or it was off — and I could actually escalate and have somebody look at it in more detail. It will submit the entire transcript as part of that incident to get support for my issue. Hopefully that answers the question.

Christine Morris

And if you say, for instance, I want to submit a request to get a piece of software — I need Adobe — it should present a catalog item for that. Because I think if I were sitting in your seat I'd think, I don't want a bunch of incidents coming in because someone didn't get the right information from Otto. And there you go — you could click directly into that request and complete it from there.

Nate Aiken

Here's an example of catalog items working within Slate. All I told it was "I need a laptop." It went out and looked at the catalog to determine which laptops I have access to, so I can actually complete the request. It renders the form right here within Slate, with all client scripts and everything working, and using my user profile to auto-populate any information it can. This is a fairly basic catalog item, so I could submit this request pretty easily. Here are my delivery and special instructions — I'm going to hit checkout. I now have a request for this laptop, with my request number available. And however you have your notifications set up, you receive them just the same way you do when using the portal today.

Christine Morris

We've seen Slate, we've talked about how it differs from EC Pro. Before we move on — based on everything you've heard today, are you leaning towards a particular path? A: adopt and stay on EC Pro. B: adopt Slate. C: run both. Let's see what you're thinking.

Jerry says stay on EC Pro. And I'll mention — depending on where you are in your renewal, these features are included the next time you renew. So it may feel overwhelming to think about moving to Slate or whether you'll need more licensing — but at some point you're going to have access to this. Stay tuned, there are definitely some robust features here.

Nate Aiken

It looks like adopt and stay on EC Pro or undecided. And that's a cautious approach to take. I would say stay in tune with what ServiceNow is releasing, the updates to the conversational AI aspects of the platform, and look to adopt when you feel it has the feature parity your organization needs to provide the same level of experience you're getting with EC Pro today.

Christine Morris

And if we think about what next Knowledge is going to look like, there are going to be a lot of great customer success stories on how organizations have been able to use this to truly change employee experience. Let's dive into finding your path forward.

Things to consider as you determine where you're going — what are the top ten things employees come to ServiceNow to accomplish? What employee experience items create the most friction? We all hate expense reports. Not knowing your PTO balance. The things you're constantly digging for.

Do employees want to browse, ask, or do both? We're at an interesting point in the world today. Think about your workforce by generation. We still have Boomers in the workplace who want to click, read, and point. Gen X — I could browse, I could chat, I could do either. All the way down to newer generations who never want to pick up the phone and talk to a single person — they expect to be able to do everything at the tip of their fingers. How you serve all of your employees is an important aspect of the employee experience.

Which employee moments require a rich destination or a guided journey? What use cases could be completed conversationally, end to end? What capabilities would we lose if we move today? And a big one I can't stress enough — focus on your content, your catalog, your taxonomy. One of the things I've seen most over the years is that when IT builds a portal, we speak in IT language. There's never going to be an end user who says "darn it, I need a peripheral" or "I could get some hardware." It's so important that as you're designing your content, you do it in the language the employee actually thinks in.

Start thinking about how, down the road when you get access to Slate and you can have that conversational interface, is your content going to support it? And how will we know the new experience is actually better?

There's no right answer that fits everyone — we really want to focus on what's the right fit for your employees. If today you've invested a tremendous amount of time in your EC Pro experience, and if you're using Journeys and they are a major part of your strategy, you're really going to have to maintain some elements of EC Pro.

If your organization has fully embraced AI, employees are ready for it, you've got tons of primary tasks they have to complete over and over again, you've got great content behind it to take advantage of that conversational self-service, and you've got a mature knowledge and catalog foundation — a lot of Slate's current capabilities are going to move the needle for you.

And what we've seen for folks that have gone the Moveworks route is a little bit of both. You can keep all the investments you've made in EC Pro. You can still have that browsing experience, but you give employees the ability to go into Moveworks and have that conversational piece — instead of Virtual Agent, it's Moveworks.

What do the next 90 days look like? Start thinking this way. Understand what your employee moments that matter are. What are those use cases? What potential adoption friction might you have? Gather employee feedback — does this resonate with them? What are the challenges they experience with your employee experience today?

Start to clean up — and I can't stress this enough — even if you're thinking "I'm not going there yet," you will have access to Now Assist at your next renewal if you don't already. Start auditing your knowledge now. Start establishing knowledge governance. Start retiring unused catalog items and unused knowledge articles. Establish that ownership and governance process today so that when you get there, you can just continue to build on it.

Define the desired employee experience — decide where browsing makes sense, where journeys belong, and map those high-value use cases. And you know what you saw today — I have an expense report I need to do right now, I would love to just pop it in and do it. Determine what those 3 to 5 use cases are where you could start to show value. We all know — platform owners, users, architects of ServiceNow — that to get people on board and go through these journeys, there's some level of cost involved. When you start to think about what the pilots are and what value they're going to bring, and start presenting that to your leadership team, it's a lot easier to get folks on board.

If anyone is interested in doing more, we have EmployeeWorks readiness sessions we can set up. It's a 90-minute working session where we evaluate things like your strategy, your identity, your knowledge, your systems, your governance, and ground that in some real use cases — not just generic information — and give you a readiness report based on where you can go. If you're interested, please connect with your account executive to book a session. We'll send this slide deck out along with a couple of one-pagers, and you can always reply to that email if you're interested in hearing more.

Any additional questions? Anything you'd like to see more of next time? We appreciate everybody joining today. We've enjoyed spending a little time on these topics. If you have questions, don't hesitate to reach out. If you want to get that EmployeeWorks assessment done, we'd love to do that with you. Thanks everyone.