---
title: "Manage the Client Actions workflow"
description: "Review required actions, open the source conversation, add team notes, then complete or reopen the action."
language: en
canonical: https://mrailabs.com/docs/en/conversations-and-customers/manage-client-actions-workflow/
published: 2026-07-13T18:51:40.226212
last_verified: 2026-07-13T18:51:40.226212
audience: "For customer operations teams"
---

# Manage the Client Actions workflow
## How do I use Client Actions to follow customer requests?

Client Actions collects cases that require a team step, such as follow-up, pending replies, orders, bookings, or cancellations. Filter the list, review details and the source chat, add notes, then mark the action complete or reopen it.

- Start with Pending and high-priority actions.
- Read the source conversation before deciding.
- Use Done only after the required operational step is complete.

## Recommended workflow

1. Open Client Actions and select Pending.
2. Filter by type, category, and date.
3. Open the action and read its description, fields, and existing notes.
4. Open the source conversation when you need context or must contact the customer.
5. Add a company note and mark Done, or reopen the action when work returns.

> **Accurate status**
> Completing an action means the required work is finished, not only that a team member opened the card.

## Frequently asked questions

### Can I reopen a completed action?

Yes. Use Reopen when the action requires new work.

### When should I export CSV?

Use it for an authorized operational review outside the system while protecting customer data.

### How is Client Actions different from Customer Operations?

Client Actions tracks a required task or result; Customer Operations organizes conversations requiring human attention now.

[Open Client Actions](/client/actions)
