Collect Wedding Song Requests Without a Group Chat
Skip the WhatsApp song-request chaos. Here is how UK couples collect guest playlist ideas, avoid duplicates and keep the DJ happy — without another group chat.

Written by
Guestlive Editorial
Someone always offers to “just start a song-request thread”. Then the chat fills with half titles, Spotify links nobody can open and three versions of the same Abba track. Your DJ gets a screenshot dump the night before. Guests who muted the group never saw the ask. There is a calmer way to collect wedding song requests — and it does not need another WhatsApp group.
Last updated: 30 September 2026

Jump to
- Why song-request group chats go sideways
- What a good request system actually needs
- Options that beat a chat scroll
- How to brief guests without nagging
- Working with your DJ or band
- Group chat vs shared doc vs event playlist
- A calm playlist stack for UK weddings
- Frequently asked questions
Why song-request group chats go sideways
Song ideas feel casual, so couples drop them into the same chat they use for taxis and seating drama. That is where the friction starts.
- Noise buries the list — a useful request sits between parking debates and hen-do photos.
- Duplicates everywhere — five people type “Mr Brightside”; nobody knows which version or who asked first.
- Incomplete titles — “that one from the film” is not a cue sheet.
- Muted guests miss the ask — the people who hate group chats are often the ones with the best dance-floor taste.
- Day vs evening muddle — evening-only guests get flooded with brunch logistics; day guests see late-night playlist spam they do not need. (If that split is already messy, see day and evening guests on one wedding website.)
- Zero host control — you cannot quietly remove a joke request or a track that is firmly on your do-not-play list without a public argument.
A chat is a conversation tool. A playlist is a curated list. Mixing them creates work for you and fog for the DJ.
What a good request system actually needs
Before you pick a tool, decide what “done” looks like:
- One place guests can find — a link or QR they can open when they choose, not a chat they must unmute.
- Clear song details — title and artist at minimum; album or year helps for covers.
- A way to surface favourites — voting or hearts so you see what the room actually wants, not who typed first.
- Host control — remove songs, clear the list, or require approval before anything appears.
- Something your DJ can use — a clean export or shared view, not a twenty-screenshot mosaic.
- Optional, not mandatory — guests who do not care about music should never feel they failed a homework task.
If your system hits those six, the dance floor gets better and your group chats get quieter. For the wider case against wedding WhatsApp overload, we wrote Stop the WhatsApp Wedding Group: Calmer Alternatives.

Options that beat a chat scroll
Shared notes and spreadsheets
A Google Sheet or Notion page is already better than a chat. Guests add rows; you sort and dedupe. Weak spots: people need the link, mobile editing is fiddly, and there is no natural “upvote this” moment on the night. Fine for a small wedding if someone enjoys spreadsheet admin.
Paper cards on tables
Classic and charming. Guests scribble a track; you collect at midnight. Weak spots: handwriting, lost cards, and no easy way to spot the same song twelve times until you type everything up.
DJ open requests on the night only
Some couples skip pre-wedding requests and let the DJ take shout-outs. That works if your DJ is brilliant at reading a room. It does not help you plan do-not-play lists or first-dance neighbours in advance.
An in-browser event playlist
Guests open a private link or scan a QR, search for a song and add it — no app install. Hosts can require approval, remove tracks, clear the list and see what is trending. A solid event playlist also helps with duplicates and can export toward Apple Music so you are not rebuilding the list by hand. That is the shape most UK couples want once the guest list climbs past fifty.
How to brief guests without nagging
You do not need a manifesto. A short note on the wedding website or invitation insert is enough:
We would love your song ideas. Add them here — no group chat required. We will share the list with our DJ. Please skip anything on our do-not-play note.
Tips that keep requests useful:
- Open requests early, close gently — invite ideas a few weeks out; remind once near the wedding. No daily pings.
- Put the QR where people already look — website, table card, welcome sign. A tidy reception table with a small card beats another broadcast message.
- Separate “must play” from “nice to have” — your first dance and parent dances stay yours; guest requests fill the party hours.
- Publish a short do-not-play list — kinder than rejecting tracks one by one in public.
- Tell evening guests where to look — one link for schedule, photos and playlist beats three different chats. Voice notes for messages to the couple can live elsewhere too — see voice note guestbook without a rotary phone.

Working with your DJ or band
Professionals would rather receive a tidy list than a chaotic chat export. Ask early what format they prefer — Apple Music, Spotify, a spreadsheet, or a shared page they can refresh on the night.
Helpful host habits:
- Send a first pass a fortnight out — must-plays, do-not-plays and mood notes (ceilidh energy, indie, Motown, no cheesy megamix, and so on).
- Share guest requests as a living list — not a final exam the morning of the wedding.
- Flag cultural or family tracks — so they are not lost under trending pop votes.
- Agree who has final say on the night — usually the DJ reads the room; your list is a guide, not a prison.
If you use an event playlist with approval mode, you can keep joke requests and break-up anthems off the public list before they ever reach the booth.
Group chat vs shared doc vs event playlist
| Approach | Guest effort | Host control | DJ-ready | Best for |
|---|---|---|---|---|
| WhatsApp / group chat | Low at first, noisy later | Weak — hard to edit or approve | Poor — screenshots and duplicates | Tiny guest lists who already live in one chat |
| Shared spreadsheet or note | Medium — link + typing | Good if you tidy rows | Fair — exportable but manual | Couples happy to admin a sheet |
| Paper request cards | Low on the night | Medium — you type later | Fair after data entry | Intimate receptions, craft-led stationery |
| In-browser event playlist | Low — scan QR, search song | Strong — remove, clear, approve, vote | Strong — curated list + music export | Most UK weddings wanting calm requests |
A calm playlist stack for UK weddings
You do not need five apps. One private event link can carry the website, RSVPs, photos and song requests — and you can leave unused features off.
A practical stack looks like this:
- Wedding website for timings, dress code, travel and the single playlist link.
- Event playlist so guests request and heart songs in the browser; you approve or remove as needed; export for Apple Music or hand the curated view to your DJ. (GuestLive Playlist is built for exactly that.)
- Photo gallery so candids do not flood the same place as track titles — and remember galleries can stay available; there is no need to invent a closing window.
- Optional voice guestbook or Funds if you want messages or contributions without stuffing them into the music chat.
GuestLive is a UK wedding and event platform: £29 once, no guest app. Guests scan a QR or open a private link in the browser. Playlist includes in-browser requests, upvote/heart voting, host remove/clear/approval controls, trending and dedupe help, plus Apple Music connect/export. Pricing is on guestlive.co.uk/pricing if you want the full picture.

Frequently asked questions
Do we still need a WhatsApp group for anything?
Maybe for a tiny logistics circle (wedding party, parents, suppliers). Song requests, photo dumps and the full guest list do not belong there. Keep the chat small and purposeful.
What if guests request songs we hate?
Use approval mode or remove tracks. Publish a short do-not-play list so people know the boundaries. A private edit is kinder than a public “please stop” in a group chat.
Can the DJ take requests on the night as well?
Yes. Pre-wedding requests shape the library; on-the-night shouts fill gaps when the room shifts. Give your DJ both the curated list and permission to read the floor.
Will older guests manage a QR playlist?
Most will if the QR sits on the table and the page is mobile-simple — search, tap, done. Offer to add a relative’s favourite yourself if they prefer asking in person.
Should song requests be open before the wedding or only at the reception?
Both can work. Opening early builds a richer list and catches guests who travel. Keeping a live list on the night captures mood shifts. Many couples do a quiet pre-wedding window, then leave requests open during the party.
How is this different from sharing a Spotify collaborative playlist?
Collaborative playlists help, but they often need accounts, invite links and little host approval. An event playlist aimed at weddings is built around guest access without an app, voting, host moderation and a clean handoff to the DJ.
Ready to start your own celebration?
Set up your event in minutes and start collecting memories with GuestLive.
Create Your Event Today with GuestLiveTags
Join the conversation
Comments are coming soon. Have feedback? Email us at hello@guestlive.co.uk

