DJOS

Managing song requests

Every guest request lands in one queue as it comes in. This guide covers the three actions you take on a request and the protections that keep the queue clean without you touching it.

The queue

Requests show newest first with the song, the artist, any note, the requester’s name, and how long ago it arrived. Each one has three actions.

ActionWhat it means
ApproveYou plan to play it. The guest sees it was approved.
PlayedIt has been played. Any other pending or approved request for the same song is marked played too.
RejectIt will not be played tonight. The guest sees it was declined.
FigureDJOS · Requests tab· joinvyve.io/dashboard/events/…/dj
joinvyve.io/dashboard/events/…/dj
Saturday Night Live
Aurora Rooftop · joinvyve.io/go/7KQ4M
LiveRequests 2Energy 87%Scene CrowdEnd live
LiveRequestsCrowdOSConnectActivityDisplay
Request queue
OpenClear queue5
Blinding Lights
The Weeknd · Requested by Sam · just now
pending123
Levitating
Dua Lipa · Requested by Alex · 1 min
pendingApprovePlayedReject
Good Days
SZA · Requested by Taylor · 4 min
approvedApprovePlayedReject
One Dance
Drake · Requested by Marcus · 24 min
playedApprovePlayedReject
Guest portalRequests, reactions, polls, shoutouts, and photos from one link.
Show QR4
  1. 1ApproveYou plan to play it. The guest is told it was approved.
  2. 2PlayedMarks it played and cascades to every other request for the same song.
  3. 3RejectNot tonight. The guest is told it was declined, with the reason if AI decided.
  4. 4Show QRThe event's QR code and short link, joinvyve.io/go/CODE, for a guest who cannot scan.
  5. 5Clear queueDismisses every pending request at once. Use it at the start of a fresh night.
Interactive: the buttons on the first row change its status. Guests see the result on their phone within a couple of seconds.

Duplicate protection

The same phone cannot send the same request over and over. VYVE catches repeats even with typos, different capitalization, or the artist typed into the title field. Other phones requesting the same song are not affected; the protection is per device.

Once a song is marked played, requesting it again is blocked for everyone for the next 24 hours. The guest sees a message that it already played.

Note
Why 24 hours
Residencies reuse one event week after week. A permanent block would mean a song played three weeks ago could never be requested again. A trailing 24-hour window protects tonight without punishing next week.

The played cascade

Marking one request as played also marks every other pending or approved request for the same song as played, matched the same way as duplicate protection. You never clear five copies of the same request by hand.

AI moderation for requests

On Pro and Enterprise, AI moderation reads the free-text fields of each request the moment it arrives. It only ever does two things: reject genuine hate speech, harassment, or spam that is not tied to a real song, and mark junk such as “skip” or gibberish as not a request, which the guest sees with a light tone since it is not a violation. It never approves a request into your set. Whether to play a song stays your call.

Real songs with rough titles are safe. The model is told explicitly that legitimately titled tracks are requests, not violations, so a guest can ask for them like anything else.

Closing requests

To stop new requests without ending the night, turn off Song requests on the Live tab. The request option disappears from guests’ phones with no lock message. See Runtime controls and guest intake.

Still stuck?

Send a message with your venue name and what you were trying to do. A person reads every one and replies by email.

Contact support