TuAgente

Overview

TuAgente answers a small business's WhatsApp and Instagram chats with that business's own prices and stock, taken from the catalog it uploads in Excel or PDF. The owner sets the rules: whether the agent can give discounts and how much, when it hands a chat to a person, and which features are on. The dashboard is where the owner and their team see every conversation, step in when the agent can't, and follow each customer through to a sale. I joined as CMO and redesigned the dashboard, the sign-in pages, and the marketing site, and I keep building on them with the team.

Problem

The people using the dashboard run shops, not support centers. Most chats the agent handles alone; the ones it can't are the ones that cost a sale if nobody sees them in time. The dashboard's main job is to say, in a glance, who is waiting for a person, for how long, and why the agent stopped.

Process

1. 01I started with the foundation: Satoshi, one set of line icons, and the brand mark, then restyled every dashboard section, the marketing site, and the sign-in pages in the same pass, on September 11.
2. 02I gave copper one main job: the action on each screen, Responder, Tomar, Contanos sobre tu negocio. Status uses green and red with a word next to it, so the agent's state and a customer waiting don't read as buttons.
3. 03A client told us the grey text was hard to read. My first fix took the faintest text from 3.35:1 to 6.05:1, past the WCAG AA line, and the client still found it hard. So I went further the same day: near-black grounds, lighter text, and the faint tier at 7.71:1 on cards, AAA, with borders brightened so cards still separate.
4. 04I restructured Conversaciones around the people waiting. 'Te esperan' is the first tab, and inside a chat the reason the agent stopped sits in a card with three actions: take it, resolve it, or teach the agent so it doesn't happen again.
5. 05I moved optional features out of the catalog page into their own Módulos tab, then made that tab only switches the owner can flip, with each feature's settings on the page it acts on. A feature one client asks for ships behind a visible switch instead of appearing for everyone.
6. 06I cut helper text twice: first the greeting banner and captions on Inicio that repeated the number above them, then the explanations in Módulos, Agenda, and the customer panel that described what the screen already shows. A line stays only where it prevents a mistake.

Reflection

The readability fix was built for one client's eyes. I pushed the whole palette darker and every faint label brighter for everyone, without testing with a wider group of owners. If the complaint comes back, I don't think the answer is a third round of the same nudge; it's asking whether the dashboard needs a faint text tier at all.