I could make Slate’s WhatsApp integration more powerful.

It could have menus, suggestions, natural-language planning, summaries, reminders, maybe even a friendly little personality. It could try to become a second app inside WhatsApp, with commands branching into commands until the capture channel becomes another product to operate.

I do not want that.

Not because those features are impossible. Because capture is not planning.

Capture usually happens elsewhere

The task rarely appears at the correct desk, in the correct app, at the correct time. It appears while walking to a meeting, waiting for coffee, reading a message, standing in a hallway, or trying to leave the house.

This is why capture is hard. Planning apps want to be opened. Brains want to be done with the thought. The distance between those two wants is where tasks get lost.

A good capture surface is not necessarily the most elegant one. It is the one already open when the thought arrives.

For many people, that surface is WhatsApp. It is on the phone, on the desktop, in the pocket, in the hand. It is where people already send fragments before they are tidy enough for anything else.

Using a messenger for task capture is not about turning a planning app into a chat product. It is about meeting the thought where it already landed.

The messenger should not become the planner

If you remember “ask Priya about the invoice wording” while leaving a call, opening the full planning surface may be too much friction. Sending a message is almost nothing. Almost nothing is the standard capture has to meet.

But there is a line to avoid. A messenger channel can quickly become a second place to manage: commands, menus, suggestions, little attempts at conversation. Then you have not reduced friction. You have created another surface that needs reconciling.

Slate’s WhatsApp channel is deliberately thin. Pair once with an eight-digit code. Then use the simple commands that belong there: add, check, list. Tasks captured from WhatsApp land in the Idea Quarry, where they can be sorted later.

That is enough. The messenger should not become the place where you plan the week. It should be the place where a thought can leave your head before it evaporates.

The heavier work belongs back in Slate, where the weekly slate and Idea Quarry can be seen together.

Capture is not commitment

A captured task is not automatically a plan. This is the same reason Voice-Dump output lands in the Idea Quarry. Capture lowers the cost of remembering. It should not raise the cost of deciding.

When a WhatsApp message becomes a task, it enters the holding area first. Later, when you are actually planning, you can drag it into Tuesday, rewrite it, check it off if it was already done, or delete it because it was a passing worry pretending to be work.

This is the difference between a capture channel and a second to-do list. A second list becomes another place to reconcile. A capture channel feeds the one place where the week is made.

Thin is the feature

Thin tools are easy to underestimate because they do not produce many screenshots. Here, thinness is the point. A capture channel should be reliable, plain, and difficult to overuse for the wrong job.

Slate’s WhatsApp integration is not there to make conversation with your tasks. It is there so “add call Marco about Thursday deck” can become a row in the Idea Quarry before the next thought interrupts it.

That is all it needs to do.

The tradeoff is obvious: if you want a full conversational task assistant inside WhatsApp, Slate will feel too restrained. I am comfortable with that. The restraint is what keeps capture from becoming another inbox.