Actions
Actions are operations a Maven AI agent performs in external systems during a conversation, such as looking up an order, issuing a refund, resetting a password, or creating a case.
What Are Actions?
Actions are how a Maven agent gets work done. Based on what the customer needs, the agent can call an Action to read information from a system, like order status or account details, or to make a change, like processing a refund or updating a subscription. This is what moves an AI agent from answering questions to resolving them.
How Actions Work
- Connected to your systems: Actions call APIs in CRMs, billing platforms, order management, help desks, and other tools.
- Several types: Actions can be simple API calls, authenticated calls made on behalf of the logged-in user, chained multi-step workflows, or in-chat forms that collect details from the customer.
- Confirmation for changes: A common best practice is to have the customer confirm, often through a form, before an Action writes data.
- Scoped by policy: Segments and Charters control which Actions are available in each situation.
Frequently Asked Questions
How do Actions relate to function calling?
Actions build on tool use and function calling, with enterprise controls for authentication, eligibility, and auditability added on top.
Where are Actions created?
In the Capabilities area of Agent Designer, or through installed Maven Apps.
Table of contents
You might also be interested in
Don’t be Shy.
Make the first move.
Request a free personalized demo.