To prepare for a first meeting with a new customer, start from their request, in their own words. Before booking a meeting by email, a Muzau agent writes your team a note on who the person is and what they are looking for: without that note, nothing is booked and the meeting waits for you in "To approve". Once it has summarized the request, that summary goes into the meeting description and into "Good to know". The conversation itself, you lead.
A new customer has written, by email or on the site chat. They explained what they need, asked two questions, accepted a slot. A few days later, the person who is meeting them opens the calendar and reads "Meeting", followed by a name. They then have to reread the whole exchange, or start with "So, what brings you here?".
The customer has already told it all once. Making them repeat what they need shows them nobody read it. The meeting, the listening and the proposal stay with your team; it is putting down in writing who they are and what they are looking for that the agent takes on, at the moment it books the slot.
Before booking a meeting by email, the agent writes your team who the person is and what they are looking for. This is not just a guideline: without that note, Muzau refuses to book, and the meeting waits for you in "To approve". It checks that the note exists, not what it says. On the site chat, the slot does not wait for it: the visitor's first question stands in for it. The note stays internal and never goes to the customer.
Once the agent has summarized the request (on the chat, that is the visitor's first question), the summary is written into the meeting description, in Google Calendar or Outlook. A "Meeting" line also appears in "Good to know", with the customer's address and that same summary. Whoever receives the customer knows what it is about on opening the event, without rereading the exchange. With Slack or Microsoft Teams connected, the agent also alerts the team there. Without a summary, the calendar description only says "Meeting booked via Muzau".
The invitation the customer receives also carries a short summary of what they talked about, written for them to read. That summary is checked before sending, like the rest of the message. What the agent thinks of the person is not in it: that judgment stays in the internal note. Depending on your setting, the invitation also gives the address to come to, or a video link when the connected calendar books the meeting.
If the agent qualifies requests and keeps a file it can write to, your questions are asked by email before proposing a meeting, or on the chat once the slot is chosen (see when to ask your questions). The answers go on the customer's record, in their own words; what they did not say stays empty. When everything is in, you receive a card and an email: their answers to each of your questions, then who they are in a sentence or two, drawn from what they wrote.
With or without a tool, a first meeting is prepared from what the customer wrote, not from your presentation. The goal: know what they are looking for, what you are missing, and what you will propose at the end.
Open with their request, reworded: "You wrote to me that you were looking for…, is that still the case?" The meeting then starts from their need, not from your catalog. Two mistakes come up again and again: running through your presentation before listening, and leaving without a date for what comes next. For a customer you have already met, the preparation changes: see preparing a meeting with a customer you have already met.
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.