We are excited to share that the Conversations API is soon launching into the Controlled Availability phase!
For the first time, you can put the Moveworks Assistant behind your own surfaces, your own desktop and mobile apps, internal portals, orchestration layers, and test harnesses, over a simple REST interface, without having to own a native chat experience.
Why we built it
Moveworks has always powered the surfaces employees already use (Slack, Teams, embedded web chat, etc.). The Conversations API extends that reach: it is the programmatic interface to the Assistant, bringing knowledge lookup, plugin execution, multi-turn conversations, and proactive messaging to any surface you build. It is the same Assistant your employees know, now available wherever you need it.
What you can do in Controlled Availability
- Multi-turn conversations with server-managed context, so you never resend prior turns. Slot filling and disambiguation are handled for you.
- Assistant-driven search with citations grounded in your ingested knowledge.
- Agentic workflows: run Agent Studio plugins and native actions (ticketing, PTO, access provisioning) through conversational flow.
- Proactive delivery: approvals, ambient agent messages, and Employee Comms campaigns delivered as events.
- Richer button interactions: slot disambiguation, confirmation groups, single and multi static selects, URL and redirect buttons, and native plugin follow-up buttons.
- Feedback submission (helpful / unhelpful plus free text) attributed back to Insights.
- Standardized authorization: Authorization Code flow for core IDPs (Okta, Azure, etc.) and self-signed JWT for service and agent requests with user impersonation.
The surface is built on four constructs, Conversations, Responses, Messages, and Events, supporting synchronous, asynchronous, and proactive interaction patterns.
Who it is for
Controlled Availability is a great fit if you are looking to:
- Bring Moveworks to custom desktop, mobile, or portal surfaces beyond Slack and Teams, including branded front doors for your full employee base.
- Embed Moveworks inside an internal router or orchestration layer that decides which AI handles a query.
- Programmatically evaluate Assistant responses on a cadence.
You can deploy your integration to a pilot cohort of end users to test your integration, and further to your broader organization!
A Note on Controlled Availability
Controlled Availability is intentionally less opinionated about UX at the API layer than our native Slack and Teams experiences. A few capabilities (in-modal form rendering, handoff fallback for legacy deflections, and per-integration analytics tagging) are not yet supported, and your feedback during this phase will directly shape what ships at GA.
How to sign up
Sign-ups are open now. Access is curated by our Product team, and accepted nominees will begin onboarding on July 20. To request access, fill out the sign-up form here. We will review your submission and reach out to discuss fit and next steps.
What to expect before you sign up: This is API access, not a turnkey feature. To get the most out of Controlled Availability, you should come in with a pilot integration in mind that you want to build, and have technical resources or developers available to build it on top of the API.
We cannot wait to see what you build!
Questions or ideas? Drop them in the comments below.
