WhatsApp is where the work already happens.

An AI WhatsApp assistant for business can run your inbox the way a steady office manager would, minus the coffee breaks. It reads every incoming thread, works out what each customer or supplier actually wants, drafts a reply in your voice, and then waits. Nothing goes out until you approve it. When a message hides a task inside it, the assistant carries that task into the tools you already use. That is the job Clark does inside WhatsApp.

For many businesses, WhatsApp is the back office

For a lot of small businesses, WhatsApp is where the work happens: orders, questions, and supplier updates all land there. Bookings, quotes, complaints, and the blessed "payment sent" screenshot pass through the same app the owner checks in the gaps between doing everything else. In many markets, WhatsApp is a normal way for customers to reach a business, which means one green inbox does the work of a CRM, a calendar, and a front desk, without the salary of any of them.

That convenience has a cost: threads stack up through the day. A booking mentioned at nine in the morning is buried by noon and forgotten by two. A supplier confirms a delivery and the note never reaches the right order. A quote gets promised, then vanishes under forty newer messages about something else entirely. The information is all there, filed under chaos, in a format nobody can keep up with by hand, especially when the person reading the messages is also the person doing the work.

Clark was built for that setting: an assistant that lives inside WhatsApp and never loses the thread.

What does an AI WhatsApp assistant for business do?

An AI WhatsApp assistant for business reads your threads, decides what each one needs, drafts a response for you to approve, and then does the task the message implies. Clark does these four things in order.

It reads every thread

Clark reads every conversation in the connected WhatsApp account, both the ones you have opened and the ones still sitting there unread and faintly accusing. It follows the history of each thread, so a message that only makes sense in light of last Tuesday's exchange gets read in that light. Nothing slips through because the day got loud or the phone got left face-down on a counter.

It understands what each thread needs

After reading comes the harder part: working out what each thread is asking for. A price question needs an answer, a "can you fit me in Thursday" needs a booking, a photo of a purchase order needs an invoice, and a supplier writing "shipment delayed to Friday" needs that fact pinned to the right job. A customer who is clearly, thoroughly annoyed needs a real person, so Clark flags that thread for you to handle yourself.

It drafts a reply in your voice

Clark writes the reply for you, in the tone you already use with your customers. It takes its cues from how you have answered similar messages before, so your quotes still sound like your quotes and your thank-you still sounds like yours. Then the draft waits for you. You read it, tweak a word if you like, and send it, or you ask Clark to have another go.

It turns messages into actions

A plain chatbot stops at the reply. When a thread contains a task, Clark carries that task into the other tools you run:

• A booking becomes an event on your calendar, with the name, time, and details already filled in.
• An order becomes an invoice, ready for you to check and send.
• A supplier update becomes a note on the right deal, so the status is current without anyone retyping a thing.

The message and the action stay linked, so you can always trace where an invoice or a calendar event came from.

How is this different from a chatbot?

A chatbot answers messages. Clark is an operator: it answers messages and then does the work those messages create. It runs on its own hosted machine, keeps working through the day whether or not you are watching, and treats each message as the start of a small job. The reply is the first half of that job. The calendar event, the invoice, and the updated deal are the second half, which usually gets dropped and which Clark picks up.

Who stays in control?

You do, at every step: Clark is built to draft and prepare, and to stop and wait for a human on anything that leaves a mark. That principle applies across the whole product.

Nothing is sent without your approval

Replies stay drafts until you approve them. You see what Clark wrote, and you decide whether it goes out the door. Over time you will trust some kinds of replies more than others, and you can loosen the reins at your own pace as that trust builds.

High-stakes moves get an explicit ask

Some actions carry more weight than a friendly message: issuing an invoice, changing a booking, anything with money or a firm promise attached. Clark treats those as high-stakes and asks you first, in plain language, before it moves.

Every action is logged

Clark keeps a written record of every draft, every action, and every request for approval, and when each one happened. If you ever want to know why an invoice exists or where a calendar event came from, the log has the answer. That paper trail lets you check the work of an assistant that acts on your behalf. The FAQ goes into how approvals and logging work in more detail.

Do your conversations stay yours?

The content of your threads belongs to your business, and Clark works inside your business's WhatsApp to do your work. It reads what it needs to draft and act, and the logs show you exactly what it touched and when. Clark works through WhatsApp as a tool it operates on your behalf. It is not a WhatsApp product and not an official WhatsApp partner. It sits alongside the app you already run and helps you keep up with the flood.

What does this look like day to day?

Day to day, you open WhatsApp and find the reading and the busywork already handled.

Take a Tuesday morning at a hair salon. Overnight, six people messaged about appointments, because people book their haircuts at eleven at night for reasons known only to them. By the time the owner unlocks the phone with one hand and a coffee in the other, Clark has drafted replies to all six, turned three firm bookings into calendar events, and flagged a message from a supplier about a colour line that is out of stock. The owner reads down the list, sends five drafts as written, edits one, and is ready before the first client is out of their coat.

Or picture a wholesaler who takes orders by message all day. A regular sends through a list of items with the punctuation of someone typing next to a forklift. Clark drafts a confirmation in the owner's usual tone and prepares the invoice with the quantities already filled in. The owner checks the numbers and approves. The customer gets a fast, correct reply, and nobody had to retype a single line into a separate system that hates them.

Or take a contractor who lives between sites and is rarely near a desk. A supplier writes that the materials are delayed to Friday. Clark records that against the right job, so when the contractor opens that project later in the week, the delay is already noted, in writing, where it belongs.

If you want a fuller sense of the rhythm, we wrote up a week with your Clark as a longer walk-through.

What are Clark's limits?

Clark has real limits. It is an operator that reads, drafts, and prepares, and your judgment still decides the messages that matter.

• It can misread a thread. Conversations get ambiguous, and Clark can read the room wrong. The approval step exists for this reason: you are the check on its work.
• It does not send on its own. If you want fully automatic replies with no human anywhere in the loop, Clark is the wrong tool, because drafts wait for you every time.
• It is not a lawyer or an accountant. Clark prepares an invoice or a reply. It does not give legal or financial advice, and it will not sign off on anything for you.
• It works through WhatsApp. Clark helps you run your WhatsApp inbox. It has no official partnership with WhatsApp and works within WhatsApp's own rules and limits.
• It is early. Clark is in beta, gets used and sharpened week by week, and some corners will get smoother over the coming months.

None of these limits should stop you if the daily message load is eating your week. They are the reason Clark keeps you in the loop: it does the reading and the drafting, and you approve the replies and the actions.

Where to start

The simplest way to picture Clark: your own WhatsApp, with the reading, the sorting, and the first drafts already done, every action logged, and nothing sent until you approve it.

Clark is in Public Beta at 250 EUR per month, locked at that price for as long as you stay subscribed. The launch price is 488 EUR per month. You can see the current terms on the pricing page.

Clark is made by Weblyfe. It works alongside the tools a small business already runs, inside the app where the work already lands.