The Request feature is how you collect content from many people at once without chasing anyone for files. Think of it as a raindrop strategy: send one link wide, and contributions trickle in from everywhere into one place. Here's how to build a Request that actually fills up.

Start with a clear title so contributors know exactly what they're submitting to, and set a close date. The close date is the quiet force that makes a Request fill up. An open-ended Request gets put off indefinitely; a Request with "closes Friday" gets done. The deadline is doing the same work it does in any other content workflow: turning a someday into a this-week.

A Request link with a cover image looks like a real, considered ask. A bare link looks like spam. The cover image is a small touch that meaningfully raises response rates because it signals the Request is official and worth a contributor's time. Add one that matches the campaign or the brand so the contributor trusts the link the moment they open it.

Build the questions that shape what comes back. A video question prompts a recorded response; an upload question collects a file. Keep the questions specific and few, the same discipline that makes any Request work: two focused questions beat five vague ones. The questions are what turn a pile of random submissions into usable, on-topic content.

Once the Request is built, generate the shareable link. Anyone with the link can record or upload a response without needing a MarketScale account, which is what makes the raindrop strategy work at scale. Send it in an email, drop it in Slack, print it as a QR code at an event. Every response lands in your pipeline, organized under that Request, ready to triage.

Pick one thing you want content from many people on. Build a Request in MarketScale: clear title, a close date a week out, a cover image, and two specific questions. Generate the link and send it wide. Watch the contributions trickle in to one place, no account required, no files to chase.