If you run your business's WhatsApp, you probably know this feeling: during the week you answer what is urgent and everything else gets buried. A quote nobody followed up on, a customer who asked about price and never wrote again, a conversation that went cold without you noticing. A weekly chat review routine with Claude keeps that from slipping through: once a week, using your own criteria, Claude looks at your real chats and brings you the ones that need a decision from you.
This guide is a practical, step-by-step way to set it up. You do not need to code. If you have not connected Claude to your WhatsApp yet, start with how to connect WhatsApp to Claude and come back.
What a weekly review routine is
It is an instruction you write once and repeat every week: what to look at, in what order, and what you want back. It is not a chatbot that answers your customers. It is a review you run yourself, with an assistant that reads faster than a person and never gets tired.
For it to work, Claude has to be able to read your real account. That is what the Chatty Connector (page in Spanish) does: it links your WhatsApp to Claude and lets it read your pending queue, the full history of each conversation, your funnels and labels, and the templates you have approved.
Step 1: Decide what you are looking for
Before writing anything, decide what counts as a problem in your business. One short paragraph is enough: "for me, a chat is at risk if the customer asked something more than three days ago and nobody answered." That sentence is the heart of the routine, because without a criterion Claude can only guess.
A few questions help: how many days without an answer is too many in your line of work? Which customer messages signal they want to buy (price, availability, payment methods)? Which chats do you never want to see (suppliers, family, spam)?
Step 2: Start from the pending queue
The Connector builds, on its own and every hour, a queue of pending chats: the ones that are going cold, with the reason for each (no reply, not closed, or a buying signal that was left hanging). That queue does not exist inside the Chatty app: the assistant builds it.
So the first line of your routine is always the same: ask Claude to read the queue. It is the cheapest shortcut to what matters, because it does not have to go through every chat from the week one by one.
Step 3: Ask it to read the history before giving an opinion
A queue tells you who is waiting, but not why. The third step is to ask Claude to open the whole conversation for each case and tell you where it came from: what was asked, what was answered, where it stopped. That avoids the most common mistake: replying to someone without knowing you had already discussed price last week.
A good instruction is: "for each pending chat, read the whole conversation and summarize in two lines what the customer wants and what we still owe them."
Step 4: Cross-check with your funnels and labels
If you use funnels (for example "inquiry → quote → close") and labels, Claude can look at them alongside the chats. Ask for concrete things: how many chats sit in each stage, which have not moved in over a week, and which labels repeat among the ones that went cold.
This turns a list of chats into a snapshot of your sales process. If 70% of your cases get stuck at "quote sent," you already know where to improve, and that is worth more than answering one loose message.
Step 5: Let it propose, and you decide
With the plan that reads and writes (Connector Plus), Claude can propose a reply for each case. The important rule: the reply only goes out once you approve it. With the read-only plan (Connector), Claude analyzes and brings you the summary, but it does not write in your chats.
One practical detail: outside the 24-hour window, WhatsApp only lets you message a customer with a template approved by Meta. The Connector can show you which ones you have approved. If the chat is closed, Claude's proposal would have to go out with one of those templates.
Step 6: Save the routine and repeat it
When the result works for you, ask Claude to leave the instruction written out so you can paste it next week. Pick a fixed day and time (for example, Monday first thing) and treat it as a five-minute meeting with yourself.
If you would rather not write the text by hand, the Chatty plugin for Claude Code includes a routines skill that interviews you (what you look at first, what is urgent for you, what you would rather not see) and builds the routine with your criteria. It is a Claude Code feature; it does not exist in claude.ai.
Common mistakes
- Asking "review everything" with no criterion. Claude will hand you a generic summary. The clearer what you are looking for, the better the result.
- Mixing the review with sending. First understand the picture; then decide what to answer.
- Approving replies without reading them. The approval is your control: use it.
- Only counting messages. Also look at how long a chat takes to move from one stage to the next.
To go deeper into the underlying problem, see also the guide on WhatsApp after-hours messages.
Frequently asked questions
Do I need to code to build the routine?
No. The routine is written in plain language, like an instruction to a person. The only technical part is connecting Claude to your WhatsApp once, and the Connector page walks you through it.
Does Claude answer my customers on its own?
No. With the Connector plan (USD 50 per month) it only reads and analyzes. With Connector Plus (USD 80 per month) it can propose replies, but they go out only once you approve them.
How much does it cost to try?
There is a 15-day trial, with no charge and no card required to start. After that, the monthly read-only plan is USD 50 and the one that also writes is USD 80, and there is an annual plan.
How often should I run the review?
For most businesses, once a week is enough to catch chats that went cold. If you get many inquiries a day, you can do a short pass daily and keep the deep one for the week.
