After the gallery closes: how to turn a photo delivery into reviews

Sending the gallery is the halfway point. The other half of a delivery is what happens after the client opens the link: a private review, a testimonial you control, and a redirect to the public review site you actually want to rank on. Most proofing tools do one of the three. Whimsy does all three off the same delivery — without ever holding a copy of the files.

The three jobs that happen after the client opens the gallery

Walk through a real wedding delivery. The client opens the gallery, downloads the JPEGs, picks favourites. What now?

The three jobs are different people, different timing, and different control. A proofing gallery that is just a link to JPEGs only does job one if the sender remembers to ask, job two if the client bothers to reply, and job three if the client can be bothered to find your Google Business page on their own.

The five-tool proofing stack we covered in the gallery-collapse post does the upload and the proofing. The review and the testimonial and the Google redirect are a separate problem the gallery does not solve.

How Whimsy handles the post-delivery flow

Whimsy''s Delivery object is the same link the client opened for the proofing gallery. The post-delivery work is layered on top, in the same record, so nothing is duplicated.

1. The private review. The recipient posts comment, approved, or changes_requested against the delivery. Comments are capped at 2,000 characters. The sender sees a summary on the delivery card — status, decision timestamp, comment count, latest event — without opening a separate inbox. The decision is attached to the file set, not floating in a chat tool that will be deleted in two years.

2. The internal testimonial. Once the recipient has approved the delivery or downloaded the zip, Whimsy invites a testimonial: a 1–2,000 character note with an optional 1–5 star rating. The testimonial is yours, not a public review — it lives on your account, attached to the delivery, and you choose what to do with it. Most creators will move it to a Studio Showcase (the persistent portfolio), which is the bridge from "this delivery went well" to "this belongs on my public site."

3. The public review redirect. The sender configures externalReviewTarget per delivery: google_business_profile, facebook, testimonial_form, custom, or none. If it is google_business_profile, the sender drops in the URL of their Google Business write-a-review page. After the recipient submits the private testimonial, the public response includes a button to leave the public review. The recipient writes the review themselves on Google — Whimsy does not pre-fill or polish it, and we are honest about that. (A future Co-Thinker pass is planned to assist at this step, but it is not shipping in the redirect today.)

The three jobs share one event log per delivery, one token, one expiry. The client does not get three separate emails with three separate links to three separate products.

What this still doesn't do

• No automated follow-up cadence. Whimsy fires the post-delivery review invitation once, at the configured trigger (delivery_approved or download_all). A six-day nudge, a fourteen-day nudge, and a "did you forget?" reminder are a marketing automation problem we have not built. If you need a sequence, Mailchimp, ConvertKit, or HoneyBook''s drip campaigns are the right tool.
• No review gating. Whimsy does not filter the redirect — a recipient who rates the delivery 1 star still sees the public review link. We do not believe it is our job to hide your Google Business page from a disappointed client, but it is a real product call that some studios will want, and we are not pretending it is solved.
• No AI polish of the review text. The recipient writes the review; Whimsy passes the link. The planned Co-Thinker pass would help the recipient shape a clearer public review, but it is not shipped yet, and this post will not pretend it is.

When this is the right tool — and when it is not

The right tool if:

• You send 20+ deliveries a year and the post-delivery follow-up is starting to eat your evenings.
• You have a Google Business Profile and a real public-reviews strategy you are trying to grow.
• You already have a CRM (HoneyBook, Dubsado) and you do not want to move contracts and invoices.

The wrong tool if:

• You send 5 deliveries a year and a personalised email is more than enough.
• You do not have a public review site yet — the redirect has nowhere to point.
• Your post-delivery loop includes custom art, custom print orders, or hand-signed thank-you cards. Whimsy does not own the printed-product workflow.

The end-to-end picture

The full Whimsy delivery loop, top to bottom, is now:

1. Connect the clouds you already pay for.
2. Select a folder of final selects in your existing storage.
3. Send a branded, expiring link to the client (no copy of the files).
4. Receive the review — comments, approval, change requests.
5. Capture the testimonial — internal, controlled, ready to promote.
6. Route happy clients to your public review page — Google Business or wherever you rank.
7. Promote a 5-star testimonial to a Studio Showcase — your public portfolio, in the same cloud you already paid for.

The gallery, the backup, the cross-cloud transfer, the review, the testimonial, the public-review redirect, and the showcase are now the same workflow. That is the point of a unified file hub — and it is the part of the stack that the proofing-zoo never gave you, because the proofing-zoo was five separate products that did not know about each other.

Whimsy is in free early access at whimsy.numeracode.com. Send the gallery, collect the private review, capture the testimonial, and route the happy client to your public review page — all from the same delivery, all in the cloud you already pay for.