A request can go to Review when RouteFlow cannot safely produce an automatic estimate from the configured customer-facing rules and information collected for that request.
When this applies
When an offering appears Auto-Quote capable but a particular caller/request is still routed for review, or when an offering is intentionally configured as Review.
What to do
- Confirm the offering is currently available and whether it is Auto-Quote, Review, or Not Offered
- Check whether the caller provided the required service/item, quantity, duration, location, or other customer-facing scope details
- Check whether the request falls within the configured supported bounds
- Remember that Review is a safe fallback and RouteFlow should not invent unsupported pricing
- If the same clearly supported request repeatedly goes to Review, collect the request details for support review
Expected result
You understand that Review protects estimate quality when a specific request does not meet safe automatic-pricing conditions
If you still need help
Ask Support to review the current account configuration and a representative request example
Contact RouteFlow Support if: A clearly supported request repeatedly goes to Review despite current configuration and complete required customer information
