# How to formalize client approvals without WhatsApp

- Author: Givaldo Marques da Silva
- Published: 2026-10-12
- Category: Creative operations
- Canonical URL: https://blog.wikimee.com/en/como-formalizar-aprovacoes-de-clientes-sem-whatsapp/
- Language: en
- Other versions: [pt-BR](https://blog.wikimee.com/como-formalizar-aprovacoes-de-clientes-sem-whatsapp/index.md) [es](https://blog.wikimee.com/es/como-formalizar-aprovacoes-de-clientes-sem-whatsapp/index.md)

> A 6-step walkthrough to take client approval out of WhatsApp: mapping, named approvers, recorded decisions with dates and a frozen version.


**The process:** formalizing client approvals involves 6 steps, from mapping decisions to tracking the approval cycle. Start with a two-week pilot involving one client to assess the workflow before extending it to other accounts.

The [guide to client approvals without WhatsApp](/en/aprovacoes-de-cliente-sem-whatsapp/) explains the context and the approach: keep conversations in chat and record decisions in the workflow. The steps below explain how to set up that process.

## The 6 steps

### 1. Map where decisions happen today
For one week, record how many approvals arrive through chat, email and phone calls. Identify who makes the decisions and check whether those people have been appointed as approvers.

### 2. Name one approver per stage
Assign responsibility for the decision at each stage. If the client requires two approval levels, set up two consecutive stages, each with a designated approver.

### 3. Define what counts as a valid approval
Agree in writing with the client that approvals must be recorded in the workflow, with the date, time and version. Under this agreed process, chat messages remain part of the discussion and require confirmation in the workflow before the asset can be released.

### 4. Centralize the decision in a recorded workflow
Send the asset through a link so the client can review the current version and approve it or request changes on the material itself. This keeps the file and the decision together.

### 5. Freeze the approved version
Keep the approved version unchanged. Any subsequent edit creates a new version that must go through approval again. The history shows which file each decision refers to if someone says &quot;I approved something else&quot;.

### 6. Measure the cycle
Track the days between submission and decision, review rounds per asset and rework. For broader context, Asana reports in its State of AI at Work 2025 that knowledge workers spend 55% of their time on coordination and follow-up activities. This percentage does not specifically measure approval cycles; use your own operational data to assess this stage.

## Handling approvals outside the workflow

If someone approves by voice note in week two &quot;just this once&quot;, record the context and ask the approver to confirm the decision in the workflow for the specified version. The team can send a reminder in chat, but the record must distinguish the approver from the person who entered the information.

Agreeing on where to record decisions is also part of managing client relationships. The [Academee Approval and Feedback learning journey](https://academee.ai/jornadas/aprovacao-feedback/), available in Portuguese, explores the process through learning tracks, including Central de Aprovação Unificada (Unified Approval Hub).

## Metrics for the first two weeks

During the two-week pilot, track four indicators to assess whether to extend the process to other accounts:

1. Average time between submission and decision.
2. Review rounds per asset.
3. Approvals recorded in the workflow versus approvals in chat.
4. Estimated rework avoided by preserving the approved version.

The third metric tracks adoption. If half the decisions still take place only in chat after two weeks, check where the client encounters difficulties. Review the steps needed to approve and the agreement with the client before insisting on the rule.

## How to introduce the process to the client

Explain what will change and how the record will be used. The following template assumes that the workflow supports one-click approval: &quot;Starting with the next campaign, every approval will go through a link where you see the exact version and decide in one click. The conversation stays here on WhatsApp, as usual. The change protects both of us: what was approved, in which version and when gets recorded, and the memory debate is over.&quot; Before sending it, check that the wording matches how the chosen tool works. The conversation can continue on WhatsApp, with the decision linked to the version in the workflow.

## Three client profiles, three approaches

**The informal client**, who prefers voice notes and chat, can keep using that channel to discuss the work. Introduce the link as the place to check the version and record the decision. Observe whether approving there takes more effort than typing &quot;approved&quot;, and adjust the workflow if necessary.

**The corporate client**, with a legal team and defined approval levels, needs a workflow that respects those responsibilities. Set up one stage per decision maker and include an approval history report in the agency&#39;s deliverables, taking the client&#39;s audit requirements into account.

**The client with limited time to review** needs an agreed response deadline and reminders. Record submissions and configure the automated notifications included in the workflow. If a scheduling dispute arises, the history shows how long each stage took.

Adapt the way you introduce the process to each client&#39;s routine. Needing an audit report is different from needing to find the asset and respond quickly.

## Frequently asked questions

**Where do we start if the whole portfolio approves by WhatsApp?**
Start with one client and one type of asset for two weeks. Choose an account with recurring rework and track the results to assess whether to extend the process.

**What do we do with the old history of chat approvals?**
Prioritize new approvals. Reconstructing the entire chat history takes work and is not a prerequisite for starting. Retain older records in line with the account&#39;s obligations.

**How do we adapt the workflow if the client already has a process?**
Adapt the 6 steps to the client&#39;s approval levels and rules. Define who approves at each stage, where the decision is recorded and how the approved version will be preserved.

**Is a formal approval process useful for small, one-off projects?**
Yes. For a one-off project, start with one stage, one approver and a preserved approved version. Rework consumes hours on these projects too and can reduce the expected margin.

**What should the proposal say about this process?**
Describe what will be provided: each approval will include a recorded version, date and approver, with a report available. This lets the client assess the process before the first project.

To implement steps 4 and 5, assess a platform that combines approvals and version control. [Explore Wikimee&#39;s approval workflow](https://www.wikimee.com/pt_br/produtos/) and book a workflow assessment using a real project.

### Sources and references

- Asana, State of AI at Work 2025, source of the 55% figure. Further reading: Anatomy of Work Index, [asana.com/resources/anatomy-of-work-index](https://asana.com/resources/anatomy-of-work-index)
- Law 13.709/2018 (LGPD), full text at Planalto, in Portuguese: [planalto.gov.br](https://www.planalto.gov.br/ccivil_03/_ato2015-2018/2018/lei/l13709.htm)

---

Blog | Wikimee · https://blog.wikimee.com/en/como-formalizar-aprovacoes-de-clientes-sem-whatsapp/
