> ## Documentation Index
> Fetch the complete documentation index at: https://docs.volubile.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Workflow during the Call

> Workflows during the call allow your Volubile agent to access external data and execute actions in real-time during the conversation. This feature significantly enhances your agent’s capabilities.

<Tip>
  This feature is not enabled by default. Please contact <a href="https://support.volubile.ai" target="_blank">support</a> to activate it on your account.
</Tip>

<Info>
  The workflow during the call generally consists of:

  1. **Live call trigger** - Defines when and how the agent can use the action.
  2. **Intermediate actions** - Uses connectors to perform actions.
  3. **Respond to the agent** - Returns a result to the agent.
</Info>

## Configuring the Live Call Trigger

The live call trigger is the component that exposes functionality to your conversational agent during the call.

<Steps>
  <Step title="Define the Action">
    Start by setting up the basic information of the action:

    1. **Action Name**: A unique identifier that the agent will use to invoke this action (e.g., `get_customer_info`).
    2. **Action Description**: A clear explanation of the action's purpose (e.g. `Retrieves customer
               information based on a given identifier`).
  </Step>

  <Step title="Configure Dynamic Properties">
    Dynamic properties define the parameters that the agent must provide to execute the action:

    1. Click on **Add Item** for each required parameter.
    2. For each property, specify:

    * **Property Name** (e.g. `customer_id`).
    * **Description** (e.g. `The unique identifier of the customer to look up`).
    * **Type** (String, Boolean, Integer, etc.).
    * **Required** (indicate whether the parameter is mandatory).
  </Step>

  <Step title="Prepare Sample Data">
    Sample data allows you to test the functionality of your action:

    1. Load a sample data set and copy it into the "Sample data" field.
    2. Modify the sample data by adding the action parameters.
    3. Click on **Retest**.
  </Step>
</Steps>

<Note>
  The action description should clearly explain when and why the agent should use this action. A precise description helps the agent determine the right moment to utilize this feature.
</Note>

<Warning>
  Ensure that each property is correctly typed to avoid runtime errors. For example, if you are expecting a numeric identifier, use the `Integer` type.
</Warning>

## Configuring the Response

In the **Respond to the agent** step interface, you can define the response structure in JSON format using the data
selector to access variables from previous steps.

<Note>
  To return a result that the agent can use during the call, make sure that the last step in the flow is a
  **Respond to the agent**.
</Note>

<Tip>
  You can access pre-call context data in your action during the call. This allows you to reuse previously retrieved information as well as system variables.
</Tip>

<Card title="Configure Actions during the Call" icon="bolt" href="../../product/agents/actions#actions-during-the-call" horizontal />