Describe your event and audience. Makeform creates a DJ request form for guest song choices, do-not-play notes, dedications, or booking inquiries.
Route DJ requests to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a starting point, adapt it, and send the prompt to the Makeform builder.
Audience
Wedding guests suggesting songs before the reception
Format
Guest request form with dedication and playlist guidance
Prompt size
220 chars
Example form structure
Guest request form with dedication and playlist guidance
Guest name
Song title and artist
Must-play or nice-to-have?
Best moment for this song
Dedication or context
Suggested routing tags
Guest requests
Client inquiries
Needs follow-up
Ask for both a must-play and a do-not-play list; knowing what to avoid can be as useful as knowing the favorite song.
Step 1
Collect
songs, artists, event code, or booking details
Step 2
Sort
separate guest requests from client inquiries
Step 3
Review
check duplicates, timing, fit, and special notes
Step 4
Act
prepare the set or follow up on the booking
A cleaner request workflow
Structured fields distinguish important event songs from casual suggestions and give booking leads enough context for review.
Separate title, artist, priority, dedication, and event moment for easy scanning.
Use separate versions or conditional paths for guest requests and bookings.
Route inquiries with date, venue, attendance, services, and contact preference.
Built around the event
Pre-event planning needs more detail than a live QR request. Keep only fields that support the next decision.
Keep it to event code, track, artist, and optional note so guests can submit quickly from a phone.
Collect must-play moments, do-not-play tracks, cultural selections, dedications, and pronunciation notes before the reception.
Add clean-version details, organizer review, and a visible request policy.
Qualify event type, schedule, venue, guest count, equipment needs, add-ons, and budget before arranging a call.
Build the request flow
Describe what the DJ needs, edit the fields, and share the finished form.
Identify live guests, wedding clients, students, or booking prospects.
Add event choices, require essentials, and explain request review.
Share a link, embed the form, or display its QR code.
Use submissions as one planning list, filter by event identifier, and follow up on qualified booking inquiries.
Choose the collection method
A DJ request form preserves names, tracks, event context, and booking details in consistent fields.
Field guide
Keep guest forms quick. Booking forms can ask more because the answers shape availability, setup, and follow-up.
Track identification
Pair the title with the artist and an optional version link so the DJ can identify the intended recording.
Priority and moment
Priority, timing, and dedication distinguish an essential event moment from a casual suggestion.
Guest context
A name helps resolve questions. An event code keeps simultaneous parties from sharing a queue.
Request policy
Explain that requests inform the playlist and may be reviewed. Add an acknowledgment so playback is not assumed.
Booking logistics
Date, hours, venue, attendance, and environment help determine whether the job fits the DJ's schedule and setup.
Client fit and follow-up
Music direction, add-ons, budget, and contact preference make an inquiry easier to answer and route.
Related tools
Pair song collection with planning, RSVP, booking, and feedback forms.
Create a focused song submission form for parties, broadcasts, or shared playlists.
Open toolGather the schedule, audience, vendors, venue details, and organizer priorities.
Open toolCollect attendance decisions and guest details before the event date.
Open toolManage wedding attendance alongside music requests and reception planning.
Open toolStart a broader appointment or service-booking flow for prospective clients.
Open toolAsk organizers and attendees what worked after the final track ends.
Open toolFAQ
Straight answers for DJs and event hosts planning song collection or qualifying new bookings.
A DJ request form collects song suggestions or booking inquiries in consistent fields. Guest versions ask for the track, artist, event, and dedication. Client versions ask about the date, venue, attendance, services, and contact details.
Start with song title, artist, guest name, and event identifier. Add priority, moment, dedication, genre, or version only when useful. Keep a live QR form shorter than a pre-event questionnaire.
Yes. Ask for an event code or event dropdown, then filter responses by that value. Use codes that are easy to enter but distinct enough to separate simultaneous parties.
Put a short policy above the submit button with an acknowledgment checkbox. Explain that requests guide the playlist and are considered alongside timing, event rules, and audience fit.
Yes. Build a separate inquiry version or conditional path. Ask for contact, event type, schedule, venue, guest count, setup, services, music preferences, budget, requirements, and follow-up method.
Use distinct fields or a priority dropdown. Ask clients to label essential moments and provide artists or versions. Keep do-not-play selections in a separate section.
Yes. Makeform offers unlimited free forms and responses, so you can generate, edit, publish, and collect DJ requests without a response cap. The paid tier removes the Makeform badge.
Publish a link or embed the form on an event page. For in-person use, put its QR code on table cards, signage, or a screen. Test submission on a phone before doors open.
Give every request a clear place to land.
