Invite guests into the music without handing over the reception. This guide helps couples and DJs collect useful suggestions, set boundaries and keep the dance floor moving.
Start by agreeing on the role of requests. They can be ideas for the DJ, not promises that every song will play. That distinction protects the couple’s priorities and gives the DJ room to read the dance floor. Put the rule in plain language wherever guests submit: requests are reviewed, timing matters, and the final music decision remains with the DJ.
Couples should give the DJ a short must-play list, a do-not-play list and any important moments that already have assigned songs. Add notes about clean versions, family sensitivities and genres that fit or clash with the celebration. These guardrails are more useful than an enormous playlist. They describe the desired experience while leaving enough flexibility for a professional to connect one part of the night to the next.
Pre-event suggestions can reveal family favourites and songs tied to the couple’s history. On-site requests capture what the room wants in the moment. Treat them as two different inputs. Review early ideas with the couple before the day, then let the DJ evaluate live submissions against the agreed brief.
Crowd Current lets guests scan a QR code without downloading an app. A curated song list can focus choices, the DJ approves or rejects every request, and a live queue gives guests a view of progress. That combination offers participation without removing control. It also keeps requests away from scraps of paper and repeated conversations at the booth.
Use the QR code where guests naturally look: on a welcome sign, at the bar, near seating information or on table materials. Avoid hiding the only copy beside the DJ, because that recreates the interruption the digital process is meant to reduce. Print it large enough to scan, provide strong contrast and leave clear space around the code.
Test every printed size at the venue before guests arrive. Scan from standing distance in the actual lighting and confirm the destination. Pair the code with one direct line such as “Scan to request a song.” The DJ or emcee can mention the process once after formalities. If a guest asks for help, show them the route without implying that submission guarantees play.
Requests during cocktails may not suit dinner, and dinner choices may not fit the dance floor. The DJ should review each request in the context of the current phase and upcoming formal moments. A strong song can still be wrong immediately before a toast or too early for the peak dancing period.
Watch for duplicates, explicit versions and tracks that undermine the couple’s boundaries. Use the live queue as a communication aid rather than a rigid running order. The DJ can choose transitions that make musical sense while guests see that requests are being handled. Crowd Current also supports shoutouts and tipping, which can be included when they fit the couple’s preferred experience.
Choose a closing point based on the reception timeline, not on the moment the final song begins. The DJ can close requests for the night, preventing late submissions that cannot reasonably be considered. An emcee announcement can thank guests and explain that the remaining music is already planned.
After the wedding, couples do not need a technical report, but the DJ should review what worked. Note whether guests found the code, understood the approval policy and used the curated choices. For plan details, compare Crowd Current pricing. Starter is $0 for up to three events with unlimited requests, while Pro is $39.99 monthly or $399 yearly. Wedding companies needing branded pages, multiple operators and central oversight can discuss custom Organization pricing.
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.
No. Treat requests as suggestions. The DJ approves or rejects every request and considers the couple’s brief, timing and the dance floor.
No. Guests scan a QR code and use the request experience without downloading an app.
Place it where guests naturally look, such as a welcome sign, the bar, seating information or table materials, and test it in the venue lighting.
Close requests before the final stretch, at a point that leaves the DJ enough time to review the remaining queue and plan the finish.
Create an event, share a QR code and manage requests with a clear process.
Create Your Account