Requests, Tips, and Fan Interaction Systems

Why This Lesson Matters

Sequence you are in:

• Previous: Setlists, Segments, and Audience Energy (MU-04) — annotated setlists with request window edges
• This lesson: Requests, Tips, and Fan Interaction Systems (MU-05) — policy, explanation script, fairness card
• Next: Growing a Music Audience on LIVE (MU-06) — clip moments, series, collabs, and return-fan habits
• Core callback (not a reteach): Core L21–22 monetization/community money manners — gratitude and ethics without pressure theater

Brief callback only: your setlist already marked where requests are allowed. This lesson writes the rules of entry and the words you say out loud.

Skip this lesson and every request becomes a mid-song argument. Complete it and Capstone shows include a fair interaction system fans can learn.

Learning Objectives

By the end of this lesson, you will be able to:

• Write a clear request policy covering what you take, when, limits, and declines
• Deliver an on-stream explanation script in under thirty seconds
• Run tips/gifts/shoutouts with fairness rules that avoid guilt and queue-jumping chaos
• Redirect out-of-window requests without killing warmth
• Test the system in a practice session or LIVE and note what to tighten
• File policy + script evidence toward the Signature Music LIVE Show Capstone

Estimated Study Time

• Study and drafting: about 25 minutes to read and write policy + script
• LIVE Mission: finalize artifacts; test the system in practice or LIVE
• First full pass: roughly 60–75 minutes including one dry-run of the explanation script

If you do not take requests in your primary format, still write a short policy that says so — clarity is the skill.

Prerequisites

Complete MU-04 so request windows exist on a real setlist. Know your MU-01 format (request room vs concert with a window vs no requests).

You should already have:

• Setlist A/B with window edges (or an explicit "no request window")
• Stamina awareness from MU-03 (requests cost voice and time)
• Willingness to decline songs you cannot or will not perform

Tools: Request Policy Template, On-Stream Request Explanation Script, Gift/Shoutout Fairness Card. No minimum gifts. No pressure tactics.

Main Lesson

Request culture is a product feature

Treat requests like a feature with specs:

• Intake: how fans submit (chat keyword, typed title, emoji flag)
• Window: when intake is open (from MU-04)
• Eligibility: repertoire you know, language, content boundaries, duplicates
• Limits: max per person, max per window, max difficulty
• Priority rules: fairness first — not loudest chatter, not highest tip by default
• Decline language: short, kind, final

If your primary format is a request room, the whole show is a managed queue. If your primary is concert, requests are a contained segment. Same policy skills; different default window size.

Writing the Request Policy

Open the Request Policy Template and fill these fields in plain language:

1. We take requests when… (clock time / segment name) 2. How to ask… (exact chat format: e.g., "REQUEST: song title") 3. Limits… (e.g., 1 per person per window; 3 songs total) 4. I may decline if… (don't know it, voice budget, content boundary, duplicate, not LIVE-safe) 5. Tips/gifts… (optional thanks; never required to ask; never implied punishment for not tipping) 6. Shoutouts… (what earns one; max length; no queue jump for harassment)

Read it aloud. If you cannot say it without sounding like a lawyer, shorten it.

On-stream explanation script

Fans cannot obey rules they never heard. Use the On-Stream Request Explanation Script at window open (and once at show open if requests are core to the format):

Example skeleton (customize):

"Quick house rules: request window is open for the next ten minutes. Type REQUEST and the song title. One per person. I may pass if I don't know it or need to save voice. Tips are never required to ask — gratitude yes, guilt no. Let's go."

Practice until it is under thirty seconds. Put a shorter redirect line on your phone for outside the window: "Love that pick — park it for the request window after song six."

Tips, gifts, and shoutouts — ethical fairness

Connect to Core L21–22 principles without reteaching modules: gratitude is good; pressure is not. On the Gift/Shoutout Fairness Card, define:

• Thanks cadence: specific, short, then return to the music job
• No guilt phrases: ban "only real fans gift," "don't let me down," silent treatment for non-gifters
• Queue integrity: money does not automatically erase the one-per-person rule unless you explicitly run a *separate*, clearly labeled paid-request product with its own ethics and limits — default Music LIVE path keeps requests fair without pay-to-jump
• Shoutout length caps: so thanks cannot eat the set
• Equal warmth: non-paying requesters still get human respect inside the rules

Operating the queue live

Simple flow:

1. Announce window + script 2. Collect requests in a notes app or visible order you can track 3. Confirm 1–2 upcoming so the room hears fairness 4. Perform / decline with policy language 5. Close window explicitly: "Requests closed — back to the set" 6. After show: note friction in one line for Capstone revision

Duo/band: assign who owns the queue so the lead vocalist is not reading chat mid-phrase.

Special cases

• Writing session: "requests" may be prompts ("write about ___") — still policy + limits
• Karaoke host: turns need time caps and content boundaries
• DJ: requests are often track IDs — energy fit still beats literal obedience
• Launch night: shrink or close requests if promo blocks are dense

Capstone connection

Policy + explanation script + fairness card (plus a test note) feed the Signature Music LIVE Show. Optional Music LIVE Lab / Honors never gates your certificate.

Examples

Example 1 — Concert with late window. Policy: window minutes 48–58; REQUEST: title; one per person; max two performed; tips never required. Script said at minute 47. Declines use "not in tonight's voice budget." Fairness card: shoutouts under eight seconds.

Example 2 — Request-room primary. Policy: queue open most of the night except open/close; still one-per-person until queue empties; difficulty cap on belts; content boundary list. Script at open and every 20 minutes. Stamina plan (MU-03) still rations peaks inside the queue.

Example 3 — No requests format (producer LIVE). Policy statement: "Tonight is a build session — no song requests; idea prompts via PROMPT: after minute 20." Explanation script sets expectation early so chat does not fight the format.

Real Creator Scenarios

Scenario A — "Someone tipped and demanded an immediate skip-the-queue song." Action: thank the tip briefly; point to the fairness card rule; offer the request in order or invite them to a clearly labeled future paid format if you ever create one. Do not invent guilt either direction.

Scenario B — "Chat floods twenty requests in twenty seconds." Action: restate limit; pick visibly from earliest correct-format asks; close intake when the max is hit.

Scenario C — "I feel mean saying no." Action: declines protect the show you promised everyone else. Kind + clear is not mean. Policy language does the emotional labor you practiced in advance.

From Brad's Experience

Pro Tips

• Say the script before the flood — not after you are overwhelmed.
• Require a chat format; free-text chaos is optional suffering.
• Close the window out loud; silent closures confuse regulars.
• Thank gifts in a cadence that returns to music quickly.
• Keep decline reasons boring and repeatable.
• Assign a queue owner in duo/band setups.
• Revise policy after one real test — first drafts are meant to tighten.
• File the test note for Capstone even if the night felt small.

Common Beginner Mistakes

• Taking every request because you fear chat leaving. Fix: limits are hospitality to the whole room.
• Letting tips silently rewrite the queue. Fix: fairness card rules stated in advance.
• Explaining rules only when angry. Fix: script at window open every time.
• Guilt language dressed as motivation. Fix: delete it; use gratitude + structure.
• No decline language practiced. Fix: write three decline lines on the policy sheet.
• Request window overlapping your hardest vocal peak. Fix: realign with MU-03/MU-04.
• Reteaching all of Core monetization mid-music path. Fix: ethics callback only — L21–22 stay in Core.

Reality Check

Your first policy test may include awkward declines and a chat user who pushes. That is data, not failure. Mission success is a written policy, an explanation script, and a documented practice or LIVE test of the system — never whether requests converted to gifts or the clip went wide.

Summary

Requests, Tips, and Fan Interaction Systems means installing fair intake rules, saying them out loud, and protecting the set from guilt-based monetization theater. Windows come from MU-04; words and ethics come from this lesson; Core L21–22 remain a brief manners callback. File policy + script + test notes for the Signature Music LIVE Show Capstone. Optional Music LIVE Lab / Honors never gates your certificate.

LIVE Mission

Mission: Request Policy + Explanation Script + System Test

1. Complete the Request Policy Template for your real MU-01 format (including an explicit no-request policy if that is your choice). 2. Write and time the On-Stream Request Explanation Script (target: under thirty seconds). 3. Fill the Gift/Shoutout Fairness Card with no-guilt rules and shoutout caps. 4. Test the system in a practice session or LIVE: announce, intake, at least one accept or decline using policy language, close the window (or restate no-request rule). 5. Write five lines of after-action notes: what worked, what broke, what you will change.

Success is graded on implementation — policy, script, and a real test — never on viewers, gifts, or virality.

Downloads

• Request Policy Template — window, intake format, limits, declines, tips ethics
• On-Stream Request Explanation Script — sub-thirty-second house-rules delivery
• Gift/Shoutout Fairness Card — gratitude cadence, no-guilt rules, shoutout caps, queue integrity

Quiz

Take the interactive lesson quiz on this page (70% to pass). It includes scenario questions on fair queues, declines, guilt boundaries, and window management — not gift maximization tricks.

Key Takeaways

• Request culture needs intake, window, limits, and decline language
• Explain rules before the flood; redirect outside the window warmly
• Tips earn thanks — never guilt or silent punishment
• Default path: fairness over pay-to-jump chaos
• Core L21–22 are ethics callbacks only — not a monetization reteach
• Test the system once and revise from notes
• Artifacts feed the Signature Music LIVE Show Capstone
• Optional Music LIVE Lab / Honors never gates your certificate

Before You Move On

☐ Finished reading this lesson

☐ Completed the Request Policy Template

☐ Wrote and timed the on-stream explanation script

☐ Completed the Gift/Shoutout Fairness Card

☐ Tested the system in practice or LIVE

☐ Wrote after-action notes (what to tighten)

☐ Passed the Lesson Quiz (70%+)

☐ Filed policy + script + test notes for Capstone evidence

Next Lesson Preview

Next up: Growing a Music Audience on LIVE (MU-06). You now have a fair room once people arrive — next you design how they find you and return: clip moments worth saving, a series that trains habit, collabs that introduce you cleanly, and a conversion path from one-time listener to return fan. Growth Mastery GR-01 is recommended parallel context; MU-06 stays musician-specific on LIVE.