Conversational Context

Conversation context is the previous conversation history between the user and the Moveworks Assistant. The ability to use context is a major differentiator between Moveworks Classic and the Moveworks Assistant experiences.

Generally, it makes sense that incorporating context will lead to more conversational and helpful interactions. But what are the specific ways in which the use of context impacts the responses that users get?

Here are the ways in which it influences the Moveworks Assistant’s behavior and responses:

1. It is used to determine whether the user is speaking about a new topic or continuing a previous one.
2. The reasoning engine uses context to understand references such as pronouns and follow-up questions that may be vague when taken in isolation, but make sense when combined with previous context.
3. Resources found in response to previous requests are also available to the reasoning engine for a few subsequent turns, and may be used to supplement any resources found for the current request.
   1. In a few cases, if the reasoning engine determines that it can answer the current request completely with the information it already has, it may not call a plugin and will summarize a response from the previously retrieved information.
4. In cases where the Moveworks Assistant produces a structured card response, such as people lookups or ticket information, the card shows fields that were configured to be displayed. However, any other fields provided by the underlying API are also available to be used for any follow up questions.
5. User feedback or responses to previously provided responses will influence the Moveworks Assistant’s decision to call the same plugin or other plugins.
   1. Particularly in the case of repeated requests for the same information, the reasoning engine may not provide the exact same answer again and again if the user’s requests indicate that the answer was not helpful.
6. It may be used to provide more empathetic or situationally aware responses if the user has had trouble getting a successful response.

How long does this context window last?

Context is automatically cleared every 24 hours from our Agentic AI reasoner. This means that any conversation older than a day will be removed from the chatbot’s memory, ensuring that your interactions remain relevant and up-to-date. When chat history gets too long, it can confuse the LLM (large language model), leading to less accurate, less relevant, or slower responses. This is why we clear the contextual history automatically behind the scenes for users. Even if a conversation spans multiple days, the most recent conversation will continue to be included in the model’s context. This overrides the standard 24-hour look back window.

Here’s an example with timestamps to help explain how our new context-clearing behavior works.Let’s say over the last couple of days, you’ve chatted with the Moveworks AI Assistant about a few different things:

• April 30, 9:00 AM – You asked about how to set up a new hire for their first day, including system access and benefits enrollment.
• April 30, 4:00 PM – You had a quick issue with your VPN not connecting while working remotely.
• May 1, 2:00 PM – You asked for help assigning Salesforce roles to that new hire.

Now it’s May 2, and you come back to the bot and say:
“David and Abhishek on my team also need access.”

Because the May 1 conversation is still within the 24-hour window, the assistant understands that you’re referring to Salesforce and that both of your employees need the same Salesforce role access as Alex— even though you didn’t mention Alex.

It won’t get confused by the older onboarding or VPN questions from April 30 — those are outside the 24-hour context window and are no longer retrieved.

✅ This means faster, more relevant answers — without the bot getting sidetracked by unrelated topics.

Learn more about context management options here.