Ask for feedback after the customer has had a fair chance to experience the product. A fixed delay from checkout can be inappropriate when production, delivery or a service appointment is still pending.
Identify the experience you want reviewed
Product use, delivery service and the buying process are different subjects. If you ask about the product before it arrives, the customer can only comment on expectations or communication.
State the subject clearly. A short request about the received item is more useful than a vague demand for a five-star rating.
Use an actual completion signal
Decide which record establishes that the relevant experience happened. For a parcel, that might involve a reliable delivery state and a reasonable opportunity to inspect the item. For a service, it may be completion rather than the booking date.
Do not assume every platform status is independently verified. If your workflow updates delivery manually, the review routine inherits that limitation.
Exclude unresolved exceptions
An order under investigation needs assistance, not an automatic rating request. Build a way to hold requests for unresolved non-delivery, cancellations or an incorrect item. That does not mean suppressing criticism; it means addressing the problem before sending an irrelevant message.
Keep the eventual feedback route open. A customer who experienced a problem should not become permanently ineligible to describe it.
Write a neutral request
Ask for an honest account of the product and make the next action clear. Avoid suggested praise, prefilled positive wording or pressure linked to support. Do not promise a reward that requires a favourable score.
An illustrative structure is: identify the order privately, ask whether the customer has used the item, invite genuine feedback and provide a support route for unresolved issues. Adapt it to the communication permission and channel you actually have.
Measure usefulness, not just response volume
Track whether requests reach the right stage, whether customers understand them and whether the resulting feedback answers future buyers' questions. A larger number of low-context ratings is not necessarily more useful.
Review a small sample of recent orders before automating. Record the rule, exceptions and owner. This guide does not assume a built-in review-request integration or permission to message every past customer.
Use the fulfilment and support hub to align the request with your real order process, then evaluate a tool against that process rather than adopting its default schedule unquestioned.
Illustrative case to check
One order is delivered, another is still being made and a third has an unresolved wrong-item complaint. A single “seven days after purchase” message would reach three different experiences. Review the actual states, hold the inappropriate requests and address the complaint. The rule should describe the experience being reviewed, with an exception path, rather than hiding dissatisfaction by excluding the customer forever.
Examples are illustrative. Confirm current features, charges and suitability before making a business decision.
Explore this topic → · Find an oBizee setup guide · Ask about your store