Browse Guides
Move to another guide without going back to the documentation hub.
Manage Review Requests Without Guesswork
Open Settings -> Review Requests to adjust timing, reminders, thank-you flow, manual sends, and delivery checks. This guide keeps automation settings separate from email design, so it is clear where each change belongs.
What Merchants Usually Need to Know First
Automation Starts After Order Data Exists
If products and orders have not synced into Sabdov yet, request timing and reminder rules have nothing reliable to act on.
Delivery Logic and Email Copy Live in Different Places
Use Review Requests for send behavior and Email Templates for content, branding, and preview. Changing one does not automatically update the other.
What You Can Control Here
Follow This Sequence
Confirm products and recent orders are already synced
Open Integrations and verify the connected platform has completed at least one successful sync. Review request automation depends on order and product data being present before timing or reminder logic can do anything useful.
Set the initial request delay and reminder behavior
Open Review Requests and choose when the first request should be sent after purchase. Then review whether reminders are enabled, how many may go out, and how much time should pass before the next follow-up.
Review thank-you flow, rewards, and pause state
Still in Review Requests, confirm automation is not paused and check what should happen after the review is submitted. This is where merchants usually verify thank-you behavior, reward follow-up, and whether requests should stop temporarily.
Edit the email content separately in Email Templates
Open Email Templates when the message copy, button wording, brand styling, or preview output needs work. Keep in mind that updating the email design does not change request timing or reminder rules.
Verify history or manual-send context before contacting support
Before escalating, check whether the order qualifies for sending, whether the request window has already passed, and whether the customer has already submitted a review. Those checks usually explain why a request or reminder did not send.
Common Review Request Issues
| Error Message | Potential Cause | Resolution |
|---|---|---|
| No review request was sent | The order has not synced yet, the send delay has not elapsed, or automation is currently paused. | Confirm the integration has synced recent orders, review the request delay, and check whether Review Requests is paused before assuming delivery failed. |
| Reminder never triggered | The original request was never eligible, the customer already submitted a review, or the reminder window and reminder count no longer allow another follow-up. | Review the original request state first, then confirm reminder rules are still enabled for the current order and customer state. |
| Thank-you or reward email did not arrive | The post-review flow is disabled, the related template is inactive, or the submitted review did not meet the conditions that trigger the next step. | Check Review Requests for post-review behavior, then confirm the related email template and eligibility rules are aligned with the current setup. |
| Manual send is unavailable | The order, product, or customer context is incomplete inside Sabdov, or the record does not match the workflow the request tool expects. | Re-check the synced order data in Integrations and make sure the target customer and product are present before retrying a manual send. |
Need the next safe action?
Start with the request rules, separate email design from automation, and verify sync or order context before escalating delivery questions.
Was this helpful?