Built for every dance floor
From an intimate wedding to a sold-out club — let your crowd help decide.
Requests work differently at a wedding than in a club, and differently again in a bar or on a festival site. The difference is not technical — it is the same QR code everywhere — but in who scans it, how much comes in and how strictly you need to filter. At a wedding you want grandma’s song to get through; on a stage for a thousand people you mainly want to know which genre is landing.
So each situation below describes where it goes wrong in practice, what DJ Request changes about it and which settings work best. If you do not recognise your own night in any of them, the setup is usually closest to clubs or bars.
Weddings
Every guest hears their song
Read more →Clubs
Feel what the room wants
Read more →Bars & cafés
More atmosphere, more revenue
Read more →Company parties
Every department on one dancefloor
Read more →Festivals
A thousand people, one setlist
Read more →Which one fits you?
If you mostly play private events with a client — weddings, staff parties, anniversaries — agreeing things up front matters more than volume. You settle the no-go list, rule those out, and use the list to hear what the room wants without anyone walking up to your booth.
If you play where the crowd turns over all night — clubs, bars, festivals — the opposite is true. You get more requests than you could ever play, so the value sits in the pattern rather than any single track. Turning on paid requests filters that by itself: people who pay mean it.