How to run an event - from start to finish

If you haven't created an event yet, start with the how to create an event guide - it covers naming, date, type (public / private), venue, playlist and dedications.

Once your event is set up and waiting to start, come back here - this is everything you need while it's running.

When the time you scheduled arrives, open the event in the app and tap "Start event". Only then does the event go live and guests can scan the QR code and send requests.

Note: if guests scan the QR before you start, they see a screen telling them the event hasn't started yet, and they wait.

Once the event is live, the dashboard shows two main tabs:

• Accepted Songs - everything you've already accepted, waiting to be played
• Requests - new requests from guests waiting for your decision

Next to the Requests tab a red dot and the number of new requests appears - so you always know if someone is waiting.

Pro tip: if you've been away from your phone for a while (e.g. just played a song), do a pull-to-refresh to make sure the data is up to date.

Live stats in the header

Above the tabs you see the key event metrics live:

• Number of users who scanned the QR and entered the event
• Total accepted songs
• Total earnings from this event

Each request contains:

• Song name
• Amount the guest offered
• Nickname of the person who requested it
• A flag if it's a premium song (and the dedication if the guest left one)

When you accept a song

The app first opens a confirmation modal, then the song briefly shows "Payment in progress" while the server processes the charge. On success, the user is charged (card or in-app balance), the song enters the queue and the guest gets a push. If the payment fails (insufficient funds, card issue), the song doesn't enter the queue and the guest gets a notification with the reason.

Recommended timeframes: regular songs within 30 minutes, premium songs as soon as possible - ideally right away.

When you decline a song

The modal includes an optional "Decline reason" field - a short note the guest will see. No money is charged, and the guest can immediately request another song or raise the price.

Cancelled songs from guests

Below the new requests list, a "Cancelled songs" section may appear - requests the guest pulled back themselves while waiting for your decision. Informational - no action needed.

The system automatically sorts the queue: played → premium in queue → standard in queue. If you try to play a standard song while a premium one is still waiting, you'll see: "Please play all premium songs before playing standard songs." Guests who paid for premium placement should hear those songs first.

This tab holds every song you've accepted. Tapping a song marks it as "now playing" - and that's a critical step:

• The user who requested it gets a notification that their song is now on - that's their "moment" for stories, sharing and excitement
• The song is visually marked as active on every guest's screen

Play confirmation and dedications

Before a song goes live, the app opens a "Play next song" modal to protect you from accidental taps. If the song has a dedication, you'll see it under the title in a "Dedication" block - read it on the mic alongside the song, it's the moment the guest paid premium for. Once played, the song can't be pushed back into the queue.

The list is public to everyone in the venue

The list of accepted songs is visible to all guests in the venue - everyone sees what's coming and in what order. Each song also shows the number of likes guests have given it, so you know which one is heating up the crowd.

The event room is connected to the server live - new requests, song statuses, guest count, income and cancellations all update on their own (with toast notifications). If the connection drops, the app tries to reconnect in the background; for a forced sync, do a pull-to-refresh.

At any time you can hit "Pause event". When paused:

• Guests can't send new requests - on their side a banner shows "Song requests are paused"
• You still see and process requests already in the queue — everything works as before, just without new ones coming in
• In the room you see a gold "Paused" bar with a reminder not to leave the event paused for too long - guests lose interest fast

Perfect for breaks between sets, swapping performers, or when requests pile up faster than you can handle.

When you're ready to resume, the same button becomes "Resume event" - tap and the event goes back to Live. Guests get a notification: "The party has restarted! Don't forget to request your favorite song."

Mid-event you can only change what makes sense: playlist, standard and premium song price, and the dedications toggle.

Everything else (name, date, venue, address, genres, image, public/private type) locks when the event goes Live so guests don't see core data shift mid-event. If you absolutely must change those, end the event and create a new one.

By tapping "Update event" at any time you can change:

• Minimum premium song price - if requests are piling up too fast or too slow, adjust up or down
• Playlist - swap to a different song list offered to guests. See how to create and manage playlists
• Dedications option - turn on/off the ability for guests to attach dedications to premium songs

Pro tip: prepare as many playlists as you can in advance and switch them through the night (warm-up, prime time, after midnight). That way you get better and more varied requests, and the night doesn't feel like a loop of the same songs.

When the party is done, tap "End event". A confirmation modal opens. If there are still unplayed songs in the queue, you'll see a warning:

There are still songs that haven't been played
Are you sure you want to end the event?

After confirming, the event moves to Closed and you exit the room automatically. New requests stop coming, and any pending ones auto-cancel (those guests aren't charged).

Ending is irreversible - the event can't be re-opened as Live. If you really need to, create a new one.

In the "Finished" tab, tapping a card opens an overview with: requested and accepted song counts, total income, song list (guest, song, paid amount, dedication) and a "Paid but not played" flag for accepted songs you didn't get to play. The screen is informational only - no retroactive play or reject.

Can I change the premium song price during the event?

Yes, anytime through Update event. The change applies to all new requests - songs already requested keep the price they were requested at.

What if I accept a song and then can't play it?

Try to avoid it because the money is already charged. If it does happen, message the guest with the reason - and email us at info@getjukebox.app so we can handle the refund without it hurting your rating.

Can guests see each other's requests?

Yes. The Accepted Songs list is public - all guests in the venue see what's coming and in what order. That lifts the mood and encourages likes.

How do guests know their song is up next?

When you tap a song in the Accepted Songs tab (mark it as "now playing"), the user who requested it gets a push notification in the app.

What if data isn't up to date?

After being away from the app for a while (e.g. you played a song without checking), pull the screen down to force a refresh. That way you're sure to see the latest requests and stats.