To know where each customer request stands without asking your team, open the "Management" page in Muzau. It tells you how many things are waiting for you, puts whatever is blocking a customer first and shows what the agents will do over the next 14 days. Every request sent to a Muzau agent opens a tracking row, where the agent dates its last action. Anything that needs your approval waits for you in "To approve".
One request comes in by email, another through the website chat, a third during a meeting. Each lives in the inbox or the memory of whoever received it. To know where they stand, all that is left is to ask: a message to the team, a round table on Monday, and answers that depend on everyone's memory.
The tracking spreadsheet was meant to prevent that, but it gets filled in after the fact: it tells you what was done on the day it was updated, not what is happening. The status of a request should be written at the moment the action takes place.
When a Muzau agent keeps a tracking file and you have given it access to the records, every request sent to it opens a row: two requests from the same customer make two rows. A quote sent with the agent's address in copy also opens a record (date, customer, subject), without sending anything to anyone. Each row shows the agent's last action, dated: "message 2 sent", "follow-ups stopped". When a colleague has written to the customer from their connected inbox, the row says who and when. A "signed" or "paid" value in your status column moves the row to "Settled / accepted", and nothing there is followed up any more (see how follow-up stops once a quote is signed).
Muzau's "Management" page tells you how many things are waiting for you and shows the three most urgent. First what is blocking a customer, such as an email nobody is picking up. Then what a customer is waiting for, and finally internal housekeeping. The oldest comes first. Whatever is waiting for your approval is gathered in "To approve", with the reason each message comes back to you. To be notified rather than go and look, see alerts in Slack or Microsoft Teams.
At the bottom of the "Management" page, the agents' schedule covers the next 14 days, one card per action and per day: follow-ups, announcements, meetings booked. You can read a follow-up before it goes out, along with the row that triggered it, and you can edit its text. When the text cannot be written in advance, the screen says so. Dragging a card to another day moves the follow-up; "Cancel sending" stops follow-up for that person, or for a single step.
You can ask an agent "where are you on this?" or "why didn't you reply?". It answers with what Muzau has recorded: its latest actions, the latest people to arrive in its files, what became of its latest emails. When nothing explains a silence, it says it does not know rather than inventing a cause. To see what it wrote to a customer, the "History" on the agent's page shows what it did and when, and follow-ups sent from your inbox appear in your Sent folder.
With or without a tool, the status of requests reads itself when each row says two things more than its status: what happened last, with its date, and who is waiting for whom. For the rules of a tracking table that holds up, see how to track customers in a small business. Then read it in three passes.
Four signs show that a request is stuck, without having to ask:
The team meeting is then for settling those rows, who picks up, who closes, who calls back, rather than reciting statuses. Avoid the "comments" column where the history piles up: nobody rereads it.
Autonomous does not mean unchecked. You set the level of autonomy of every agent, its limits cannot be crossed, everything it does is recorded in a plain-language log, and one gesture stops it all.
For the tasks you don't have time for. You give the address of your website, then describe the work in your own words. Nothing to install.