Messages here are read by a person, not a bot. This page explains which enquiry type to choose, what to include so the team can act on your first message, and what to expect once you send it.
Choose the enquiry type first
The enquiry type decides who reads your message, so it is worth a moment's thought. Pick the category that matches what you need rather than the one closest to hand. A question about an existing release, a question about rights or a takedown, a press or partnership approach, and a general question about how the platform works all go to different places. If nothing fits neatly, choose the closest option and say plainly in the first line what you actually need. A clear opening sentence is more useful than a perfectly chosen category.
What to include so a human can act
Give the team enough to work with in one message. Include your artist name exactly as it appears on your releases, the release or track in question, and a link to it wherever it is live. Say what outcome you want: a correction, an explanation, a removal, an introduction. If you are writing about something that went wrong, add what you expected to happen and what happened instead, with dates. Screenshots help. Sending one complete message is faster than a short one followed by four rounds of clarifying questions.
What to expect after you send
Every message is reviewed by a person, so response times vary with volume and with how complex your question is. A simple factual question is usually quicker than one that needs records checked or a third party involved. You will not get an instant automated answer, and there is no queue position to watch. If your situation changes while you are waiting, reply on the same thread rather than starting a new one, so the whole history stays in one place for whoever picks it up.
What the team can and cannot answer
The team can explain how the platform works, help with account and release questions, look into delivery or reporting issues, and point you to the right process. It cannot give you legal advice, act as your representative in a dispute with a third party, promise editorial placement or coverage on any streaming service, or predict what a platform will do with your release. Availability on any given service is subject to that platform's own rules and eligibility. Where something is outside what the team can decide, you will be told plainly.
Rights and takedown enquiries
Rights questions need more detail than most messages. If you believe material has been used without permission, or you need something removed, say clearly what the material is, where it is appearing, what your connection to it is, and what right you are asserting. Include links and any documentation you can share. These enquiries are handled by a person and can take longer than general questions, because they usually involve checking records and sometimes contacting other parties. Sending complete information at the start avoids several rounds of delay.
Applying for distribution is a separate route
Access to Mazufa is invite-only, and applications do not go through the contact form. If you want to be considered for distribution, submit the public application at /apply/, which enters a human-review queue. Submitting an application does not create an account and does not guarantee acceptance. Sending your music to the contact address instead will not move you into that queue any faster, and may simply be redirected. Use the contact channel for questions about the process, and the application form for the process itself.
What should I include in my first message?
Your artist name as it appears on your releases, the specific release or track involved, links to it, and a clear statement of what you need. If something went wrong, add what you expected, what happened instead, and the dates. Screenshots are welcome. One complete message resolves things faster than a brief one followed by several rounds of clarification.