Kanban board · reads task
Task board
To-dos by status (todo / doing / done).
Cards in columns, one column per stage.
To do
Rewrite the welcome email
Doing
Chase Maison Lauret invoice
Photograph the new range
Done
Renew the domain
What it does
Behaviours, not fields. Choosing between two modules is choosing between these.
The shape of the board tells you where work is stuck, which a list of tasks cannot.
The agent moves a card when a conversation says it moved — usually before anyone would update it by hand.
Columns are yours, so the board matches how the work actually flows.
How it works
- 1
A task is created from a conversation and placed in the first column.
- 2
The agent moves a card when somebody says the work moved, which is usually before anyone would update it.
- 3
The count per column is what makes the board diagnostic rather than decorative.
- 4
A card sitting still is visible by age.
Best for
Anything that moves through stages: leads, orders, applications.
Not the right choice for
Data with no natural stages — you get one very long column.
What a row holds
Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.
| Field | Type | Filled from |
|---|---|---|
| Taskrequired | text | Anything somebody says they will do, captured in their words. |
| Columnrequired | choice | The state it is in. The columns are yours; three or four is usual. |
| Assignee | text | Who has it. Matched against Contacts or Team where those exist. |
What it does not do
A module chosen for something it cannot do costs more than one that was never offered.
- No swimlanes or sub-tasks. A card is one thing.
- No work-in-progress limits, so nothing stops six cards piling into one column.
- No due dates — that is a to-do list or a Gantt chart depending on the horizon.
- Column order is the order they first appeared unless set explicitly.
Before it works
What you have to provide, if anything.
- Nothing. The columns can be invented as the work reveals them.
- Pair with Sprints if the useful question is whether the work fits a window.
In practice
A four-person team tracking who is on what.
“I have started chasing the Lauret invoice.”
What the agent built
The card moved from To do to Doing without anyone opening the board.
What changed
Two cards sat in Doing for nine days. Making that visible was the whole value; both were blocked on the same missing answer.
Better with
These do a different job on the same data. An agent can have all of them.
The work is a sequence of small independent things and nobody needs to know what stage each is at.
The team works in fixed iterations and needs to see what was committed against what actually landed.
Items move through stages you invented, and no purpose-built module matches those stages.
Who uses this page
Property manager
Takes tenant issues, sorts the urgent from the routine, and keeps every unit’s history.
SaaS support team
Answers from your real documentation, and escalates the rest with context attached.
IT services provider
Triages what is actually urgent, and gathers the detail before a human looks.
Freelance developer
Filters the enquiries worth your time and scopes them before the first call.
Questions
What data does the Task board page use?
It reads task records the agent has collected. To-dos by status (todo / doing / done). Nothing has to be imported first — the page appears once there is something to show.
Do I have to build or configure it?
No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.
When is a kanban board the wrong choice?
Data with no natural stages — you get one very long column. It is best for: anything that moves through stages: leads, orders, applications.
Does it stay up to date?
Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.
More in Planning & time
Fri 12 Sep — Autumn tasting
Events
Everything the agent schedules — dates, place, attendees.
4 Sep — Tasting — Maison Lauret
Calendar
Month/week view across all dated nodes.
07:30
Load in, unlock the hall
45m
08:15
Floor plan and chairs
1h 30m
09:45
Sound check
30m
10:30
Doors
—
Planning / schedule
A run-of-show / agenda timeline.
Gantt chart
Tasks & phases with dependencies and durations.
Ask for it in a sentence
You do not configure this page. You tell your agent what you need and it builds it from what it has already collected.
Build your agent free