# 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.

By Rohin Aggarwal · 2026-08-24

**Quick answer**

- A single generic rights request sent right after a post is tagged gets ignored more often than not; the fix is a short sequence, not a better one-liner.
- Timing beats wording: the first ask should go out while the customer still remembers posting, and the whole sequence should close within ten to twelve days.
- What you offer matters. A feature-and-credit is usually a stronger pull than a discount code, but the two work for different customers.
- Fold consent into the reply itself (a one-tap yes or a single-word reply) so getting to yes doesn’t require the customer to fill out a form.

## Why the one-shot ask underperforms

Most brands treat a rights request as an afterthought bolted onto tagging: a customer posts, someone spots it, a template email goes out asking permission to reuse it, and everyone waits. The email usually explains the request at length, sounds like it came from legal, and asks for a broad grant of rights the customer has no context for. None of that is what makes someone reply. What makes someone reply is remembering the moment they posted and being asked quickly, specifically, and with a clear answer to 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, not whenever the queue gets to it. Wait a week and the customer has moved on: the photo that felt exciting to post on Tuesday is forgotten by the following Monday, and a request that references it now reads as spam from a brand they vaguely remember buying from. A fast first touch also keeps the follow-ups in the sequence landing inside a window where the customer still plausibly cares.

## The sequence: three touches, spaced out

1. Day 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.
2. Day 4-5, "the reason": if there’s no reply, resend with a different angle, not the same email again. This time lead with where the photo would appear ("on the [Product] page, credited to your handle"), because concreteness moves people who ignored a vague first ask.
3. Day 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**
1. **Day 0-1: the ask** — Fast and specific: name the exact post and platform. One-tap yes. (Within 48 hours)
2. **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)
3. **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, not a policy statement. 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 (your photo, on our product page, with your handle attached) flatters the customer and costs nothing to fulfil. It tends to outperform a discount code with customers who already have some following, or who post because they enjoy the recognition. A discount code works better with a customer who has no particular interest in being featured but will happily trade a photo they already took for a modest saving on their next order. Running one flavour of offer for every reply forces people who don’t want it into ignoring the email; segmenting by whether the customer has a public handle worth crediting is a cheap way to pick the right one.

| 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 |

_Which offer to lead with, and where it tends to fall flat._

## Make the yes as small as possible

Every extra step between "interested" and "done" loses replies. A link to a multi-field consent form with a signature box loses people who would have replied yes to a text message. The best-performing pattern is a single word: reply YES, or tap one button, and the system records the grant, timestamps it, and moves the post into the reusable pool. Save the fuller terms (where content can appear, for how long, whether it covers paid use) for a plain-language line inside the email itself, not a form the customer has to open separately.

> **A line worth stealing:** Reply YES and we'll feature your photo on the [Product] page with a credit to @[handle]. That's all we need.

## 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.

**Q: How long should a rights-request sequence run?**

A: 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.

**Q: Should the rights request come from a real person or the brand account?**

A: 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.

**Q: What if the customer never replies?**

A: 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.

**The pattern that actually moves reply rates:** Speed, specificity and a small ask beat a well-written policy email every time. Send fast, reference the exact post, offer something concrete, and make saying yes take one tap. The sequence does the rest.

---
Canonical: https://idukki.io/blog/rights-request-email-sequence-that-works
Tags: rights-management, ugc, email, strategy