Skip to navigation

Assistant Platform Overview

The assistant your employees use, the channels it runs on, how it reaches out to them, and how you measure it.
View as Markdown

The Assistant Platform is the part of Moveworks that employees see and use: the Moveworks AI Assistant, the chat and web channels it is deployed to, the messages it sends without being asked, and the analytics that show how it is performing. The pages in this area cover configuration in Moveworks Setup and Studio. Building the plugins, connectors, and search sources the assistant draws on is covered in Tools, and the reasoning that turns an employee’s request into a plan is covered in Harness.

If you are new to Moveworks, start with the orientation. If you already have a tenant, the two most common first tasks are putting the assistant in front of employees on a chat or web channel and creating a purpose-built assistant for a team.

Start with

Your first deployment

1

Connect your systems and ingest users

The assistant serves the users in the Moveworks roster, so ingest users first. If ServiceNow is your service desk, Implement on ServiceNow takes you from a connected instance through search, forms, and ticketing in order.

2

Deploy to a channel

Complete the access requirements for your chat platform, then follow Configure Moveworks Assistant to create the chatbot configuration and its notification route. Browser deployments are covered under Web Experiences.

3

Launch

Work through the Moveworks Implementation Starter Guide for the rest of the rollout and validate against the Launch Checklist before announcing the assistant.

4

Measure and adjust

AI Assistant Insights shows how employees use the assistant and how it performs, and the CSAT survey samples active users for a satisfaction rating. Use both to decide what to tune or build next.

Two kinds of assistant

The Moveworks AI Assistant is the pre-built assistant. It covers every plugin, knowledge source, and system your organization has connected, runs on the Agentic Reasoning Engine, and is configured through its built-in plugins in Moveworks Setup and extended with plugins built in Tools. A Productivity Assistant is a separate assistant that does one job well: it has its own name, instructions, curated tools, knowledge scope, Skills, and audience, and it runs on the Agentic Orchestrator, the upgrade to the Agentic Reasoning Engine, which reaches Productivity Assistants first. End users get a normal assistant experience either way; the scoping is invisible to them.

Productivity Assistants are in Controlled Availability. The Productivity Assistants overview covers access, builder roles, and where end users find them.

Find your task

Getting Started also holds the Roadmap & Release Notes, Moveworks Best Practices for launching the assistant and driving adoption, and the scope of Support and Professional Services. Analytics also includes the Data API, which exports interaction records for your own BI tools; the endpoint reference is under API Reference.

Where the work happens

SurfaceWhat you do there
Moveworks SetupCreate chatbot configurations, route notifications, edit the assistant’s dialogues and branding, run Employee Communications campaigns, and control the built-in plugins.
Assistant BuilderCreate and manage Productivity Assistants, in the EmployeeWorks web app.
EmployeeWorks web appWhere employees open the assistant inside ServiceNow, browse the Productivity Assistants shared with them, and use Enterprise Search, Tasks and requests, Notifications, and Canvas.

How this area relates to the rest of the docs

The Assistant Platform is where you shape what employees experience. How the assistant reasons about a request, plans, selects plugins, and applies guardrails is documented in Harness, along with built-in behaviors such as Smart Handoff, approvals, and AI disclaimers. What the assistant can do, meaning the plugins, connectors, MCP servers, and search sources it calls on, is built and maintained in Tools. Who can use the assistant, including user ingestion, access control, SSO, and security settings, is managed in Platform Management. Ticketing, forms, provisioning, and knowledge for service desks are covered in Service Management.