Why requests happen at all
Someone making a request usually wants one of three things: to be seen, to hold on to a moment („that was our song“), or to change the mood, because they do not like what is playing. Only the third is a statement about your music at all — and even there the named track is more of an example than a demand.
That is the practical consequence: you are not answering the track, you are answering the need. A redirected request feels almost as good to the guest as a granted one — as long as they notice you listened. A declined one without a reason feels worse than no conversation at all.
The four kinds of request
They look identical from the outside and need completely different answers. Sorting them takes two seconds.
| Kind of request | What gets said | What is meant — and what helps |
|---|---|---|
| Being seen | „Play something by …“ — often without a specific track | Needs no song, needs a reaction. Eye contact and one sentence is usually plenty — the request often disappears on its own afterwards. |
| The moment | „That is our song“ — usually with a story attached | The strongest request there is, and the one where declining costs most. If the tempo allows it at all: play it, with a time. |
| The mood change | „Could you play something faster/harder?“ | The only genuine statement about your music — and worth taking seriously. Look at the floor before you answer: sometimes they are right. |
| The foreign body | A track two genres and 40 BPM away | Here declining is correct, but with a craft reason rather than a verdict on taste. Redirecting to something in the same mood works surprisingly often. |
The one rule: never the phone at the booth
The moment someone else’s device is plugged into your mixer you have handed over control of volume, key and timing — and of the night. It is also the worst route technically: unknown level, no analysis, no beat grid, often a streaming version of a different length.
The sentence for it can be friendly and final: „Nothing external goes into the booth, but tell me the title — I will see if I have it.“ That keeps the door open and the system protected.
Answering a request in 5 steps
Ten seconds, always the same sequence. Practise it once and you will not have to think in the moment.
Listen and take the headphone off
One cup down, eye contact. Taking a request with the headphones half on and your eyes on the screen is already a refusal before you have said anything.
Sort the request, do not judge it
Being seen, holding a moment, changing the mood, or just a favourite song? Two seconds is enough — and the sorting decides which of the three answers fits.
Check whether it fits the tempo and the hour
Not whether you like the track, but whether it fits the BPM range you are currently in and the phase of the night. A track that meets both almost always works — even when it is not your taste.
Answer, and answer concretely
Take it with a time („in twenty minutes“), redirect it with an offer („I have something in that direction“) or decline it with a reason („it would empty the floor“). A „we will see“ is not an answer — it is a postponement, and the guest will come back.
If you say yes: actually play it — and say so
A request promised and not played is worse than one declined. If it does not work out, say so in passing. If you do play it, a nod in that direction is enough — that is what the request was for.
Mistakes that cost you the night
Taking the phone
Unknown level, no analysis, no beat grid — and you have handed over control of the night. Note the title, not the device.
Saying „we will see“
Not an answer, just a postponement. The guest returns in ten minutes and then it is a second conversation instead of a closed one.
Promising and not playing
Worse than any refusal. Forgetting a request gifts the guest an hour of waiting and a disappointment at the end of it.
Justifying it with taste
„Not my thing“ gets taken personally by everyone. „That does not fit the tempo tonight“ is the same answer without the insult.
Slotting it in instantly, mid-transition
A request is not an emergency. Searching during one loses the running mix — and then the whole floor hears the request.
Preparation that defuses requests
Most awkward moments do not happen at the booth but beforehand — because something was not settled.
Settled with the host how much request is allowed
At private parties the single most important question — and the only one that cannot be answered at the booth.
Ten fallback tracks ready
Broadly danceable, at your current tempo, in their own list. They are the answer to „something familiar“.
Genuinely knowing your own library
Only someone who has an alternative in mind within two seconds can redirect. That is preparation, not talent.
A designated place for requests
Slips, a box, one person — anything that is not the booth. It removes pressure before it builds.
Said the refusal sentence out loud once
Having it ready means not inventing it in the moment. That is exactly when the unfriendly versions come out.
One exception that genuinely is one: at private parties the agreement with the host outranks your taste. Someone playing a wedding is booked so that particular people hear particular songs — there the request list is not an intrusion into your set, it IS the job. The craft lies in sequencing it so it still forms an arc.
Frequently asked questions
Do I have to play requests at all?
In a club: no, you are booked for the selection. At a private party: usually yes, there the selection is the job. The difference is not politeness but the booking — and settling it beforehand means not arguing about it at the booth.
How do I decline without being rude?
With a reason that does not sound like a verdict on taste. „That does not fit the tempo tonight“ or „it would empty the floor“ is something entirely different from „not my thing“. The first is craft, the second is a brush-off — and only the second gets taken personally.
What if the same person comes back five times?
Sort it the first time, repeat the answer the second, and get friendly but final on the third: „I told you why earlier — that stands.“ Renegotiating on every attempt invites a sixth. And if it turns, it stops being your problem and becomes security’s.
Request slips and lists — worth it?
At parties yes, in a club rarely. A request box collects everything in one place, takes the pressure off the booth and gives you time to sort instead of react. The only thing that matters is that you genuinely look in it — a box that is an alibi gets noticed.
What if I simply do not have the track?
Say so openly and redirect — „do not have it, but I have X, which goes in the same direction“. Do not: quickly download or stream something. An unanalysed track at an unknown level in the middle of a set is not worth the risk, and the guest will not notice the difference anyway.
And if the request is bad but the floor wants it?
Then it is not bad. The dancefloor is the authority, not your taste — and reversing that means playing for yourself instead of the room. The honest limit runs elsewhere: a track that wrecks the energy for the next twenty minutes stays out, no matter who wants it.
Practise first
Know your library, say no less often
Only someone with alternatives in mind can redirect. That comes from preparing your own library — not from improvising at the booth.
Start for free