List · reads reminder
Reminders
Time-based nudges.
One row per item, the plainest possible view.
- Follow up on the Atelier Nord quoteIn 3 days
- Insurance renewal1 Nov
- Ask Camille about the venue depositTomorrow 09:00
- Reorder packagingWhen stock < 50
What it does
Behaviours, not fields. Choosing between two modules is choosing between these.
A reminder has a trigger and a recipient — it is raised unprompted rather than waiting to be found.
Fires on a condition as well as a date, which a calendar cannot express.
The failure mode it addresses is forgetting at the right moment, not forgetting entirely.
How it works
- 1
A reminder is created from a sentence, with whatever trigger was stated.
- 2
Date triggers fire on the day; condition triggers are checked whenever the underlying module changes.
- 3
The agent raises it in conversation rather than sending a notification nobody reads.
- 4
A fired reminder is closed unless it was recurring.
Best for
Reading and scanning. It is the right default more often than it looks.
Not the right choice for
Comparing many fields at once — use a table.
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 |
|---|---|---|
| Remindrequired | text | The thing to bring up later: chase this, renew that, ask about the other. |
| Whenrequired | text | A date, a relative time, or a condition. All three are valid triggers. |
| Whorequired | text | Who it is raised with. Usually the owner. |
What it does not do
A module chosen for something it cannot do costs more than one that was never offered.
- Conditions are limited to what another module already tracks — stock below a level, an invoice past due.
- No escalation. If the reminder is ignored, nothing happens next.
- No external delivery: no email, no SMS, no push.
- Recurring reminders repeat on a simple interval; there is no calendar logic behind them.
Before it works
What you have to provide, if anything.
- Nothing for date reminders.
- A condition reminder needs the module it watches to exist first.
In practice
A business that had missed an insurance renewal the previous year.
“Remind me about the insurance before November.”
What the agent built
A dated reminder against the renewal, plus a stock-level one set the same week.
What changed
The renewal was handled a fortnight early. The stock reminder fired on a condition three months later and prevented a stockout.
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 business runs on appointments or dated commitments and someone needs to see the shape of the month rather than a list.
Repetitive reactions are being done by hand, and the trigger is something the system already knows about.
Who uses this page
Insurance broker
Collects what a quote actually needs, without a twenty-minute call.
Clinic or practice
Answers the administrative questions, so the phone is free for the clinical ones.
Accountancy firm
Answers the deadline and paperwork questions, and chases what you are still missing.
Garage or car dealership
Answers what a job costs and when you can fit it in, without leaving the ramp.
Questions
What data does the Reminders page use?
It reads reminder records the agent has collected. Time-based nudges. 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 list the wrong choice?
Comparing many fields at once — use a table. It is best for: reading and scanning. It is the right default more often than it looks.
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