Intent identification AI agent
On this page
Intent identification AI agent
This AI agent analyzes and identifies the input email body intent. A list of admin-configured intents are compared with the input email body for a potential match.
Workflow
The agent fetches the email body using a given email sys_id.
-
Fetch the email body and execution context for the intent analysis and continue with the next step.
-
Check for malicious attempts, such as prompt injections.
-
Analyze the input to determine the overall thread context and the latest sender’s goal, which can represent either an actionable request, expression, statement, or interest. The email body can include a conversation or email thread involving multiple participants.
-
Perform intent analysis to evaluate whether a given input utterance semantically matches an intent from an admin-configured list.
<table><thead><tr><th>
Field
</th><th>
Description
</th></tr></thead><tbody><tr><td>
Allow third party to access this AI agent
</td><td>
When enabled, third-party AI agents can use this agent. This value is off (false) by default. This setting is defined in the AI Agent configs [sn_aia_agent_config] table on the External discoverable field.
</td></tr><tr><td>
Allow AI specialists to access this AI agent
</td><td>
When enabled, AI specialists can use this agent. This value is off (false) by default. When set to true, more configuration options for tools become available so that an AI specialist can map inputs and response templates to tool outputs. This setting is defined in the AI Agent configs [sn_aia_agent_config] table on the Specialist enabled field.
</td></tr><tr><td>
Manage long-term memory
</td><td>
When enabled, all previous user interactions are used as context for the LLM. This value is off (false) by default. This setting is defined by the sn_aia.ltm.enable_long_term_memory system property. For more information, see ServiceNow Otto AI agents reference.
</td></tr><tr><td>
Tools
</td><td>
-
Scripts
Context Fetcher
Intent Fetcher
</td></tr><tr><td>
Allowed user roles The specific user roles that can access this AI agent.
</td><td>
snc_internal, snc_external
</td></tr><tr><td>
Data access roles The specific user identity roles that determine which data the AI agent can access and what actions it can take.
</td><td>
intent_identification_ai_user, sn_notif_agents.notification_ai_reader
</td></tr><tr><td>
Triggers
</td><td>
Optional. None defined by default. An admin can specify triggers if desired. For more information, see Add a trigger to an AI agent.
</td></tr><tr><td>
Channels
</td><td>
Configure an assistant for Virtual Agent or ServiceNow Otto panel using Assistant Designer.
</td></tr><tr><td>
Used in agentic workflows
</td><td>
Intent to Action
</td></tr></tbody> </table>Learn more about Notifications in Notifications.
Parent Topic:Notifications AI agents
Keep exploring.
Find another answer, or bring this documentation into your own tools.