# Review then photo request sequence without spam

One customer, two jobs: stars and a photo. When to combine, when to sequence, and how to cap channels. We make Idukki.

By Rohin Aggarwal · 2026-10-31

Monday: stars please. Wednesday: got a photo? Friday: a SMS nudge. By Saturday she had muted the brand. The dress still looked good on her. The inbox did not.

**Quick answer**

- Stars and a photo are two jobs. Decide combine vs sequence before you write copy.
- Default: one ask per order. A second email needs a new reason.
- Cap channels. Email and SMS on the same order is how mute lists grow.
- Email #2 should thank, show what a useful photo looks like, and stop.
- We make Idukki. Our dual setup sends at most one of the two emails per order.

A review says how it went. A photo shows how it looks on a real person. Both help the next shopper. Stacked badly, both feel like noise.

_Figure: Two jobs, one customer. Illustration of a single order timeline._

## One customer, two jobs

Job one: a rating and a short verdict. Job two: a photo or clip of the product in use.

Job one is fast. Job two needs the product nearby and a moment of care. Treating them as one form works when the upload path is short.

Treating them as two campaigns needs hard caps. Without caps, every tool on the stack sends its own nudge.

## Combine vs sequence decision

**Combine the ask, or send two emails?**
Q: Can your form take stars and a photo in one visit?
- Yes, on mobile in under a minute: **Combine** — One email, one CTA, one upload page.
  - Photo field is optional: Lead with the photo ask in the headline
  - Buyers abandon after stars: Put the camera on the first screen
- No: stars live in another app: **Sequence with a hard stop** — One tool owns the first ask. The second email only goes if media is still missing.
  - They already left a photo review: Skip email #2
  - They ignored email #1: Do not add SMS the same week
- You already send both today: **Audit the stack** — List every post-purchase message for one order.
  - More than two asks: Cut to one job per order

> **Write the stop rule before the second subject line:** Skip email #2 for buyers who already uploaded, unsubscribed, returned, or left a photo.

## Quiet hours and channel caps

- **One channel per order by default.** Email or SMS. Avoid both in the same week.
- **Quiet hours.** Avoid late night in the buyer’s timezone.
- **Weekly cap.** A buyer with two orders still should not get four asks in four days.
- **Shared suppression.** Unsubscribes and “already uploaded” must sync across tools.

If Klaviyo, Shopify and a reviews app all fire, you do not have a sequence. You have a pile.

| Rule | Default | Exception |
| --- | --- | --- |
| Asks per order | 1 | A second email only if media is still missing |
| Channels in 7 days | 1 | SMS only with explicit opt-in for asks |
| Reminders | 0 or 1 | Never a third |
| Quiet hours | Local 21:00–08:00 | None for transactional receipts |

_Channel caps to put in writing. Adjust to your list health._

## What to say in email #2

Email #2 is not a louder version of email #1. It has a narrower job: a photo.

- Thank them if they already left stars.
- Show one example of a useful photo: product in use, daylight, no clutter.
- One button to the upload page.
- No guilt. No “last chance” urgency.
- A clear stop: this is the final ask for this order.

> **Show the photo you want:** A tiny example image in the email beats another paragraph about “sharing your experience”.

**Email #2 tone**
Spammy follow-up:
- We still have not heard from you
- Last chance for your discount
- Second SMS the same day
- No mention of what photo helps
Narrow photo ask:
- Thanks for the stars, if they left them
- One example of a useful photo
- Single upload button
- “This is our last ask for this order”
_Copy sketch. Not a measured test._

## Measurement

Track the sequence as a funnel. Separate campaign opens hide the real drop-offs.

1. Orders eligible for an ask.
2. Email #1 sent, opened, completed (stars and/or photo).
3. Email #2 sent only to the media-missing set.
4. Photos approved and shown on a product page.
5. Unsubscribes and spam complaints in the same window.

If complaints rise when #2 turns on, shorten the gap or drop #2 for that category.

## Idukki dual request setup

We make Idukki. You can set a review request and a photo and video request after Shopify orders. Details are in [the post-purchase help guide](/help/send-post-purchase-review-and-photo-requests).

One order gets one email at most. If one has gone, the other is skipped for that order. That is the spam brake built in.

**How Idukki keeps it to one email**
1. **Connect Shopify** — Orders feed the request settings.
2. **Pick review or photo** — Turn on the email that matches the job.
3. **Set the delay** — Days after the chosen order event.
4. **Preview and save** — Nothing sends until sending is approved.
_From the help guide. Early access on sending until your store is approved._

Stars in Judge.me and photos in Idukki still need one outbound ask per order. Import can move media later without a second nudge.

**Your next step:** List every post-purchase ask that can fire for one order this week. Cut until one job remains, or one combined form.

### Questions store owners ask

**Q: Is a second email always spam?**

A: No. It becomes spam when the job repeats, the gap is short, or another channel already asked.

**Q: Should SMS follow email #1 the next day?**

A: Only with opt-in, and only if email did not complete the job. Default to no.

**Q: Can Idukki send both emails for one order?**

A: No. One order gets one of the two emails at most.

**Q: What if my reviews app already asks for photos?**

A: Keep that as the single ask. Do not add a second photo email from another tool.

**Q: How long should I wait before email #2?**

A: Long enough that the buyer has used the product again. Often several days after #1, never the next morning.

### Sources
- [Idukki help: send post-purchase review and photo requests](/help/send-post-purchase-review-and-photo-requests) — One email per order; review and photo flows.
- [Idukki: collect UGC](/collect-ugc)
- [Idukki: why photo reviews outperform text reviews](/blog/why-photo-reviews-outperform-text-reviews)

---
Canonical: https://idukki.io/blog/review-then-photo-request-sequence-without-spam
Tags: reviews, photo-reviews, email, ugc, post-purchase, spam