# About the Callout activity package

> The **UiPath.Callout.Activities** package allows you to build and design custom callouts to guide users through attended automations. The interface uses drag-and-drop components that bind the callout fields to the variables in your workflow. Not only can you show multiple callouts at the same time, but you can also show multiple instances of a callout at the same time. You can use this activity package in the context of [Trigger-based attended automation](https://docs.uipath.com/studio/standalone/latest/user-guide/trigger-based-attended-automation-introduction).

The **UiPath.Callout.Activities** package allows you to build and design custom callouts to guide users through attended automations. The interface uses drag-and-drop components that bind the callout fields to the variables in your workflow. Not only can you show multiple callouts at the same time, but you can also show multiple instances of a callout at the same time. You can use this activity package in the context of [Trigger-based attended automation](https://docs.uipath.com/studio/standalone/latest/user-guide/trigger-based-attended-automation-introduction).

You can create callouts using the [Form Builder](https://docs.uipath.com/activities/other/latest/workflow/form-builder) that you use to create forms, as well. Callouts are also `uiform` files. The main difference between callouts and forms, is that callouts are bound to an UI element, following it if it's moving, or not showing if the element is hidden.

You can also create callouts using custom HTML files, similarly to how you would create an HTML form file. Check out [this tutorial](https://docs.uipath.com/activities/other/latest/workflow/design-forms-using-custom-html) to learn how to build a custom HTML form or callout file.
:::note
Given that callouts are **uiform** files, you can use activities from the [Form.Activities](https://docs.uipath.com/activities/other/latest/workflow/about-the-form-experience) on them, as well. For example, if you're showing a callout, and you want to update its form values at runtime, you can use the [Set Form Values](https://docs.uipath.com/activities/other/latest/workflow/set-form-fields-activity) activity.
:::

The table below shows the activities available with the package:

| Activity | Description |
| --- | --- |
| [Show Callout](https://docs.uipath.com/activities/other/latest/workflow/show-callout-activity) | Shows a callout for a certain UI element. |

:::note
UiPath.Callout.Activities versions above **23.4** are compatible only with **Studio 2023.4.0** or higher, and versions **23.4.X** or higher of the following activity packages:
* [UiPath.Form.Activities](https://docs.uipath.com/activities/other/latest/workflow/about-the-form-activities-pack)
* [UiPath.System.Activities](https://docs.uipath.com/activities/other/latest/workflow/about-the-system-activities-pack)
* [UiPath.UIAutomation.Activities](https://docs.uipath.com/activities/other/latest/user-guide/about-the-ui-automation-activities-pack)
:::

## Pre 23.4 Callout experience

The pre 23.4 callout experience exists for **Callout.Activities** package versions lower than **23.4.X**. To switch to the current experience, learn how to use the [current activities](https://docs.uipath.com/activities/other/latest/workflow/callout-activities).

The **UiPath Callout Designer** is a customized implementation of the form.io engine that provides a drag-and-drop form builder experience in UiPath Studio. The UiPath Callout Designer functionality complies with internal security requirements.

:::note
UiPath.Callout.Activities versions 2.0.X are compatible only with the 2.0.X versions of the [UiPath.Form.Activities](https://docs.uipath.com/activities/other/latest/workflow/about-the-form-activities-pack) package.
:::