There's a little card on every table: Scan to request a song. Twenty minutes into the set, sixty people have. The requests are stacking up on your phone, three of them would empty the floor in a minute flat, and someone near the front is already waving because they don't see theirs come up. A QR code just turned the entire room into requesters in about ten minutes. Whether that's the best or worst thing to happen to your show comes down entirely to how you set it up.
The short version
If you're standing up a QR request setup before your next gig:
- The code collects requests. It doesn't decide anything. What plays, and when, stays yours from the first song to the last.
- Put it where phones already are — table tents, the bar, the screen, the stage lip — and say the one line out loud: "Scan, request, I'll work in what fits."
- Let requests land somewhere private and pull from them on your timing. Don't answer every ping in real time; that's how the booth becomes a bottleneck.
- The requests you skip are worth as much as the ones you play. Together they're the clearest read on the room you'll get all night.
The rest is how to make each of those true.
Why QR code song requests for live shows beat paper and shouting
The old way of taking requests has two settings: a stack of napkin scraps you'll never sort, or people leaning over the monitors mid-song to yell a title you can't hear. Both put the transaction right in your face at the exact moment you're supposed to be reading the crowd and working the mix. You end up negotiating song choices in real time, in public, with whoever's loudest — and the loudest three people are rarely your best read on the night.
A QR code fixes the intake problem cleanly. Fans point a phone camera at the code, a page opens in the browser — no app, no download, no account — and they've sent a request in about ten seconds. Nobody has to shout, nobody has to fight to the front, and everybody can reach you at once instead of only the people brave enough to approach the booth.
That last part is also the catch. When everyone can reach you, volume becomes the new problem. Sixty silent requests are easier to ignore than one drunk guy, but they're still sixty decisions. So the setup that matters isn't the code itself — it's what happens after the scan.
How to set up a QR code request system in six steps
You can have this running before your next show. Do it in this order.
- Lock your requestable catalog first. Decide what people are even allowed to ask for before the doors open. A closed list means no off-brand curveballs, no songs you don't have, no surprises you have to shut down live.
- Generate one code per show. A fresh code per night keeps requests scoped to the room in front of you and gives you a clean recap afterward instead of a rolling blur.
- Place the code where phones already are. More on placement below — the wrong spot is the single most common reason a good setup gets no scans.
- Script the announcement and say it twice. One clear sentence from the mic — early, and again after the room fills — does more for scan rate than any sign. Tell them it takes ten seconds and that you'll work in what fits.
- Route requests to a private queue, not your text messages. Requests should land somewhere you review on your own timing, not buzz your phone like an incoming call you have to answer.
- Test it cold before the room does. Scan your own code from a phone that's never seen it, submit a request, watch it land. Do this at soundcheck, not at 11pm with a full floor.
Where to put the QR code (and why it matters)
Placement decides whether you get sixty scans or six. Match the code to where attention and phones already are.
| Where | Why it works | Watch-out |
|---|---|---|
| Table tents / bar top | Phones are already down there between drinks | Print big; a tiny code in low light won't scan |
| The screen or projector | Everyone's already looking at it; refresh it between songs | Needs a clear line of sight from the floor |
| Stage lip / DJ booth front | Catches the people who'd otherwise come up to ask | Keep it lit; stage light washes codes out |
| Bathroom / hallway signage | The unhurried moment where people actually pull out a phone | Easy to forget; add it to your load-in checklist |
| Ticket confirmation / story link | Reaches fans before they even arrive | Only works if the code is show-specific |
The part that keeps it from turning on you
Collecting requests is the easy half. The hard half is that a request is information, not an instruction — and a QR setup that dumps all that information straight onto a screen, or straight into a live tally the room can watch, hands your set to whoever's most motivated to spam the submit button. You don't want the floor watching a scoreboard. You want the read without the pressure.
This is the model CueTonight is built around. The QR code does the collecting: fans scan and request from the list you approved in advance, so nothing off-catalog ever reaches you. Every request lands in a private queue — nothing goes public, nothing hits the screen, until you clear it. You approve what fits, hold what doesn't, and there's no running count for the crowd to rally around. You get the whole room's demand and still play what works when it works.
The speed is real, and it's the thing paper never gave you. At a Slick Rick show at The House of Independents in New Jersey, the room sent 588 requests from 412 different people inside a twelve-minute window — the team surfaced some and held others back for pacing, all before anything went public. You cannot field that by ear. But you can read it, and reading it beats guessing.
The bonus nobody sets this up expecting: the requests you don't play are as useful as the ones you do. After the night you can see total requests, how many unique people sent them, and demand for songs that never made the set. For a one-off that's a nice extra. For a weekly night it's the whole edge — you stop guessing what your room wants and start working from a map.
FAQ
Do fans need an app to request a song by QR code?
No — and that's the point. A QR code opens a page in the phone's normal browser. Fans scan with the built-in camera, land on a request page, and submit in about ten seconds. No download, no account, no login. The ten-second, no-app path is exactly why scan rates beat every "text this number" or "find us in the app store" alternative.
How do you handle bad song requests that come in by QR?
You don't have to handle them live at all, which is the whole advantage. If requests land in a queue you review on your own timing, a floor-killer is just a request you never approve — no argument, no awkward "maybe later," no one watching you say no. Lock your catalog in advance and most bad requests never reach you in the first place.
Where should you put the QR code at a live show?
Wherever phones already are: table tents, the bar top, the screen, and the front of the booth or stage. Print it large, keep it lit, and back it with one spoken line from the mic. A code nobody can find or scan in low light is the most common reason a setup gets ignored.
Do QR code song requests actually work, or is it a gimmick?
They work when the code only handles intake and you keep every decision. The failure mode is wiring the code to a live public screen and letting volume run the night — that's a gimmick. Used as a private intake channel you review, it turns the loudest-three-people problem into a full read of the room. One New Jersey show pulled 588 requests in twelve minutes that way.
Can people request songs by text instead of scanning?
Text-based intake exists where it's enabled, but lead with QR as the main path. A scan is faster than typing to a shortcode, works without anyone handing over a phone number, and avoids the carrier and consent overhead that comes with two-way texting. Offer text as a backup for the room with no signal, not the headline.
The bottom line
A QR code is the best intake tool live shows have had in years, and it's dangerous for exactly the same reason: it lets the whole room reach you at once. The setup that works keeps those two things apart — let the code collect everything, and keep every call about what plays yours.
If you want to see that run end to end — QR intake, a private queue, you approving what hits the screen — see how CueTonight runs a request moment for a live night.