# Welcome Video and Acknowledgement
### Overview
This use case for Trackers demonstrates how to create automated workflows that deliver content tailored to a user's country or language. In this example, we’ll send send welcome videos to New Hires. These videos will require acknowledgement and also show in the user's primary language.
These form will be followed by an Employee Mood Tracker prompt.
Features used in this example:
| Feature | Purpose |
| ----------------------- | ----------------------------------------------- |
| Form Workflow | Automates sending forms at login/scheduled time |
| Send Form Action | Directs a specific form to a user/team |
| Description Add-On | Displays videos, welcome text |
| Language-Specific Forms | Tailored communication by audience segment |
***
### **Create a Tracker and Form**
To get started, we will first need to setup our tracker which will record the user acknowledgements. In this tracker we will create the fields **Acknowledgment** (to track our English users) and **Reconocimiento** (to track our Spanish users). We will configure these columns to be the [**Checkbox Type**](https://guides.mangoapps.com/user-guide/trackers/tracker-column-types#check-box) with only 1 option. This option will be the acknowledgement description.
We will also show the **@ Submitted By** system column so we can see who has acknowledged the video.
Next, we will [create two Forms](https://guides.mangoapps.com/user-guide/trackers/forms/create-a-form), an English form and a Spanish form. These two forms will be utilized in the workflow configurations.
For our forms, we will make use of the [**Description Add-On**](https://guides.mangoapps.com/user-guide/trackers/forms/edit-a-form#add-on) form feature to insert welcome text and the Welcome Video.
Add in the matching language version **Checkbox Field** for "Acknowledgement" and mark as **Required**.
The Description form feature uses a rich text editor to support multiple languages, allowing you to create a separate form for each language.
In this example, we have created **separate forms** for English speakers and Spanish speakers:
* "Welcome to ACME Hub!" (English)
* "¡Bienvenidos a ACME Hub!" (Spanish)
Each form’s **Title**, **Description**, and **Acknowledgement text** has been customized to reflect the appropriate language.
***
### **Set Up the Form Workflows**
In the next step, we will [create workflows](https://guides.mangoapps.com/user-guide/trackers/tracker-workflows/creating-a-tracker-workflow) for our forms to ensure the right user segments receive the forms. We will create two workflows.
Go to your tracker and click **Tracker Tools → Manage Workflows**. Click **Create Workflow** and select the [**Form Workflow**](https://guides.mangoapps.com/user-guide/trackers/tracker-workflows/creating-a-tracker-workflow/form-workflow).
**Define the Trigger**:
Set **Trigger** to **At Scheduled Time**, **On Entry Added**, or **On Login** (depending on your need). For our example we will set the cadence to "**At Scheduled Time**" and "**Once**" on user login/access.
***
**Add Conditions for Language Segmentation**:
In this section, we will set conditions for the workflows to check user segments based on whether they are "**New Hires**" **AND** if they fall into the selected "**Language segments**".
For our example, we will configure our **Conditions** as:
**User is in Segment** = *New Hires*
**AND** (By default, this operator will be **OR**, click on it to change the operator)
**User is in Segment** = *Spanish Speakers Frontline* (for Spanish form), *English Speakers* (for English form)
You can define segments based on language preferences, regions, or user groups.
***
**Send the Appropriate Form**:
For the **Action**, we will select [**Send Form**](https://guides.mangoapps.com/user-guide/trackers/tracker-workflows/creating-a-tracker-workflow/form-workflow#sending-a-form).
**Form** = Select the corresponding form (e.g., "¡Bienvenidos a ACME Hub!" for Spanish speakers).
**Mode** = **Pop-up while using App** (to ensure visibility).
**Display Priority** = **High**. This will ensure that the welcome video form will display first in the event there are multiple forms requiring user interaction upon login.
**Allow User To Skip** = Disabled. We will disable this option since we want users to acknowledge the video.
**Save** the workflows.
***
### User Experience
With the tracker, forms, and workflows configured, our users can now begin populating acknowledgements. For this example, we have also configured a [Mood Tracker ](https://guides.mangoapps.com/user-guide/trackers/tracker-workflows/creating-a-tracker-workflow)form to appear after the Welcome Video form.
When a user fulfilling the user segment conditions logs in, they will be prompted to acknowledge the video via pop-up. The user can see their is another form that requires their attention via the slider icon beneath the pop-up. This Mood Tracker form, though, is optional, as we have enabled the **Skip** function in its workflow.
Depending on the user's language segment, they will receive the corresponding form configured through our workflows.
***
### **Manage Acknowledgements**
As end users interact with the forms, their acknowledgments will be tracked in our Welcome Video Viewership tracker. Acknowledgments from users in the English segment will be recorded in the **Acknowledgment** column, while acknowledgments from Spanish-speaking users will appear in the **Reconocimiento** column.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://guides.mangoapps.com/user-guide/trackers/tracker-use-cases/welcome-video-and-acknowledgement.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.