For a reproducible tool problem, a correction to a lesson or a suggestion about a resource, email contact@musicsheetmaker.com. This page opens your own email application; it does not submit a form or automatically attach a score. You decide what to include and send. A clear, small report is more useful than a large collection of unexplained files.
Try the relevant help before writing
The Help page covers local saving, project files, printing, sound and common format problems. It may explain a limitation or setting without requiring a report. Save an editable backup before testing a reload or another browser.
If the behaviour is expected but does not meet your needs, describe it as a feature suggestion. If a control or result differs from what the page promises, describe it as a problem. This distinction helps explain the change you are asking for.
Describe the steps and the result
Name the page and give a short sequence that someone else can repeat. For the main editor, mention relevant clef, meter and note values. For the MIDI converter, include the selected track and rhythm grid. For the MusicXML viewer, say which file type and source export were used.
Explain what you expected and what happened instead. Include the browser, device type and any visible error message. For a print problem, also give paper size, orientation and scale. You do not need to include unrelated personal information to make these details useful.
Share only a small original example
When an example is necessary, prefer a few original notes or a short file you are allowed to share. Remove names, private lyrics and other sensitive details. Do not send passwords, payment information or a complete private collection.
Read the privacy policy before deciding what to send. Files opened in the tools are not automatically attached to an email. You choose attachments yourself in your email application and should keep your own copy of any project used to demonstrate the issue.
Point to the exact lesson or resource
For a notation or answer-key correction, identify the page, section, row or exercise and explain the proposed correction. A concrete example is more useful than a general statement that a page is confusing. The editorial policy explains how corrections and sources are approached.
For a rights-related concern, follow the information requested in the copyright policy. Keep that report separate from a general tool suggestion so that the material and concern can be identified clearly.
Explain the musical task behind a suggestion
When suggesting a feature, say what you are trying to create, practise or print. Check the tool collection for an existing workflow and the printable library for a suitable starting page. Explain the missing step rather than only naming a button you would like.
The current editor is deliberately a single-melody workspace. A suggestion can still be useful when it falls outside that scope, but it does not mean the feature is available or scheduled. Avoid sending repeated copies of the same report while continuing your own work from a backup.
Review the message in your email application
Use a specific subject such as “Print clipping on Letter paper” or “Note answer in bass-clef worksheet”. Check the recipient and any attachment before you send. If no email application opens, copy the displayed address into the email service you normally use.
Opening the email link is not confirmation that a message was sent. Check your email application’s own sending status. Keep the report concise and retain the original project or resource so that you can refer to the same example later.