A cocktail hour song request system that actually works

Wedding cocktail hours are 60 minutes of carefully choreographed mingling. Guests are in transition — ceremony just ended, reception hasn't started. They're looking for their seat, grabbing their first drink, avoiding the aunt they don't like. And they're listening to the band set the tone.

Taking requests during cocktail hour usually goes one of two ways: awkwardly (guests interrupting between songs, the lead vocal fielding “do you know...” attempts, 15 minutes lost to chat) or badly (requests ignored, guests frustrated, couple fielding complaints later). Here's a system that makes it smooth.

The problem with cocktail-hour requests

Unlike reception dancing, cocktail hour is a background-music moment. The band isn't playing “dance songs” — they're playing jazz standards, light pop, acoustic covers. The role is ambiance, not engagement.

But guests don't read the room that way. They hear a band, they want to request. The band pauses between songs to hear the request, shifts instrumentation, loses the flow. Now they're not background anymore — they're doing a live Q&A.

Doing this three times in an hour eats 10–15 minutes of actual music. The cocktail hour vibe suffers. The couple notices.

The QR-on-highboys solution

The fix: move the request-taking off the band and onto a self-serve QR flow on every highboy table. Guests can request whenever they want; the band plays continuously without interruptions.

Implementation:

1. Pre-filter your band's setlist to “cocktail-hour appropriate” songs. Anything high-energy or dance-heavy: off. Smooth / ambient / classic: on.
2. Print a small QR card for every highboy. Minimalist design — something like “Song requests — scan.” No “TIP” language (tips feel weird at weddings).
3. During cocktail hour, requests arrive in the band's hidden queue. Lead checks between songs and slots them naturally.
4. Auto-refund anything you don't get to by end of the hour.

The band plays continuous 60 minutes without interruption. Guests still feel heard.

The filtered cocktail-hour setlist

Here's the nuance that makes this work: not every song in your repertoire should be available during cocktail hour. Guests will request dance-floor bangers in the middle of hors d'oeuvres service if allowed.

Use a platform that lets you toggle song availability by time window. In Encore, you can enable/disable individual songs — the cocktail-hour menu might be 30 songs; the reception dance-floor menu might be 60.

Typical cocktail-hour filter:

• In: jazz standards, smooth acoustic covers, instrumental versions, classic pop at low tempo
• Out: dance-floor bangers, anything with a heavy kick, request-heavy crowd-sing-along territory

Guests don't realize they're seeing a filtered list. They just see “songs the band plays.” Nobody requests “Shout” during cocktail hour because it's not on the menu.

Pricing (or not)

Should cocktail-hour requests be paid or free?

Free: If the couple is paying the band well and tipping feels awkward, leave requests free. The system still works — it captures requests into a queue, filters the setlist, manages flow. Just without money on top.

Paid (with tipping disabled):If the band is open to cocktail-hour tips supplementing the base fee. Low-key pricing — $5 base, no priority tier during cocktail hour. Guests who pay are signaling priority; the band works it in but doesn't hyper-prioritize.

Paid (priority tier enabled): Rare at weddings. Not recommended for cocktail hour — feels auction-y. Save priority tier for reception dancing.

Most bands we work with use: free requests during cocktail hour, paid requests during reception. Easy toggle in Encore.

The lead's script

Once per cocktail hour, the lead mentions the QR:

“For the next hour, we're taking requests — if you'd like to hear something specific, there's a QR on the cocktail tables. Pick from what we know, we'll work it in.”

Once is enough. Twice starts to feel promotional, which breaks the ambiance. One mention, usually 20 minutes into cocktail hour (after guests have had time to settle).

The queue management

During the 60-minute window, requests trickle in — typically 5–12 per hour for a 80–150 guest wedding. The band's workflow:

• Lead checks the queue every 2–3 songs (between songs, discrete glance at iPad or phone).
• Slot requests in the next natural break — not mid-medley, but at the end of the current piece.
• Mark each as “played” in the app (auto-payout).
• Anything not played by the end of the hour auto-refunds. Fan isn't charged for a song they didn't hear.

Net result: continuous 60-minute set with ~10 natural-feeling request fills woven in.

What it looks like on the guest side

Guest arrives at cocktail hour, grabs a drink, finds a highboy. Notices the small card. Scans the QR. Sees the band's cocktail-hour menu (30 songs, neutral design, no pricing clutter).

Taps a song. Hits request. Either it's free (“request submitted”) or it charges $5 via Apple Pay in 3 seconds. Done.

20 minutes later, the band plays it. Guest hears it. Smiles. Whole interaction: seamless, no band-interruption, perfectly on-vibe.

Compared to the old way

Without a QR flow, guests either:

• Don't request (they know it's awkward), and feel disconnected
• Interrupt between songs, making the band stop
• Ambush the drummer at the drum kit, making things worse

With a QR flow, the interaction is clean. 80% of the requests that would've been shy-and-unstated get submitted. 100% of the awkward-interruptions disappear. The band plays continuously.

Bottom line

A cocktail-hour request system that works is: (1) filtered setlist menu, (2) QR on every highboy, (3) hidden queue for the band, (4) auto-refund at hour's end, (5) pricing choice per event (free / low-key paid).

The 60-minute set flows without interruption. Guests still get requests. The couple doesn't field complaints. Nobody ambushes the drummer.

Encore for wedding musicians is set up for exactly this: time-windowed menus, filtered song lists, tipping toggle, automatic refunds.