updated · 2026-08-07
How to stop song request harassment in the booth without a \"no requests\" sign
Song request harassment in the booth is a refusal problem, not a request problem. Someone leaning over your controller at 1am is asking for a public yes in front of their friends, so any no you deliver face to face costs them status and invites escalation. The fix is a system that makes the refusal asynchronous and faceless: a policy published before doors, an intake point away from the rail, silence as the default answer, and an escalation path agreed with the venue in advance.
Why do the usual five polite excuses stop working after midnight?
The existing advice is not wrong. It is aimed at the wrong object.
Digital DJ Tips, in Phil Morse's guide last updated in 2022, is the most useful of the set: collect requests on paper, never play anything immediately, name-check the requester on the mic so a bad track is visibly their fault. Heavy Hits, by DJ Santero in 2020, is sharpest on tone — keep the moral high ground, stay calm, put deliberate hurdles between the crowd and the booth. The DJ Revolution calls the clipboard a "diversionary tool", exactly the right instinct. BPM Supreme reduces it to five lines, from "I'll play it soon – I promise!" to "Nah." DJ Music Geek suggests "I'll play it after the next three or four songs" and, failing that, pretending you cannot hear. DJ Gym frames it as boundaries and crowd reading.
Six guides, one shared assumption: the problem is finding the right sentence.
It isn't. On a quiet Thursday any of those sentences work. At 1am on a Saturday, with someone four hours into the night and three friends watching, none of them work — and not because they are badly phrased.
Is the problem the request, or the refusal?
The request is trivial. Someone wants to hear a track; you have thirty crates of reasons why it does not go here. That part is not hard.
The refusal is the problem — specifically that it happens in public, in real time, thirty centimetres from your controller, in front of the requester's group. They did not come to the booth to solve a music problem. They came to be seen getting a yes. What they lose when you say no is not the song. It is standing, in front of people whose opinion they care about, taken from them by someone holding a microphone.
That is why refusals escalate and requests do not. You cannot phrase your way out of a status loss.
So you know what a working solution has to do, whatever the tool. Make the refusal asynchronous — the answer does not arrive in the same moment as the ask — and faceless — it does not visibly come from you. Price is one way there. Not the only one, and not always the best.
| Mechanism | Who delivers the "no" | How the requester learns | Escalation risk at the rail |
|---|---|---|---|
| Verbal refusal at the booth | You, in person | Instantly, in front of their group | High |
| "No requests" sign | The sign, pre-emptively | On arrival | Medium — anger redirects onto you |
| Notepad or clipboard | The notepad | Usually never | Low |
| Bar or door staff | Venue staff | Later, from a non-artist | Low |
| SMS or QR web form | The system | Silence, or an automated message | Low |
| Priced request | The price | Before they ask; the number filters | Low |
Does a "no requests" sign work?
The most common answer here, and the weakest.
First, it is a broadcast refusal: it says no to everyone in the room, including the people who were never going to ask, and pre-emptive refusal reads as contempt rather than policy. Second, it does not remove the confrontation, it schedules it — whoever was going to ask anyway now arrives already annoyed, with a grievance to open on. Third, and least discussed: the sign makes you the visible author of the rule, in front of the crowd and whoever runs the room.
That last point is not theoretical. Racket, a Minneapolis newsroom, documented what happened to DJ Ja'mon Kimbrough, who performs as Aries Firebomb, after three years of sets at The Saloon. Per Racket's reporting, patrons responded to declined requests by holding up phones flashing monkey emojis and making racist remarks about the music he played. He put up No Requests visuals. The owner demanded he take them down, threatening to come and do it himself, and later banned him. Kimbrough filed a racial discrimination charge over the venue's failure to act on the patron conduct and over the retaliation that followed; the Minnesota Department of Human Rights served charges on the operating company, AMPA Inc., on 19 February 2026. The owner, Chris Bock, denies the allegations, saying none of AMPA's staff witnessed, reported or heard of any racial discrimination and that the company has a zero-tolerance policy. Racket is the only outlet to have reported the case in detail, and the charge has not been tested.
The sign caused none of that. But it is what management could see, and what management moved against. A refusal you author personally, in public, is a refusal that can be held against you.
One sign format has a better record, precisely because it is not a prohibition. In 2024, Mixmag reported that DJ PressPlay put a mock price list up at Coda in Colchester: £250 for Sex on Fire, £500 for Wonderwall, £1,000 for Mr Brightside, plus a line item for insisting you know better than the DJ. He was explicit that it was tongue in cheek — "I'm going to pretend I'm going to charge you for it" — and Mixmag reported that the track had not been asked for since the list went up. A number is not a rejection. It is a condition, and people argue with conditions far less than with people.
What does a request system actually look like?
Five steps. Set it up once, run it every night.
- Publish the policy before doors. Requests open or closed, where they go, whether money is involved — on the venue's event post and on a card at the booth. Nobody loses face over a rule that was already public.
- Move the intake point off the rail. Clipboard at the far end of the booth, QR code on the wall, bar staff who take a track name. It has to be somewhere you are not: reaching it must not involve reaching you.
- Make silence the default answer. No reply means no. Say it once in the policy — "not everything gets played" — then never send a decline. An unanswered request has no moment of rejection to react to.
- Never answer inside the ask. If someone gets to you anyway: one short line, one gesture, back to the mixer. No reasons. Reasons are an invitation to negotiate.
- Agree the escalation path before the set. Who you signal, what the signal is, what they do. Settle it while the lights are still on.
What about when this is a safety issue rather than an annoyance?
For some DJs, and disproportionately for women, the person at the rail is not a nuisance. They are a risk, and the booth is the one place in the room you cannot leave.
The nightlife context is documented, if not specifically for DJs. Kira Button, Nicholas Taylor and Peter Miller surveyed 232 nightlife patrons in Geelong, Australia between December 2022 and February 2023; writing up the results in The Conversation, they report that half the women and almost one in three men had experienced some form of sexual harm on a night out in the previous three months, unsolicited sexual comments, leering and groping being the most common. Only 35–38% told venue staff or police. They also found that as a venue's lighting rating rose by one unit, the odds of experiencing sexual harm fell by 27%.
That study covers patrons, not performers, and should not be stretched. What transfers is the structure: a dark, loud, alcohol-heavy room where reporting is rare, and a DJ standing in one spot for four hours.
So step five is not admin. For some DJs it is the whole point, and it belongs in the rider next to the technical spec. And an intake system that logs requests gives you what a verbal exchange never does: a timestamped record of what was asked, and by whom.
What do the request tools do differently?
They differ mainly on one axis: what the requester has to give up.
| Approach | What the guest does | Money | Best fit |
|---|---|---|---|
| App-based collector — e.g. RequestBox | Installs an app, joins a "box", votes on others' requests | No payment feature advertised | Weddings and private events, when you just want ideas |
| Subscription SMS/QR — e.g. RequestNow | Scans a code or texts a number, no app | Tips optional; DJ pays a subscription, advertised from $7/month | Residencies where you also want a text list |
| Priced request with a card hold — e.g. REQ | Scans a code, picks a track and an amount, pays only if you accept | Requester pays on acceptance; platform commission | Busy bars and clubs where request volume is the problem |
REQ, the tool we build, sits in the third row. It is in beta, with very few real transactions so far.
The mechanics: the crowd scans a QR code and lands on a web page — nothing to install — picks a track via Spotify autocomplete and an amount, and goes through Stripe Checkout. The payment is an authorization with manual capture, so the card is held, not charged. You get a push notification and accept or decline from your phone. Accept, the hold is captured. Decline or let the timer run out, and the authorization is cancelled: no debit, no refund to wait for, no refund object created at all. You can also accept for free — play it and cancel the hold.
Commission is 20%, the DJ keeps 80%, Stripe's fees come out of our side. Funds hit your Stripe Connect balance at capture and reach your bank on Stripe's payout schedule — on our accounts that has meant roughly seven days for a brand-new account, then every two to three business days. The DJ app is iOS; Android is in preparation.
Where it does not fit: REQ has no Serato, rekordbox or Traktor integration, so nothing lands in your prepare list — you read the request and pull the track yourself. Want to collect ideas at a wedding with no money involved? RequestBox is closer. Want the requester's phone number for a mailing list? RequestNow advertises that; REQ does not do it.
The hold mechanism is proprietary to nobody. Stripe documents placing a hold on a payment method as a standard pattern, states that a card authorization for an online payment is generally held for around seven days, and treats cancelling before capture as releasing the hold. Any platform can build on it; plenty charge up front and refund instead. Ask which one you are getting: "you were refunded" and "you were never charged" are very different sentences to say to someone at 1am.
None of this replaces reading a room. It replaces being the person who has to say no out loud.
This article is not legal advice. It describes an ongoing discrimination charge that has not been ruled on, and it touches on contracts, venue responsibility and payment rules that vary by country. For your own situation, ask a lawyer or your union.
Frequently asked questions
Does a "no requests" sign actually work in a club?
Rarely, and it carries a cost. A sign is a pre-emptive refusal broadcast to everyone, including the people who were never going to ask, so it reads as contempt rather than policy. It also makes the DJ personally responsible for the rule in the eyes of both the crowd and the venue. In Minneapolis, DJ Ja'mon Kimbrough (Aries Firebomb) put up No Requests visuals at The Saloon after patrons responded to declined requests with racist abuse; according to Racket's reporting the venue's owner demanded the sign come down and later banned him, and Kimbrough filed a racial discrimination charge that the Minnesota Department of Human Rights served on the operating company in February 2026. The owner denies that any staff witnessed or reported racial discrimination. A sign that states a price rather than a prohibition at least avoids that framing: a number reads as a condition, not as a personal rejection.
What do you say to someone who will not take no for an answer in the DJ booth?
Stop negotiating and stop explaining. Every extra sentence is another turn in a conversation the other person wants to keep alive, and explanations invite counter-arguments. Point once at whatever intake system you use — a clipboard, a QR code, the bar staff — say one short line such as "it all goes through there", and return to the mixer. If the person stays at the rail after that, it is no longer a music conversation and it becomes the venue's job, not yours: signal security using whatever gesture you agreed with them before the set started.
Is it unprofessional for a DJ to charge for song requests?
No — it is now common practice, in both joking and literal forms. What would be unprofessional is charging without saying so. At Coda in Colchester, England, DJ PressPlay posted a mock price list in 2024 — £1,000 for Mr Brightside, £500 for Wonderwall, £250 for Sex on Fire — which he described as a polite notice rather than real fines; Mixmag reported that Mr Brightside had not been asked for since the list went up. Several request platforms make the charge real and optional. The professional standard is disclosure: the price must be visible before someone asks, and it must be clear whether paying guarantees a play or only guarantees the request reaches you.
Who is responsible for removing an aggressive person from the DJ booth?
In practice the venue handles it, not the DJ. A DJ is tied to a booth full of equipment and cannot walk away from a confrontation the way bar staff can, and removing someone from a room is the job of the people who run it. The practical step is to agree the escalation path before the set: who you signal, what the signal looks like from across a dark room, and what happens next. If you are a touring or freelance DJ, put it in the contract or rider alongside the technical spec, so it is settled with the promoter rather than improvised at 2am. Who is legally responsible depends on your country and on your contract — check it rather than assume.
Do paid song request apps charge the customer if the DJ says no?
Some do and some do not, and the difference shows up on the customer's bank statement. Platforms built on a Stripe authorization with manual capture place a hold on the card instead of taking the money: Stripe documents authorizing an amount without capturing it, and cancelling the payment before capture releases the hold, with no charge and no refund to process. Stripe states that a card authorization for an online payment is generally held for around seven days. Platforms that charge immediately and refund later create a real debit on the statement and a wait for the money to come back, which is a materially different experience even when the end balance is the same. Ask a platform which of the two it does before you put its QR code on the booth.
Sources
- 01No Requests: How a DJ's Sign Led Him to File Discrimination Charges Against the Saloon — Racket (Minneapolis)
- 02How To Handle Requests When DJing — Digital DJ Tips (Phil Morse, updated 2022)
- 03The Only 5 Responses a DJ Needs for Song Requests — BPM Supreme (2018)
- 04How to deal with requesters! — Heavy Hits (DJ Santero, 2020)
- 05How to Handle Requests as a DJ — DJ Music Geek
- 06Taking Song Requests: A DJ Guide — DJ Gym (2023)
- 07How To Manage Song Requests: 7 Real-World Tips & Strategies for DJs — The DJ Revolution (2025)
- 08DJ introduces fines for clubbers who ask for "over-requested" tracks — Mixmag Asia (2024)
- 09Half of women at nightclubs recently faced sexual comments, groping, or forced kissing – new study — The Conversation
- 10Place a hold on a payment method — Stripe Docs
- 11RequestBox — song request collection app
- 12RequestNow — song request platform for DJs and musicians