How to build a rights-request email sequence people actually reply to
Most rights requests are a single generic email that gets ignored. A three-touch sequence with fast timing, specific subject lines and the right offer turns a trickle of replies into a real pipeline.
A customer posts a photo of your jacket on Tuesday. Someone on your team spots it the next Monday and sends a long permission email. It reads like legal wrote it, and nobody replies. A short sequence, sent fast, gets the photo cleared.
In this article
Why the one-shot ask underperforms
Most brands treat a rights request as an afterthought bolted onto tagging. A customer posts and someone spots it. A template email goes out asking permission to reuse it, and everyone waits. The email explains the request at length and sounds like legal wrote it. It asks for a broad grant of rights the customer has no context for. People reply when they still remember posting. They reply when the ask is quick and specific. And they reply when they know what happens to the photo if they say yes.
Timing: send it while the moment is still warm
The rights ask should go out within a day or two of the post being flagged. Do not wait for the queue to reach it. Wait a week and the customer has moved on. The photo that felt exciting on Tuesday is forgotten by the next Monday. A request about it now reads as spam from a brand they vaguely remember. A fast first touch also lands the follow-ups while the customer still plausibly cares.
The sequence: three touches, spaced out
- 1Day 0-1, "the ask": send within 24-48 hours of the flag. The subject line names the product and the platform, e.g. "Loved your [Product] photo on Instagram, mind if we use it?" Keep the body to two sentences: what you saw, what you’d like to do with it, and a one-tap yes.
- 2Day 4-5, "the reason": if there’s no reply, resend with a different angle. Do not send the same email twice. This time lead with where it would appear: "on the [Product] page, credited to your handle". Concrete detail moves people who ignored a vague first ask.
- 3Day 9-10, "the last call": a short, low-pressure close. State plainly that this is the final follow-up and that no reply is treated as a no. This clears the queue instead of leaving requests open indefinitely, and a hard close occasionally prompts the reply that two soft ones didn’t.
The three-touch cadence
- 01
Day 0-1: the ask
Fast and specific: name the exact post and platform. One-tap yes.
Within 48 hours
- 02
Day 4-5: the reason
For non-repliers: a different angle, leading with exactly where the photo will appear and who gets credited.
Second touch
- 03
Day 9-10: the last call
Short and final. States plainly that no reply means no, which clears the queue either way.
Sequence closes
Subject lines that get opened
- Name the product and the platform: "Your [Product] photo on TikTok, can we feature it?" beats "Content usage request."
- Ask a question. A policy statement gets no reply. A question invites a one-word reply; a statement invites nothing.
- Skip the brand voice for this one email. Warmth reads as human; a marketing register reads as a company.
- Never lead with the legal ask ("grant of rights," "license"). Lead with the compliment, put the mechanics in the body.
What to offer: credit vs a discount code
Two offers dominate rights-request emails, and they don’t work equally well on everyone. A feature-and-credit offer flatters the customer and costs nothing to fulfil. Your photo, on our product page, with your handle attached. It tends to beat a discount code with customers who have some following. It also wins with people who post for the recognition. A discount code works better with a customer who has no interest in being featured. They will trade a photo they already took for a modest saving next time. One offer for everyone pushes the people who don’t want it to ignore the email. Segment by one question: does the customer have a public handle worth crediting?
Which offer to lead with
Start here
Does the customer have a public handle worth crediting?
- Yes
Lead with feature + credit
Their photo on your product page, with their handle attached. It costs nothing to fulfil.
- Repeat, higher-value customer: Add one line offering a small code as well.
- No, or a private account
Lead with a small discount code
They trade a photo they already took for a saving on the next order.
- The ask feels transactional: Keep the wording warm so it does not read as buying rights.
| Offer | Works best with | Watch out for |
|---|---|---|
| Feature + credit | Customers with a public handle, or who post for the recognition | Feels hollow to a customer who wasn’t posting to be seen |
| Small discount code | Customers with no interest in a feature, or private accounts | Can read as buying the rights if the ask feels transactional |
| Both, offered together | Higher-value repeat customers worth the extra line of copy | Keep it to one added sentence, not a menu |
Make the yes as small as possible
Every extra step between "interested" and "done" loses replies. A multi-field consent form with a signature box loses people who would have texted yes. The best-performing pattern is a single word. Reply YES, or tap one button. The system records the grant, timestamps it, and moves the post into the reusable pool. Put the fuller terms in one plain line inside the email. Say where content can appear, for how long, and whether paid use is covered. Keep them out of a separate form.
What not to ask for in the first email
- Don’t ask for paid-usage or ad rights in the same breath as a simple feature request. That’s a separate, bigger ask that belongs in its own conversation once the relationship exists.
- Don’t ask for every platform at once ("Instagram, TikTok, and any future use") when the post only exists on one. Scope the ask to what you actually saw.
- Don’t make the first email longer than four sentences. Length signals effort on your side and reads as a chore on theirs.
FAQs
How long should a rights-request sequence run?
Ten to twelve days from the first touch covers most of the value. Replies drop off sharply after the second follow-up, and a sequence dragging on past two weeks mostly annoys people who’ve already decided not to reply.
Should the rights request come from a real person or the brand account?
A named sender, a real person’s name, even if the inbox is shared, consistently reads as less like spam than a no-reply brand address. It’s the same principle behind why a specific subject line beats a generic one.
What if the customer never replies?
Treat silence after the final touch as a no and leave the content out of the reusable pool. Chasing past the close either gets ignored again or earns a complaint, and neither is worth it for one photo.
Continue reading
2 pieces in this clusterThese long-form pieces on the Idukki blog link back to this article, go deeper on the cluster.
- Strategy
BFCM 2027: a 12-month plan that starts in January
Black Friday 2027 is 26 November. Plan the customer content your product pages need by then, month by month. Start with this year's unboxings.
- 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.
More from Rohin Aggarwal
- Strategy
When a creator deletes the original post, what happens to your gallery
If your gallery embeds the live original, a deletion leaves a broken hole. If you hold your own copy and rights record, the licence and the tile both survive.
- Rights and compliance
Auditing creator content rights before they quietly expire
A usage-rights grant almost never lasts forever, even when nobody wrote a date down. Past a few dozen live agreements, tracking that in memory or a shared inbox stops working.
- Rights and compliance
Influencer whitelisting and paid-usage rights
Whitelisting means running paid ads through a creator's own handle. It performs hard, and a vague deal turns it into a rights minefield.