When an order is Completed in Popmenu, or a reservation or waitlist party is completed, Reviewflowz asks the guest for a review. The review that comes back is matched to that guest and their order or visit.
How it works
An order is Completed, or a reservation or waitlist party is completed, in Popmenu.
At the next hourly check, Reviewflowz reads it and its guest.
The request goes out after your delay.
The guest's review is matched to the order or visit and its location.
What triggers a request
Trigger | When it fires | Who is asked |
An order is Completed (online, catering or contactless dine-in) | The order's status is Completed in Popmenu | The guest on the order |
A reservation is completed | The reservation party is completed in Front of House | The guest on the reservation |
A waitlist party is completed | The waitlist party is completed in Front of House | The guest on the party |
All three are ticked from the moment you connect, and feed one request, Popmenu review requests. Untick any you don't want. The guest is asked using the name, email and phone they gave at checkout or on the reservation.
Orders relayed from DoorDash, Uber Eats or Grubhub are never asked. Your own online, catering and dine-in orders are. Guests aren't asked when the restaurant or the guest is in the EU, the UK or Switzerland.
Orders and visits from before you connected are imported so their reviews still match. Nobody is messaged for those.
Connect Popmenu
You connect with an API token you create in your Popmenu dashboard:
Developer API. The token lives under the Developer API, which Popmenu turns on for each restaurant. If Settings has no Developer API tile, ask Popmenu Support at [email protected] or 1-844-POPMENU to turn on the Developer API for your restaurant.
Who. A Popmenu dashboard user who manages API tokens creates it, signed in to a login that manages this restaurant only.
In Popmenu, open Settings, then Developer API. Under GraphQL API Tokens, press Add API Token. Name it Reviewflowz, set Expiry to Never, and save. Copy the token straight away: Popmenu shows it only once. Your other tokens keep working as they are.
In Reviewflowz, open Integrations, go to the Automate Review Requests tab and click the Popmenu card. If you already have an integration connected there, click Connect another integration first. Paste the token into API token and click Connect Popmenu. The connection shows your restaurant's name.
Link your Popmenu locations to your locations
Under Locations, give each Location in Popmenu the Reviewflowz location whose review profiles its guests should see. Saffron & Salt links Saffron & Salt Decatur, on Church Street, and Saffron & Salt Inman Park, on Edgewood Avenue NE, to their own locations. Orders and visits at a location you haven't linked use the one in Fall back to. If your Reviewflowz account has one location, every Popmenu location is linked to it for you when you connect. Opened a new location in Popmenu? Click Refresh list and link it.
Set up the request
Timing. An order counts from the time it was due, a reservation or waitlist party from when it was completed, and your delay comes on top. Saffron & Salt emails 3 hours later, then sends a reminder 3 days after that with the subject "How was your meal from Saffron & Salt, {{first_name}}?" and the button "Leave a review". Up to 3 messages, and follow-ups stop once a guest clicks, reviews or unsubscribes.
Channel. Email, SMS or WhatsApp, set per message.
Message. Saffron & Salt's From name is "Saffron & Salt", the Subject "Thanks for your order, {{first_name}}", which Marisol Vega reads as "Thanks for your order, Marisol", and the Button text "Review your order". Try yours with Send myself a test.
Direct reviews to. Smart routing gives one button, and your goal for reviews decides which site it opens. Saffron & Salt aims for as many Google and Yelp reviews as possible. Show all options on the email lists every site instead.
Turn it on
Open Popmenu review requests and click Turn requests on. The Syncing panel's Sending requests for orders and visits completed since shows the day you connected.
When an order or reservation is cancelled
If an order is Cancelled or Rejected within three days after it was due, or a reservation or waitlist party is cancelled, and its request hasn't gone out, the request is withdrawn.
See what it brings back
Every review is matched to the guest and the Popmenu order or visit it came from, at the location it belongs to. The Requests page counts Contacts, Requests, Clicked CTA, Matched and Stopped, and lists each guest with the state of their request. The CRM Integration widget under Reports > Dashboard tracks requests, links clicked and reviews matched from Popmenu.
Good to know
Keep the Reviewflowz token in Popmenu. If the card shows Reconnect needed, create a new token under Settings, then Developer API, with Expiry set to Never, and enter it with Enter new credentials. Your request and location links stay as they are.
If Reviewflowz says your token's login manages more than one restaurant, create the token signed in as a teammate who manages only this restaurant.
The Syncing panel counts guests who can't be asked, such as a guest with no email or phone. They're still kept, so a review from that guest is matched by name.
A second Popmenu restaurant connects on its own, and gets its own request, named after the restaurant.
Disconnect stops the checks and withdraws every request that hasn't gone out.
