Requests let you crowdsource content: video, text and files from your team, customers, partners or MarketScale's network of experts. Build a Request around one clear contribution, send it to the right people, then turn the best responses into finished content.
Who can create and manage Requests
Use a role with Request creation access in the channel you want. Social users don't have this workflow. A Request is managed by its creator, any collaborators the creator adds, and authorized channel Admins. Collaborators can see everything the Request collects and edit its settings.
Before you start, decide who should respond, what you'll ask, how you'll use the answers and your deadline.
Create a Request in the form builder
Open Requests and choose Create request. Studio opens either the form builder or a guided conversation; follow the matching steps.
Enter a Request title, or leave it blank and Studio uses your first question as the title. Add a short description of the audience and how you'll use the responses. For example: "Show one valve-installation check for our distributor training library."
Add at least one complete question. Choose its answer types (text, upload or video) and set Required deliberately. A responder must answer at least one question to submit.
Review the Request settings: close date (the Request closes automatically that day), response folder, Email response notifications, collaborators, and any custom terms your organization requires.
If you want to offer a gift, turn on Add a reward and finish the reward setup before sending. See Offer a reward on a MarketScale Request.
Under Who should respond?, choose Shareable link, Invite channel users, or an available connected hub. Check the names and email addresses for invitations.
Choose the matching final action once, and wait for its result: Create request link, Send request, or Post request to hub.
Open the collector link and check the title, company, questions and response options. For invitations, check the sending status on the Request; a queued invitation isn't proof of delivery.
Save as template stores a reusable starting point. It doesn't publish a new Request.
If Studio opens the guided conversation
Describe your audience, subject and the response you want. Review the proposed questions and answer types, edit the wording and Required settings, then choose Use this.
If another suggestion appears, read the Review suggested questions notice. Use suggested questions replaces your whole question list. Choose Back to edited draft to keep your own version.
Review collaborators, Email response notifications and Advanced settings. Media visibility controls who can see content created from responses later; it's separate from who you invite to answer.
Choose Create request to finish setup, or Save as draft to come back later. A draft isn't live; use Finish it when you're ready.
Choose Generate a shareable link or Select existing channel users, review recipients, then Send invites. Use Copy link or Open collector to see exactly what responders will see.
Recover a saved Request without creating duplicates
Request saved. Sending didn't finish.: choose Try sending again to resume the same Request, or Edit saved request to fix it. Saved questions don't prove invitations went out.
Your saved requests are safe: check each Request's state, then choose Continue setup to finish it. You choose invitations after setup finishes.
We could not confirm the save: choose Check your Requests first. If the Request exists, continue from it instead of creating another copy.
An invitation is queued or failed: check its status and correct the recipient on the Request. Don't re-send to the whole audience while the outcome is unclear.
Review responses and turn them into content
Return to Requests, search by title or creator, and open the Request's responses.
Review each answer, its media and who sent it. Receiving a response doesn't approve it for distribution.
Select the responses you want, check the title, source material and visibility, and create content from them. From a Media Studio you can order editing, use AI writing on text answers and transcripts, order AI translation, or generate AI social clips.
Complete editing, approval and publishing as separate steps.
Responses stay private to the Request's creator, collaborators and Admins until you create content from them. Once you do, that content follows the visibility you chose. A response must become a media card before you can add it to a folder.
If something doesn't work
Creation is unavailable: check your role and the selected channel. A responder link doesn't give anyone access to manage the Request.
The form won't finish: check question content, Required settings, a close date of today or later, selected recipients and any reward errors. An existing Request needs a title when you save changes.
People can't answer: check whether the Request is a draft, paused, closed or past its deadline.
The gift-card catalog is unavailable: use the retry shown, or turn off Add a reward if you want to send without one. Don't promise a gift the Request can't deliver.
Frequently asked questions
Can I edit a Request after it's been shared?
Yes. Open the Request, choose Edit from its menu, and update the questions, description or settings. Changes apply going forward.
Is a Request the same as a Survey or Media Request?
Yes. Requests replaced both Surveys and the old Media Request, with the same core purpose and more response options.
What to do next
Share your Request as a public link with Create and share an Open Link Request. To see what responders experience, read How to Respond to a Request on MarketScale.