A QR code works when guests can find it, scan it and understand what happens next. Build the sign and the operating process together.
Before printing anything, define what the QR code invites guests to do. A submission can be a request for consideration, not a promise of immediate play. Decide who reviews it, what makes a choice unsuitable and when requests will close. This policy shapes the instruction beside the code and gives the DJ a consistent answer when guests ask about timing.
Crowd Current keeps the decision with the DJ, who approves or rejects every request. A live queue gives guests visibility while the DJ continues to manage the room. Curated song lists can guide guests toward appropriate choices. Choose those settings before testing so the trial matches the experience you will actually provide.
Give the QR code strong contrast and clear space on every side. Do not place text, logos or decorative patterns across it. Print a test at final size rather than relying on a screen preview. Gloss, folds, low light and distance can all change scan performance. Test from several common phones in the venue.
Pair the code with a brief action line: “Scan to request a song.” Add one expectation line if needed: “Requests are reviewed by the DJ.” Avoid a paragraph of rules on the main sign. Put detailed guidance on the request page or in smaller supporting copy. The sign’s first job is helping a guest take the next action confidently.
Place signs where guests pause: entrance tables, bars, seating areas and other natural gathering points. A code placed only at the DJ booth still sends traffic directly to the workspace. For a wedding, coordinate with the couple before adding it to table materials; the wedding request guide covers reception-specific boundaries.
Position each code at a comfortable scanning height and keep it out of glare. Large venues may need multiple identical signs, but every sign should point to the same event. Remove codes from previous events and label printed sets carefully. A working code connected to the wrong event is harder to notice than one that does not scan at all.
Scan every physical sign, confirm the correct event and submit a test request. Check how the title appears, whether the curated list is right and whether the request reaches the operator view. Review the guest-facing queue, then approve and reject tests to understand each state. Finally, confirm the process for closing requests.
Repeat the test using cellular data if the venue’s guest Wi-Fi may be unreliable. Ask a staff member who did not build the setup to try it without coaching. Their hesitation will reveal unclear labels or placement. Keep a short fallback URL or staff-assisted route, and put any assisted request into the same queue.
Mention the code once when guests are ready to participate, then let the signs do their work. Review requests regularly rather than allowing a backlog to grow unseen. Use the live queue to communicate progress, but preserve the ability to choose the musical order that serves the room. Shoutouts and tipping can be offered when they suit the event.
Close requests before the final segment so remaining expectations are realistic. Crowd Current lets the DJ close requests for the night. For costs, Starter is $0 for up to three events with unlimited requests. Pro is $39.99 per month or $399 per year, and Pro and Organization have a 0% platform fee on tips and payments. Compare options on the pricing page.
Run one complete rehearsal with someone who did not configure the event. Ask that person to find the invitation, scan the code, understand the request policy, choose a song and submit it without coaching. Then follow the request on the operator side: review it, make a decision and confirm that the guest-facing queue communicates the result clearly.
Use the rehearsal to check responsibilities as well as screens. The operator should know who can answer guest questions, staff should know not to promise a play, and everyone should know the closing rule. Test from the actual guest area in event lighting, not only beside the booth. If any step needs a long explanation, simplify the sign or the policy. A ten-minute rehearsal exposes wrong event links, unclear wording and ownership gaps while there is still time to correct them.
Place them where guests pause, such as entrance tables, bars and seating areas, rather than making the DJ booth the only scanning point.
No. Guests scan a QR code and use the request experience without downloading an app.
No. State that requests are reviewed. The DJ approves or rejects every request and manages timing for the room.
Scan every physical sign, confirm the correct event, submit a test, check the operator view and guest queue, and test approval, rejection and closing.
Create an event, share a QR code and manage requests with a clear process.
Create Your Account