How to build a rights-request email sequence people actually reply to

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. 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.
2. 2Day 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. 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.

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.

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.

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.