# 3. How to Configure Statuses

Effective status management lets you tailor client and request lifecycles to your business processes, ensuring clear visibility of progress and automating downstream actions. In **Settings &gt; Configurations &gt; Statuses**, you’ll find two panels—**Client status** and **Request status**—that govern how records appear and transition within the **Clients** and **Requests** modules, respectively.

##### Use Cases

1. **Customized Pipelines:** Define stages like “Lead,” “Prospect,” and “Customer” for clients, or “New,” “In Review,” and “Completed” for requests, matching your organization’s terminology.
2. **Default Routing:** Set a default status (e.g., “Active” for clients) so that all new records start in a predictable state, reducing manual setup.
3. **Visual Prioritization:** Assign distinct colors to statuses (red for high-priority, gray for archived) to surface critical items at a glance.

##### Accessing the Statuses Configuration

To configure statuses, go to **Configurations &gt; Statuses** tab at the top. A tab with two sections will open:

1. **Client status (left):** In this section, you can manage the statuses you select for clients in the [Clients](https://wiki.wi.services/books/wifox-business-core-solution-wbcs/chapter/slients) module.
2. **Request status (right):** In this section, you can manage the statuses that you select for clients in the [Requests](https://wiki.wi.services/books/wifox-business-core-solution-wbcs/chapter/requests) module.

##### Adding a New Status

1. Click the **Add** button in the upper right corner of the corresponding section.
2. In the **Add status** form, enter:  
    **Name:** The display text (e.g., “Pending Approval”).  
    **Label:** A unique identifier used internally (e.g., `pending_approval`).
3. (Optional) Choose a **Color** by clicking one of the swatches—this color will appear as the status badge.
4. To make this your system-wide default, check **Make as default**.
5. Click **Save** to add the status.

##### Editing an Existing Status

1. Click the ✏️**Edit** icon next to the appropriate status.
2. In the **Edit status** sidebar, you can update:  
    **Name** (label remains read-only)  
    **Color**
3. Click **Save** to apply the changes.

##### Setting a Default Status

Only one status per panel can be default. New records automatically receive this status.

1. Hover over the status you want as default.
2. Click **Make as default**.
3. The “Default” badge will move to this status.

##### Deleting a Status

<p class="callout info">**Important:** You cannot delete a status marked as default or one currently in use by existing records.</p>

1. Ensure the status is **not** the default (see “Make as default” above to change defaults).
2. Click the **🗑️ Delete** icon next to the status.
3. Confirm the deletion when prompted.

<article class="text-token-text-primary w-full" data-scroll-anchor="true" data-testid="conversation-turn-306" dir="auto" id="bkmrk-by-thoughtfully-defi">By thoughtfully defining client and request statuses—complete with unique labels, colors, and defaults—you create a transparent, enforceable workflow that scales with your business. Regularly review and prune unused statuses to keep your system lean, and leverage status-driven automation (notifications, reports, transition rules) to streamline daily operations.

<div bis_size="{"x":143,"y":1470,"w":840,"h":89,"abs_x":729,"abs_y":1688}" class="text-base my-auto mx-auto py-5 [--thread-content-margin:--spacing(4)] @[37rem]:[--thread-content-margin:--spacing(6)] @[72rem]:[--thread-content-margin:--spacing(16)] px-(--thread-content-margin)"><div bis_size="{"x":143,"y":1470,"w":840,"h":89,"abs_x":729,"abs_y":1688}" class="[--thread-content-max-width:32rem] @[34rem]:[--thread-content-max-width:40rem] @[64rem]:[--thread-content-max-width:48rem] mx-auto flex max-w-(--thread-content-max-width) flex-1 text-base gap-4 md:gap-5 lg:gap-6 group/turn-messages focus-visible:outline-hidden" tabindex="-1"><div bis_size="{"x":143,"y":1470,"w":840,"h":89,"abs_x":729,"abs_y":1688}" class="group/conversation-turn relative flex w-full min-w-0 flex-col agent-turn"><div bis_size="{"x":143,"y":1470,"w":840,"h":67,"abs_x":729,"abs_y":1688}" class="relative flex-col gap-1 md:gap-3"><div bis_size="{"x":143,"y":1470,"w":840,"h":22,"abs_x":729,"abs_y":1688}" class="flex max-w-full flex-col grow"><div bis_size="{"x":143,"y":1470,"w":840,"h":22,"abs_x":729,"abs_y":1688}" class="min-h-8 text-message relative flex w-full flex-col items-end gap-2 text-start break-words whitespace-normal [.text-message+&]:mt-5" data-message-author-role="assistant" data-message-id="fef3eac9-ed5d-4936-b7c1-a9fc84e578e9" data-message-model-slug="o4-mini-high" dir="auto"><div bis_size="{"x":143,"y":1470,"w":840,"h":22,"abs_x":729,"abs_y":1688}" class="flex w-full flex-col gap-1 empty:hidden first:pt-[3px]">  
</div></div></div><div bis_size="{"x":143,"y":1492,"w":840,"h":22,"abs_x":729,"abs_y":1710}" class="flex justify-start">  
</div><div bis_size="{"x":143,"y":1515,"w":840,"h":22,"abs_x":729,"abs_y":1733}" class="mt-3 w-full empty:hidden">  
</div></div><div bis_size="{"x":143,"y":1537,"w":840,"h":22,"abs_x":729,"abs_y":1755}" class="absolute"><div bis_size="{"x":143,"y":1537,"w":840,"h":22,"abs_x":729,"abs_y":1755}" class="flex items-center justify-center">  
</div></div></div></div></div></article>