Send Feedback to the Muse Team Through Your Muse

When something you need is missing, you can ask your muse to write and send the feedback to the team that builds it, as a private note, without your personal details attached.

What it does

Every service has a gap that only shows up in real use. When the gap is a missing connection or feature, you do not have to hunt for a feedback form. You can ask the muse to send the request itself. The muse drafts the feedback, sends it as a private note to the team, and leaves your own context out of it: no account details, no message history, just the request and why it mattered. The same route works for a feature you wish existed or a step that keeps breaking in the same place. You describe the problem in plain words, read the draft, and approve it before anything is sent.

How to use it

1. Describe the gap in one or two sentences, the way you would say it out loud: what you tried to do, and what was not there or did not work.
2. Ask the muse to draft the feedback as a private note to the team, and to leave out your personal details, account information, and message history.
3. Read the draft before it goes. Check that it asks for the thing you actually want, in the words you would use.
4. Approve the send, or correct the draft and approve the corrected version.
5. Keep your own note of what you sent and when, so a second message about the same gap builds on the first instead of repeating it.

What you need

• A muse account
• A clear description of the missing feature, missing connection, or repeated problem

What to watch for

• Sending feedback is a request, not a promise. The team may build the thing, build something else, or not build it, and the muse cannot tell you which.
• Read the draft for stray details. A feedback note should carry the request and the reason, not your schedule, your contacts, or anything from your connected accounts.
• Be specific about the job you were trying to do. "Add this email service" lands better with the example of the work it blocked than as a bare feature name.
• One clear note per gap works better than a long list in a single message. Separate gaps deserve separate notes, each with its own approval.