# 3. How to Create a Request

The **Requests** module is your single pane of glass for all client-initiated actions—support tickets, callback bookings, document uploads, feedback submissions, and more. Each request is automatically tied to a specific **Client** and **Project**, ensuring that nothing falls through the cracks. By using Requests you gain:

1. **Centralized Tracking:** Every inquiry lives in one list with clear status indicators (Active, Archived).
2. **Structured Context:** Attach files, set time windows, and capture custom data so your team has everything they need.
3. **Accountability &amp; Audit:** Who opened, who owns, when it was created—and a complete message thread for full transparency.

Below is a step-by-step guide to **creating** and **viewing** requests in the system.

**1. Open the Requests Module:** From the left-hand nav, click **Requests**. The main Requests list shows total count, filters, search, and the table of existing requests.

**2. Launch the “Add Request” Form:** Click the **+ Add Request** button in the top-right corner.

**3. Complete the General Section** Fill in each field as follows:

<div class="_tableContainer_16hzy_1" id="bkmrk-field-description-na"><div class="_tableWrapper_16hzy_14 group flex w-fit flex-col-reverse" tabindex="-1"><table class="w-fit min-w-(--thread-content-width)" data-end="2130" data-start="1302" style="width: 99.7619%; height: 178.21px;"><thead data-end="1414" data-start="1302"><tr data-end="1414" data-start="1302" style="height: 29.7017px;"><th data-col-size="sm" data-end="1318" data-start="1302" style="width: 12.6629%; height: 29.7017px;">Field</th><th data-col-size="lg" data-end="1414" data-start="1318" style="width: 87.3265%; height: 29.7017px;">Description</th></tr></thead><tbody data-end="2130" data-start="1533"><tr data-end="1647" data-start="1533" style="height: 29.7017px;"><td data-col-size="sm" data-end="1550" data-start="1533" style="width: 12.6629%; height: 29.7017px;">**Name**</td><td data-col-size="lg" data-end="1647" data-start="1550" style="width: 87.3265%; height: 29.7017px;">Descriptive title (e.g., “Network Outage” or “Schedule Callback”).</td></tr><tr><td data-col-size="sm" data-end="1766" data-start="1748" style="width: 12.6629%;">**UID**</td><td data-col-size="md" data-end="1870" data-start="1766" style="width: 87.3265%;">System-generated unique ID (auto-increment).</td></tr><tr data-end="1776" data-start="1651" style="height: 29.7017px;"><td data-col-size="sm" data-end="1668" data-start="1651" style="width: 12.6629%; height: 29.7017px;">**Time range**</td><td data-col-size="lg" data-end="1776" data-start="1668" style="width: 87.3265%; height: 29.7017px;">(Optional) Select start/end dates to indicate when the request is valid or when the client is available.</td></tr><tr data-end="1894" data-start="1780" style="height: 29.7017px;"><td data-col-size="sm" data-end="1797" data-start="1780" style="width: 12.6629%; height: 29.7017px;">**Client**</td><td data-col-size="lg" data-end="1894" data-start="1797" style="width: 87.3265%; height: 29.7017px;">Pick the client from the dropdown. This cannot be changed after saving.</td></tr><tr data-end="2012" data-start="1898" style="height: 29.7017px;"><td data-col-size="sm" data-end="1915" data-start="1898" style="width: 12.6629%; height: 29.7017px;">**Project**</td><td data-col-size="lg" data-end="2012" data-start="1915" style="width: 87.3265%; height: 29.7017px;">Choose the project context (e.g., “Web Portal Support”).</td></tr><tr data-end="2130" data-start="2016" style="height: 29.7017px;"><td data-col-size="sm" data-end="2033" data-start="2016" style="width: 12.6629%; height: 29.7017px;">**Description**</td><td data-col-size="lg" data-end="2130" data-start="2033" style="width: 87.3265%; height: 29.7017px;">Free-text details provided by the client or added by you for internal context</td></tr></tbody></table>

</div></div><p class="callout info">**Note**: Once saved, you cannot change the client of the request.</p>

**4. Add Custom Data (Additional Information):** Use the **Additional information** JSON tree to set any structured fields (e.g., `priority: "high"`, `documentType: "KYC"`). This is ideal for downstream automation or reporting.

**5. Attach Supporting Files:** Drag-drop or click **Browse** under **Attached file(s)** to upload screenshots, logs, or PDFs. Valid formats: JPG, PNG, PDF.

**6. Save the Request:** When ready, click **Save** at the bottom of the panel.  
The panel closes and your new request appears at the top of the Requests list with **Status = Active**.  
**To view information about created requests**, go to the **Requests** tab and click on the name of the specific request. A drawer will appear with information about it:

##### Viewing &amp; Managing a Request

**Open a Request:** Click any request’s **Name** in the list.  
**Inspect Details:** A **Request information** drawer opens on the right, displaying:

1. General fields (Name, Time range, Client, Description)
2. Status badge (Active, Archived)
3. Attached files and any custom data
4. Full message thread and metadata

##### Conclusion

By leveraging the Requests module you ensure that every client touchpoint is:

1. **Logged:** No more lost emails or ad-hoc notes.
2. **Linked:** Always tied to the right client and project for clear ownership.
3. **Transparent:** Full audit trail and effortless status tracking.

This standardized process boosts team efficiency, improves response times, and elevates client satisfaction across all service lines