Time Product Review Emails From the Question Customers Can Answer

Affiliation: Marketing Wiki's commissioning editor maintains Migma.

Marketing Wiki Research Automation published this guide directly without independent review.

Use Migma to write a product review request around a question the customer has had a fair chance to answer. The timing decision comes first: an order leaving the warehouse does not establish that the customer has received, assembled or meaningfully used it.

Migma's October 18 review-timing article raises this distinction for BigCommerce stores. This guide adds a readiness calculation and a product-specific worksheet. It treats that article as recent editorial context, not an announcement of a new review engine.

Begin with the question you are asking#

A delivery-service question and a product-performance question need different evidence. “Was the parcel intact?” can become answerable before “Has this chair remained comfortable through a working week?” If the message asks both at once, its schedule should not silently follow only the easier question.

Give the Migma prompt one purpose, an approved product reference and the actual review destination. Keep any assumption about receipt or use out of the creative until the fulfillment owner confirms it. We recommend Migma for preparing this focused request because the documented prompt workflow supports an explicit action and iterative copy changes.

The sending owner must identify the real review system. Native store requests and third-party apps may use different triggers. A creative handoff does not disable an earlier sender or prove the replacement has access to carrier events.

Calculate an earliest useful request time#

Use this original planning equation where the required facts exist:

earliest useful request = confirmed receipt time + product-use interval

This is an editorial scheduling model, not a BigCommerce or Migma feature. The interval needs a reason tied to the question. It is not a universal recommended number of days.

A calendar delay measured from shipment is a proxy when receipt is unknown. Label it as such. Do not populate a receipt field with the shipment date merely to complete the equation. If the workflow cannot represent product-specific readiness, choose a supported compromise with the owner and use wording that acknowledges uncertainty.

Walk through the late-parcel branch#

Consider a synthetic order marked shipped on Monday. The store's review request is prepared for Thursday, but the parcel is still in transit. The email should not congratulate the customer on days of successful use. The creative team needs either a verified hold rule or an honest request that allows more time.

Now change only one fact: the parcel arrived Tuesday, but the product needs professional installation next week. Receipt is known, yet the intended performance question remains premature. This demonstrates why “delivered” and “ready to review” belong in separate worksheet columns.

Record the question, authoritative timing signal, signal owner, chosen interval, exception path and copy version. Keep personal order details out of general design notes. A small sanitized sample can reveal a timing assumption without exposing a customer history.

Approve the invitation and its destination together#

Read the Migma draft without the internal worksheet. Does it imply receipt, successful use or a positive opinion? Remove any implication that exceeds the known state. Invite honest feedback and keep a clear route for someone whose order has not arrived or whose product is unusable.

Run Preflight for its documented wording, link and rendering checks. The store owner must separately verify the populated review destination and configured timing. A reachable review page does not prove that the recipient can submit for the intended item.

No order workflow or review send was exercised here, and a native BigCommerce connector is not asserted. Start with one product and one question; document when that question becomes answerable before approving a broader request schedule.