ReviewPro Feature

S
Swiftspeed
Updated May 13, 20263 min read

The ReviewPro feature adds a fully functional, customisable smart review collection system to your Swiftspeed app. It collects customer feedback intelligently. Happy customers are routed to public review sites (Google, Yelp, App Store); unhappy customers land in your private inbox so you can fix the issue before it becomes a public complaint.

Like every Swiftspeed feature, you do not write any code. Add the feature, configure it from the editor, save. End-users see it immediately.

Adding the Feature to Your App

From your dashboard, open the app in the editor. In the top bar, click Features. Click Add a feature. Search for ReviewPro. Click Add. The feature appears in your app's tab bar or menu, and the editor takes you straight to its configuration page.

To configure later, return to Features and click the ReviewPro card.

How It Works

End-users see a simple rating prompt inside your app (1 to 5 stars). The flow branches based on rating:

  • 4 or 5 stars: customer sees "Glad you love it! Mind sharing on Google?" with a one-tap link to your review platform of choice.
  • 1 to 3 stars: customer sees "What can we improve?" with a private text-message form that lands in your ReviewPro inbox. No public review prompt.

This intercepts unhappy reviews before they reach a public board, while still channelling positive sentiment to where it matters for your business.

Setup

Configure your review destinations: Google Business URL, Yelp URL, App Store ID, Play Store ID, custom URL. Tick which platforms to route happy customers to. The app picks the most relevant one based on the user's device (Apple users get App Store, Android users get Play Store, etc.).

Inbox

Negative feedback lands here with the customer's name (if available), their message, their rating, and the date. Reply inline to start a conversation, or mark as resolved. Filter by unread, unresolved, by date range.

Triggers

Decide when the rating prompt appears. Options: after a positive event in the app (order delivered, class completed, course finished), on session count (e.g. after the user's 5th session), after a manual button tap. Avoid asking for a review before the user has had a good experience.

Appearance

Style the rating prompt: theme, colors, button copy, optional logo. The default copy works for most businesses but you can localise.

Tips

  • The trigger matters more than the design. Asking after order delivery is gold; asking on app launch is annoying.
  • Reply to every negative inbox message within 24 hours. Most customers update their public review (or post one) after a personal reply.
  • Route iOS users to the App Store and Android users to Play Store. Cross-routing converts at half the rate.
  • Show the rating prompt at most once per user every 90 days unless they have a new positive trigger event in the meantime.