How to respond to a curator rejection
Thank them once, ask one short question about fit, and stop. Do not argue, do not send another track in the same thread, and do not ask them to reconsider. Record the reason, keep the contact, and pitch the next release with that context. A graceful no is how a future yes starts.
Updated 2026-10-26. Written by the team that operates this platform; no rankings, placements or listener numbers are promised anywhere on this page.
Why the reply matters more than the no
Curators talk to each other, and many of them run several playlists or move between outlets. The artist who answers a no with a polite question is memorable; the one who argues or sends three more tracks is remembered as a problem. You are not trying to overturn this decision — you are trying to be the artist they think of when a slot opens.
The practical value is information. A curator who says "too slow for this list" or "we only take instrumentals" has told you something about your record and your targeting. Even a two-word rejection can be recorded and used, which turns a wasted send into a data point.
- Reply once, briefly, and thank them.
- Ask at most one question about fit or future timing.
- Do not resend the track or a different track in the same thread.
- Record the reason and the contact for the next release.
The reply, in two sentences
Something like: "Thanks for listening and for telling me — helpful to know it is a tempo fit rather than the record. Would it be useful if I sent the next single when it is out in spring?" That is the whole reply. It is short, it accepts the answer, and it asks a forward-looking question that is easy to answer with one word.
If they say "send the next one", record it as a warm contact and actually do it, with a first line referencing this conversation. If they say nothing, that is also an answer: keep the contact, do not follow up again on this release, and move on. The curator pitch template is what to use when you come back.
What not to write
Do not ask them to listen again, and do not explain why they are wrong about the record. Do not offer money, and do not imply that other curators have already added it — that is pressure, and it is usually untrue. Do not send a second track in the same thread as a "try this instead" unless they asked for it.
Also avoid the silent treatment followed by a re-pitch three weeks later as if the no never happened. That is the behaviour that gets an address filtered. If you genuinely believe the fit was misjudged, the honest route is a different release, not a different argument.
Turning a no into a list asset
Every no is a row with a reason and a date. Sort them into three groups: wrong genre, wrong timing, wrong format. Wrong genre means remove from the list. Wrong timing means keep and pitch the next release. Wrong format means fix the asset — an instrumental, a clean edit, a radio edit — before the next campaign.
Over two or three releases, those categories tell you more about your market than any analytics dashboard. They also keep your list small and honest, which is what protects deliverability and makes the next wave worth sending. The email-list hygiene guide explains the maintenance routine.
Published plans
These are the plans this platform publishes today, in US dollars per month. Every paid plan includes managed domain SMTP sending and email verification; the tiers differ in allowances.
| Plan | USD / month | Emails | Contacts | Managed mailboxes |
|---|---|---|---|---|
| Starter Outreach | $49 | 2,000 / month | 1,000 | 1 |
| Pro Industry | $99 | 10,000 / month | 10,000 | 3 |
| Artist Plus | $199 | 50,000 / month | 50,000 | 5 |
| Label | $399 | 100,000 / month | 100,000 | 7 |
| Agency | $699 | 250,000 / month | 250,000 | 10 |
| Enterprise | $1000 | 500,000 / month | 500,000 | 15 |
Allowances reset on the first day of each UTC month. Prices are read from this site's own plan data, not estimated. See the pricing page for the exact feature list per plan.
Worked example: three rejections, three answers
A curator writes: "Nice track, but too slow for this playlist." Reply: thanks, ask whether a faster remix would be worth sending in a few months, record "tempo / wrong timing". A second writes: "We only take instrumentals." Reply: thanks, confirm an instrumental exists, ask whether to send it now, record "format". A third never replies: record silence, no follow-up on this release.
Three contacts, three outcomes, no argument and no extra sends. Two of them are now warm for the next release with a specific fix attached: the remix and the instrumental. That is a better result than a defensive reply and a burned contact, and it took about two minutes.
- 1Answer within a day, with two sentences at most.
- 2Ask one forward-looking question, not a request to reconsider.
- 3Record the reason under wrong genre, timing or format.
- 4Fix what the reason points at before the next campaign.
- 5Pitch the next release with that context in the first line.
The numbers in this example are arithmetic on the plan allowances, not observed results.
Rejection reply checklist
The reply is short by design; check that it stays that way.
- The reply thanks them and accepts the decision.
- It contains at most one question.
- It does not ask them to listen again.
- It does not offer money or incentives.
- It does not send another track unprompted.
- The reason is recorded in the list.
- The contact is kept for the next release.
- No further follow-up is planned for this record.
What a good reply will not do
It will not reverse the decision. Curators decline for reasons that are often about their own programming, and a polite reply does not change that. It will not guarantee a future yes either; a warm contact is an opportunity, not a promise.
It will not fix a record that does not fit a playlist’s genre. If the pattern across twenty rejections is "wrong genre", the answer is a different list, not a better reply. And it will not work as a negotiation tactic — treating a no as the opening of a bargain is how artists acquire a reputation.
- No guaranteed reconsideration or future placement.
- No pressure, incentives or implied competition.
- No claim that a polite reply obliges any response.
Questions people ask
- Should I reply to a rejection email?
- Yes, once, briefly. Thank them and ask at most one forward-looking question. Most curators will not answer again, and that is fine — the point is to be remembered as easy to deal with.
- What if a curator says "not right now"?
- Ask whether you may send the next release, record the contact as warm, and do exactly that when the next record is out. Do not send another email in between; the "not now" is about timing, not about needing reminders.
- Should I offer to pay for a playlist add after a rejection?
- No. Offering money in response to an editorial no is inappropriate and often against the curator’s own rules. Paid promotion is a separate, disclosed arrangement, never a reply to a rejection.
- What if the rejection is rude?
- Do not respond in kind. Record the contact, remove them from future campaigns, and move on. A rude reply costs you the high ground and produces nothing.
Tools we build for this work
Spotify Monthly Listenersthis site
music promotion outreach platformDirect outreach to playlist curators, radio, press and industry contacts with managed sending.
LocalSMTP
LocalSMTPInbox-ready SMTP accounts with the domain, mailbox and DNS work handled for you.
Mail Pro
cold email campaignsCold email campaigns: sequences, senders, replies and reporting in one workspace.
AI Sales Agent
AI-written cold outreachAI-written cold email with campaign workspaces, pooled sending and reply handling.
Scrape.Email
verified B2B leadsVerified B2B lead discovery and email verification before you send.
United States Marketing
multi-channel marketing workspaceWhatsApp, SMS and social outreach in one marketing workspace.
Help Me Teach Me
AI teaching and guided task helpA patient AI teacher that shows you how to do a task, or does it with you.
How To Unblock Website
proxy and VPS hostingProxies and VPS access for websites and tools that block your region or network.
Software Programmer
Software ProgrammerCustom software built for a specific workflow, integration or internal tool.