***
title: Steering Conversational Plugins
position: 3
excerpt: ''
deprecated: false
hidden: false
metadata:
title: ''
description: ''
robots: index
next:
description: ''
---------------
The Agentic Reasoning Engine understands how to use your plugins without the need for any prompt engineering. However, your organization may still want to customize that treatment for special situations. For example:
* The reasoning engine assumes the `start_date` of any sick leave should be today, but in your organization, sick leaves are submitted retroactively with a doctor's note.
* The reasoning engine assumes the `country_code` should be set based on the current user's profile, but you want it to ask.
* After the reasoning engine executes a plugin, you want to promote specific related plugins (e.g. present a `Book timeoff plugin` after user views their `Timeoff balance plugin`)
Adding **instructions** to your plugin makes it possible for the Agentic Reasoning Engine to understand & achieve your desired behavior.
* [Triggering instructions](/agent-studio/core-concepts/conversational-plugins/natural-language-triggers#triggering-instructions)
* [Slot instructions](/agent-studio/conversation-process/slots#slot-instructions)
* [Progress update instructions](/agent-studio/conversation-process/activities#progress-update-instructions)
* [Response instructions](/agent-studio/conversation-process/activities#plugin-result-instructions)
Don't worry, these instructions won't compromise your AI agent's guardrails & safety protections or attack other plugins. Our reasoning engine treats them as **Tool Outputs**, which can't break your AI agent.
If you want to strictly enforce plugin behaviors, consider using [policies](/agent-studio/core-concepts/agentic-automation-engine/policies) or managing other logic in the [Action Orchestrator](/agent-studio/actions)