How to Get Rights to Repost Customer UGC (with Templates that Average 38% Yes-Rate)
DM, comment and email templates, the 24-hour ask window, one-tap consent links and audit trails.
A customer posts your jacket, and you want it on the product page by Friday. You send a long DM full of legal wording. Two weeks later there is still no reply. The templates below are short, specific and sent within a day.
Say you want to repost a customer's post on your site, in email or in ads. To do it legally, you need explicit written permission for that specific piece, granted before publication. A "thanks for tagging us!" comment does not count. Nor does a like on the original post, or a creator's public Terms-of-Use paste-in. What counts is an unambiguous yes from the named creator, tied to specific content. It has a documented scope and duration. You can pull it from an audit log when a dispute arises.
The good news: rights collection is mechanical. The brands hitting 60%+ yes-rates move faster and ask more specifically. They make consent a single tap. Their copy is ordinary. The templates below follow that: the right ask, at the right moment, on the right channel.
In this article
What "legal permission" actually means
A valid consent record survives a creator lawsuit, a GDPR audit or a platform takedown notice. It covers four elements at minimum:
- 1Identification of the specific content. Original URL or post ID, screenshot of the asset, timestamp it was captured. "All your future posts about us" doesn't pass.
- 2Scope of permitted use. Where the brand will display it. PDP only, or email + paid ads + retail signage? List each surface explicitly. Scope creep is the most common cause of creator complaints later.
- 3Duration. Most consent is granted "until revoked." Time-limited rights (e.g. "for the spring campaign only") are legally valid but operationally painful to track.
- 4Unambiguous yes from the creator. A reply containing "yes" or a tap on a consent button. Silence is not consent. A liked post is not consent. A retweet is not consent.
Three regulatory frameworks make this non-optional. GDPR (EU + UK) requires a documented lawful basis for commercial reuse of identifiable content. In practice that means explicit consent. CCPA / CPRA (California) requires the same, plus a documented workflow that honours deletion within 45 days. FTC Endorsement Guides (US) require disclosure of any material connection between brand and creator. The fuller regulatory picture sits in GDPR + UGC compliance, CCPA + customer reviews, and FTC endorsement guidelines.
Yes-rate by channel and timing: the operational data
38%
Overall median yes-rate
Across all channels · competent programme
24%
Instagram DM
Within 24h of post · personalised
32%
Public comment tag
Yes-reply mechanism · auditable
41%
Email (high-value content)
Substantive scope · most defensible
Three patterns are worth designing around. Timing dominates copy quality. A mediocre template sent within 24 hours of the post beats a polished one sent at day 14. The creator's enthusiasm for the brand decays faster than most brands assume. A request that lands the same day, while the post is fresh, is far likelier to get a yes. One that arrives a fortnight later is not. So same-day automated outreach beats a manual weekly cadence.
Channel matches content scope. Instagram DM works for "can we use this on our website?" Email works for "can we use this in a paid Meta campaign, in lifecycle email, on retail signage, and in the spring catalogue?" Asking for full commercial scope on a DM gets a 6% yes-rate. Asking for the same scope by email gets 41%. Use the channel that matches the size of the ask.
Personalisation is the single biggest copy lever. Templated mass-DM yes-rates drop to 8%. Personalised DMs hit 24%. They name the specific photo, say what the brand likes about it and capitalise the handle correctly. Skip writing 60 unique DMs by hand. Use merge fields that fill in one specific detail per request. AI-assisted personalisation auto-extracts a "what's in the photo" tag. It gets you 70% of the lift for 5% of the effort.
Which channel for the ask? Match it to the scope
Start here
What are you asking the creator for?
- Website, PDP or gallery use
Instagram / TikTok DM (24% yes-rate).
The native channel for consumer-grade content. Personalise one specific detail and offer credit plus a link back. Put the one-tap consent link at the bottom. Ask within 24 hours.
- No reply: Re-approach once at day 7, then stop
- High-volume, lower-risk content
Public comment tag (32% yes-rate).
The yes lives on the post forever, which is good evidence. Comments also dodge the ~50-DMs-a-day rate limit on mass outreach.
- Post is sponsored content: Check the bio and recent posts for "ad" tags first; DM instead of commenting
- Paid ads, email or signage: full commercial scope
Email (41% yes-rate).
Big asks need substantive context: scope, duration, credit and compensation laid out line by line. The same scope asked over DM lands at 6%.
- No current email on the profile: Fall back to DM and keep the scope small
Template 1. Instagram / TikTok DM (24% yes-rate)
Use for: any consumer-grade content (PDPs, social feeds, gallery walls). Default channel for the first ask.
Three things this template does right. One specific detail shows a real person is asking. The creator's "is this spam?" check does not fire. The credit + link offer leads with what the creator gets. Most creators want the brand traffic. The one-tap consent link sits at the bottom for creators ready to formalise it now. The YES reply handles casual confirmations.
Three things to avoid. Don't start with "Hey beautiful" or other stock flirty openings. Yes-rate drops 6 points. Don't ask for scope you don't need right now. "Can we use this everywhere forever?" loses three-quarters of the casual yeses. Don't follow up more than once. Re-approach at day 7 if non-responsive; then stop.
Template 2. Public comment tag (32% yes-rate)
Use for: high-volume, lower-risk content. The yes is publicly auditable, because the comment stays on the post. That is easy for the creator and good evidence for the brand.
Why comment-based collection scales better than DM: Instagram's DM rate limits cap mass outreach at ~50 DMs/day per account before the account gets flagged. Comments have no such limit. At 200 rights requests a day, comments work and DMs do not. The trade-off: comments allow a little less personalisation than DMs. The asset reference is shorter.
One caveat: if the original post is sponsored content (the creator was paid by another brand), commenting publicly may surface the request to that brand and create awkward dynamics. Always check the creator's bio and recent posts for "ad" or "partnership" tags before public-comment outreach.
Template 3. Email (41% yes-rate)
Use for: high-value content where the scope is bigger than a single PDP. Paid ads, email creative, retail signage, multi-quarter campaigns. Email gets the highest yes-rate because it carries real context. Creators need that context before agreeing to serious commercial use.
Why email outperforms DM by 17 points on yes-rate for high-value content: the creator has time to read the offer properly, scope is laid out unambiguously, the compensation makes the commercial nature explicit (which removes any "am I being scammed?" hesitation), and the consent mechanism is professional in a way that matches the size of the ask. The trade-off: email reaches creators 60% of the time, when their Instagram-listed email is current. DM reaches them every time. Use email for the wins where the substance justifies the friction.
The one-tap consent link: the single biggest workflow lever
Across every channel, one change lifts yes-rate most. Replace "reply YES" with a one-tap consent form link. The form fits on one screen. The creator's name is filled in, scope boxes are pre-checked, and a big "I consent" button sits at the bottom. Tap once, signed, audit-logged.
The mechanism is simple. "Reply YES" makes the creator type a reply, and typing is friction. The one-tap form requires zero typing, zero decision-making, completes in 4 seconds. A consent form removes that friction. Few single changes in a rights workflow pay off more.
A working consent form meets five requirements. (1) The creator's handle auto-fills from the request URL. (2) The content thumbnail shows inline, so the creator sees what they consent to. (3) Scope boxes are pre-checked at the brand's default and clearly editable. (4) The confirmation email includes a revocation link. (5) The form posts to an audit-trail database as well as an email inbox. Most modern UGC platforms ship this as a feature. If yours doesn't, build it. No rights infrastructure returns more.
Tracking and storing consent: the audit-trail standard
Every rights record must be timestamped and tied to a specific piece of content. It must be retrievable on demand. Retrieval matters more than most brands assume. A GDPR data subject request gives you 30 days. In that time you must surface every piece of personal data you hold on the creator. Say the record lives in a Notion database on someone's laptop, indexed by post URL. You'll miss the SLA.
Operational requirements for an audit-trail-grade rights database:
- Indexed by both creator handle AND content URL so a GDPR request can be served from either entry point.
- Timestamped consent capture with the verbatim text or screenshot of the creator's yes. A boolean flag alone is not enough.
- Scope record per consent: which surfaces, which duration, which compensation, all stored alongside the yes.
- Withdrawal log alongside the consent log: if a creator revokes, the record stays as "consented then revoked," not deleted.
- Cross-reference to every published use so a withdrawal can trigger automated takedown from every surface within the GDPR 30-day window.
Manual rights tracking scales to ~50 pieces/month per FTE. Above that, automated tooling is essential, the audit-trail requirements above don't fit in a spreadsheet at volume. Growing brands usually hit that ceiling sooner than they expect once a structured UGC programme is running.
The brands with a 60%+ yes-rate are faster, more specific and easier to consent to. Fix the workflow before the wording.
What to do when permission is denied
Two scenarios:
Explicit denial up front. Creator replies "no thanks" or "please don't use it." Don't push. Log the denial in the database, so nobody re-approaches the creator automatically. Remove cached copies from internal moodboards, and move on. Pushing back triples the probability of a public callout that damages the brand's wider rights-acquisition reputation.
Revocation after initial consent. Creator changes their mind, sometimes years later. Treat as a GDPR right-to-erasure event. Remove from every surface (PDP, gallery, email creative, paid ad cache, retail signage) within the 30-day GDPR-compliant window. Include CDN cache purges, the most-missed step. Flag email-creative variants and any B-roll reuse. Log the revocation date and creator confirmation that the takedown was acceptable.
A working rights system flags every consented piece "consented but revocable". It links the consent record to an automated takedown. When the creator revokes, the system fires takedowns to every surface that holds the asset. Then it confirms back to the creator. Manual revocation handling is the riskiest failure in UGC operations. The 30-day GDPR SLA isn't negotiable. Missed revocations are how brands earn ICO investigations.
Edge cases, kids, public figures, and copyright music
Three categories where standard consent isn't enough:
Content featuring children under 13 (or under 16 in some EU member states) requires parental consent. The creator's consent does not cover it. Say a parent posts a photo of their child. The parent's consent covers the parent's likeness. It may not cover the child's. The safe default: send content with identifiable minors through a separate consent workflow. It records the parent's relationship and explicit consent for the child's likeness. Detail in GDPR + UGC compliance.
Public-figure UGC (a creator the brand wants to feature is also a celebrity, athlete, or contracted public personality) carries additional rights overhead. The creator may consent personally. Their management, agency or sports federation may still hold the commercial rights. Before proceeding, always ask: "Do you hold the commercial rights to this image, or does an agent or federation?"
Copyrighted music in the UGC clip is the most-missed compliance gap on shoppable video. The creator may own their image. The music in the background is someone else's. A TikTok clip with licensed music is fine on TikTok, which holds the platform licence. Rehost the same clip on your PDP, and it infringes copyright. Either strip the audio, replace with cleared music, or licence the track separately. Detail in copyright fair use in UGC.
Putting it together: the full operational workflow
What the working rights workflow looks like end-to-end on a programme above 100 pieces/month:
- 1Inbound monitoring flags new tagged content within 1 hour of posting (hashtag stream + branded mention listening). Detail in ingestion stage of the UGC pipeline.
- 2Auto-triage scores each piece against the moderation rules (brand-safe? rights-eligible? creator-publicly-tagged?) and routes the eligible ones to the rights queue.
- 3Automated outreach fires the appropriate template (DM, comment, or email, selected by content scope) within 24 hours of the post going up.
- 4Consent capture via one-tap form. Audit log writes consent record indexed by creator + content URL + scope + timestamp.
- 5Auto-tag for production use: consented assets become available in the brand's UGC library, tagged for SKU, scope and creator credit.
- 6Revocation watcher monitors a creator's account for content deletion or revocation messages; fires automated takedowns within the 30-day SLA when triggered.
Brands running this workflow hit 50-60% yes-rates and process 500-2000 pieces/month with one part-time ops person. Brands running manual outreach from a shared inbox hit 15-25% yes-rates. They also start missing the 30-day GDPR window on revocations. Automation pays back at ~30 pieces a month. Most brands feel rights pain well above that. Detail on platform economics in the build-vs-buy analysis.
Closing
Rights collection is the unglamorous core of UGC operations. Run it as a system: templates, timing, channel fit, one-tap consent, audit-trail storage and automated revocation. Without the system, legal risk grows faster than inventory. When the ICO investigates, the person named on the privacy page carries most of it.
The good news: rights collection scales with one operator and the right tooling. With same-day requests, one-tap consent and an automatic audit trail, volume stops being a headcount problem. The shape of the work between here and there is template fit, timing discipline, and the one-tap consent infrastructure.
Foundational context on UGC programmes in what is UGC in ecommerce; the broader operational framework in the strategy framework; the regulatory overlay in GDPR + UGC compliance.
FAQs
Is liking or commenting on a customer's post the same as getting permission to use it?
No. A like, a retweet, or a "thanks for tagging us!" comment doesn't count as consent. Valid permission needs an unambiguous yes from the named creator, tied to specific content. Its scope and duration are documented, so you can produce them if challenged.
How quickly should a brand ask for UGC rights after a customer posts?
Within 24 hours. Yes-rate roughly halves by day 7 and drops 80% by day 30. Timing matters more than polish. Brands running same-day or next-day outreach consistently outperform those working through a weekly batch.
Which channel gets the highest yes-rate when asking for permission to repost UGC?
It depends on the size of the ask. Instagram or TikTok DM suits smaller requests like website use (24% yes-rate). Public comments work for high-volume, lower-risk content (32%). Email does best for full commercial scope like paid ads or signage (41%).
What is a one-tap consent form and why does it improve yes-rates?
It's a one-screen form that replaces a typed "reply YES" with one button. The creator's name auto-fills and usage scope is pre-checked. A tap logs a timestamped, auditable consent record. Swap a reply-based ask for this form, and yes-rate rises 9-12 points on the same template.
How long do you have to remove content if a creator withdraws consent?
Treat it as a right-to-erasure request. Take the content down within 30 days from every surface: product pages, galleries, email, paid ad caches and signage. Missing that window is a common way brands end up facing a regulator investigation.
Sources & notes
- 1GDPR, Article 6 lawful basis + Article 7 consent · Commercial reuse of identifiable content requires documented lawful basis. Consent must be freely given, specific, informed and unambiguous (Article 7).
- 2GDPR, Article 17 right to erasure · Withdrawal of consent must be honoured. EU/UK regulator guidance treats 30 days as the operational SLA for takedown from all surfaces.
- 3FTC Endorsement Guides · Material connection between brand and creator must be disclosed clearly and conspicuously. Brand and creator are both liable for disclosure failures.
- 4ASA / CAP, Recognising ads on social media (UK) · UK influencer ad-disclosure requirements. #ad must be clearly visible; "thanks for the gift" or similar implicit disclosures are insufficient.
- 5Methodology note · Yes-rate figures in this piece are illustrative. They are not measured Idukki data. Measure your own by channel and timing before setting targets.
- 6Idukki: the best UGC rights management tools in 2026 · Software to send requests and keep the records.
Continue reading
8 pieces in this clusterThese long-form pieces on the Idukki blog link back to this article, go deeper on the cluster.
- Buyer's guides
The best UGC rights management tools in 2026: five tools and what each records
Flowbox, Taggbox, EmbedSocial, Foursixty and Idukki compared. How each asks creators, what it stores and which plan carries rights. We make Idukki.
- Strategy
A 30-Day UGC Operating System for a Team of One
A week-by-week plan for running a UGC programme solo. What to collect, clear, publish and measure, one week at a time. No agency, no new headcount.
- Shoppable video
Repurposing customer support videos and unboxings as marketing assets
Support teams and customers already make the videos a product page is missing: assembly walkthroughs, fit checks, what is in the box. Who owns each kind, what consent you need, how to clean a clip for the PDP, and a monthly workflow that moves the good ones from the help desk to the storefront.
- Strategy
A kitchen table in Egham, why I built Idukki
Day job: SAP architect on UK government software. Night job: founder of a UGC platform. The Venn diagram of those two communities is roughly one person.
- Strategy
UGC Strategy Framework: The 6-Step Playbook for 2026
Define the goal, pick a content type, source a pipeline, secure rights, distribute, measure. The sequence that works, step by step.
- AI search
How to Measure UGC ROI: Formula, Attribution, Templates
Incremental revenue minus fully-loaded cost, over cost. Holdout testing for attribution. The KPI stack, the reporting cadence, and the pitfalls that inflate the number.
- Shoppable video
Shoppable Video for Furniture & Home Goods: Buyer Behaviour
Furniture is a strong fit for shoppable video. Scale and texture are what a static image cannot show.
- Strategy
UGC for Luxury Brands: Authenticity Meets Brand Equity
Curatorial UGC, member-only galleries, anti-cheapening guardrails. Why the mass-market UGC playbook does not translate to luxury, and what does.
More from Rohin Aggarwal
- Rights and compliance
The UGC rights workflow merchants will wish they had built (and what to do now)
A defensible UGC rights workflow automates detection, outreach and the audit trail, and needs six clauses to hold up. Build it before agents surface your UGC.
- Rights and compliance
Instagram UGC rights requests: two messages, a consent page and the proof to keep
Copy-ready templates for a public comment, a DM and a consent page. Plus what to store as proof and what to do when the answer is no.
- Rights and compliance
GDPR + UGC Compliance: The Operational Manual for 2026
GDPR treats reused customer content as personal-data processing. You need consent per asset, a searchable audit trail and a 30-day withdrawal SLA.