Marvin now remembers the people he works with. What somebody usually works on, what they asked him to do differently, what they took on and whether they finished it — carried from one conversation to the next instead of starting from nothing every morning. A thing he has seen once stays quiet; a thing he has seen repeatedly becomes something he can bring up.
A clear report on each team member, built entirely from counted facts: whether they answer, whether they finish what they take on, whether their own time estimates are realistic, what is open and overdue on their name, their support queue and the hours they logged. Where there is nothing to measure it says so rather than reporting a zero.
Marvin keeps a daily reading of what the whole workspace is doing, so he can talk about a direction of travel and not only about today's number.
On a quiet evening the daily report is not sent at all. It goes out when somebody has something you could act on that day — a blocker, nobody with work, silence, follow-through slipping — and stays quiet otherwise, so that receiving it always means something.
The daily report distinguishes a new problem from a continuing one — “newly blocked” reads very differently from “still blocked”, and whatever appeared this week is ranked above what was already known last week.
A daily report to the management team: one line per person — who is stuck, who has nothing to do, who is not answering, what is overdue on their name — ordered so that whoever needs attention first appears first, followed by how the workspace as a whole is moving. Set the time in Marvin's settings; naming nobody as management switches it off.
Marvin now brings what he remembers about you into the conversation itself, so he can pick up where you left off instead of asking the same opening question every morning. If you were on something yesterday he asks whether you are still on it, and carrying on takes one tap.
A blocker Marvin has already reported does not quietly go away. If somebody is still stuck on the same thing days later, management hears about it again and more firmly, and the person is told plainly that they are owed a decision rather than another reminder.
Marvin notices when a job keeps rolling over. From the third day on the same piece of work he stops asking whether it is done and asks whether something is holding it up — and if you say something is blocking you, he tells management so somebody can clear it instead of leaving it in a private chat.
Marvin learns how your own time estimates work out. If your jobs reliably take longer than you expect, he checks back later instead of chasing you early — and he waits until he has seen enough of them before assuming anything.
Appointments — three new panels on the dashboard. Up next lists the bookings that have not started yet with how long is left on each. Booking pressure shows one bar per day for the coming fortnight, marking the days that are closed and the open days nothing is booked on. Provider load this week compares each provider's booked hours against the hours they are actually open, so an overloaded and an idle provider are told apart at a glance.
Updates
Appointments — the dashboard has been rebuilt in the same look as the rest of the app: a floating title bar, glass panels and the platform type scale, and it reads correctly in dark mode.
Appointments — the bookings list on the dashboard can now be filtered by type, by date range and by status. It still opens on today; the filters are there to look further.
Appointments — the App now ships its full in-product documentation: what it is, how to install it, a step-by-step guide to every screen, best practices for services, hours, payments and calendar sync, the modules and Apps it connects to, and an honest comparison with the standalone booking tools.
Marvin’s Proactive settings are easier to read: the timings are grouped by what they actually control, and the things Marvin can watch for you are split into Work, Money, Support and Your installed Apps instead of one long list.
Marvin’s help articles now cover proactive leadership: what it is, what your team sees when Marvin checks in with them, how to switch it on, how to read the manager’s digest, and how to run it well.
Marvin’s daily report to managers reads far better: who he cannot reach on Telegram is now said once at the bottom instead of opening almost every line, so each person’s entry starts with their actual work.
Each person’s line in Marvin’s daily report now says what they finished, not only what is late. Somebody who closed thirty tasks against a large backlog was being reported as though they had done nothing at all.
The workspace summary in Marvin’s daily report now includes how many projects are past their deadline, and what the overdue invoices are actually worth — a count on its own does not tell you how much is at stake.
What Marvin remembers about a colleague is now carried into conversations more usefully: how they work and what they have recently taken on are kept apart, and the most recent work always comes through rather than being crowded out by long-standing habits.
Marvin’s Conversations page is now a proper table: searchable, sortable, exportable, and it reads as a list on a phone. It also no longer stops at the fifty most recent threads.
Marvin’s Proactive settings now tell you when the setup will not do what you expect — switched on with nobody chosen to lead, no management team for blockers to reach, people who have since disconnected Telegram, or a watch that is on but has nobody to warn. Each of these used to fail in silence.
Marvin will no longer start more than a set number of conversations with the same person in one day, however much his watches find. On a workspace with a large backlog he could previously send hundreds of messages a day to the same people. The limit is twelve by default and can be changed, or switched off, in the Proactive settings. Replies to a message you send him are never counted.
When you tell Marvin you are not sure what to work on, the list he offers now spans your projects instead of filling up with the first one. Someone with a large backlog in one project and a few tasks in another was never shown the second at all. Most urgent is still at the top.
The buttons under that list no longer cut task names off in the middle of a word.
Marvin now tells managers when a team member has nothing assigned to them at all, taken from the workspace itself. Previously he could only notice this by asking, so the person nobody had connected on Telegram was also the person nobody noticed had run dry. It is reported the day it starts, not every night afterwards.
Fix
Marvin’s daily report to managers could not be delivered at all for a larger team: Telegram rejects any message over 4096 characters, and the report grows by one line per person. Long messages are now sent in parts, split between people so nobody’s entry is cut in half.
Marvin’s rule against inventing figures, dates or names lived only inside the editable persona text, so a workspace that rewrote the persona to change his tone silently removed it. That rule is now applied on every conversation regardless of what the persona says.
The Conversations page and the connected Telegram groups list appeared as white blocks in dark mode.
Information, success and neutral notice boxes stayed pale in dark mode, so they appeared as bright blocks on a dark page — including the ordinary “everything is running” message on Marvin’s settings. They now match the rest of the dark theme.
Status labels on Marvin’s settings were white on yellow and white on light blue, which was hard to read in both light and dark mode.
Warning boxes were hard to read in dark mode across the whole app: the panel was darkened but the text was left the colour it had on a pale background. They now use the app’s warning amber.
When somebody told Marvin their work was blocked, or that they had nothing to do, he replied that he had passed it to management — even when no management team had been set up, or nobody on it had accepted his messages, so the report reached no one. He now says plainly that there is nobody to escalate to and asks the person to raise it themselves.
Marvin could send two messages about the same support ticket in one round, because two of his watches found it from different angles. One record now gets one message.
Marvin’s alerts about a record with no client attached ended with an empty pair of brackets — “Order #1 has been in Processing for 636 days ().”
Marvin’s notes about a team member did not record where they came from, so every remembered detail looked the same regardless of whether he learned it in a conversation or worked it out himself.
Appointments — the dashboard's bookings list was missing its Payment column, which left the table one column short of the data it was given.
Appointments — the start and end time under each booking date was unreadable in dark mode.
