Skip to content

Flow & Form Recipes

Recipes combine several FSRevs features around a real customer goal. Use them as a starting point, then adjust the wording, locations, destinations, consent practices, and follow-up to fit your business.

Start with a Permission-First Review Request

Section titled “Start with a Permission-First Review Request”

Asking for a Review gives your frontline team a short spoken prompt, then walks through selecting the customer, checking request history, and sending the right Review Flow.

This is a good first recipe when you already have:

  • An enabled Review Flow
  • The correct Google or other review links in My Links
  • A team member with Send requests
  • Permission to contact the customer by the chosen channel

Connect a Review Flow’s Completion destination to a Custom Form, then send the customer to a useful thank-you page after submission. Start with Customer Journeys and Followup Destinations.

Track the Employee Connected to an Experience

Section titled “Track the Employee Connected to an Experience”

Enable team-member attribution in the Review Flow, assign Employee tracking only to the people who should appear, and make the employee choice as accurate and low-friction as possible. Start with Review Flow Settings and Roles & Permissions.

Add the appropriate review destinations in My Links, include them in the Review Flow, and test every route. Do not include Yelp as a solicited review destination. Start with Managing Your Links and Creating a Review Flow.

Collect Private Feedback for Manager Follow-Up

Section titled “Collect Private Feedback for Manager Follow-Up”

Configure the Review Flow to collect written feedback, set eligible manager notifications, then use Manager Feedback to work the Needs Response queue. Start with Review Flow Settings, Notifications, and Manager Feedback.

For any recipe:

  1. Decide the customer outcome before choosing fields and destinations.
  2. Use the shortest experience that gathers the information you will actually use.
  3. Confirm contact consent and choose an appropriate delivery channel.
  4. Test every meaningful branch with your team.
  5. Review the underlying activity and report data before changing the workflow.