When a party leaves in Tock, Reviewflowz asks the guest for a review and credits it to the server named on the reservation. Setup takes one email from your Tock Account Owner. See the Tock integration.
How it works
Your team closes the table in Tock, and the party shows as left.
Tock sends us the visit, and the guest becomes a contact in Reviewflowz.
The request goes out after your delay.
Their review is matched to the visit and credited to their server.
What triggers a request
Trigger | When it fires | Good for |
Party left (on by default) | The table is closed in Tock | Teams that close tables in Tock |
Party seated | The party is seated | Teams that don't close tables: set the delay in the request |
Each trigger reads Reservations only or Reservations and walk-ins, and + Add a trigger adds another. Each one sends to its own request: Juniper Table Group's Party left sends to "Tock party left". A visit is asked once, whichever comes first, and a returning guest isn't asked again by the same request. Cancelled, no-show and transferred parties are never asked.
From each visit we take the guest's name, email and phone, the business and the server. The guest who dined is asked, not whoever booked for them, and a guest with no email or phone isn't asked. In the EU, EEA and UK, we ask only guests who opted into your marketing emails in Tock.
Connect Tock
In Reviewflowz, open Integrations, go to Automate review requests > Connect another integration and click the Tock card. Finish connecting Tock shows the email that switches the connection on, with your Endpoint URL and Auth header already in it.
From your Tock Account Owner's address, the one listed on your Tock Dashboard's Team page, send that email to [email protected]. Click Click to copy, or Open in my email app. Tock switches on webhooks for Premium and Premium Unlimited plans; [email protected] confirms yours.
Tock turns the webhooks on within a few days. You can leave the page in the meantime. As soon as Tock sends its first visit, the badge turns Connected. Your guests are asked once you turn the request on.
Turn off Tock's own review request
Tock asks for a review after each visit too, so your guests would be asked twice. In Tock, open each experience, then Post-Visit Communications, and switch off "Request a review for this experience". Your thank-you email can stay on.
Link your businesses to locations
Link each Tock business to the Reviewflowz location whose review page its guests should see. A business appears under Businesses after its first visit. Juniper Table Group links Juniper Evanston and Juniper River North to their own locations. With one location, or an account that isn't set up by location, there's nothing to link: every business's guests are asked.
Set up the request
Timing. Juniper emails 120 minutes after the party leaves. Delays go up to 7 days, with up to 3 messages, and follow-ups stop once a guest clicks, reviews or unsubscribes.
Channel. Email, SMS or WhatsApp, one per request.
Message. The From name is "Juniper Table Group", the Subject "Thanks for dining with us, {{first_name}}" and the Button text "Review us on Google". Fatima reads "Thanks for dining with us, Fatima". Try yours with Send myself a test.
Direct reviews to. Smart routing shows one button and picks the site per guest for your objectives. Juniper's is "Get as many reviews as possible" on Google. Show all options on the email gives each site its own button, on email only.
Turn it on
Open the request from Sends to, write your message and click Turn requests on. A guest is asked when their party leaves (or is seated) after you've connected, linked their business, switched the trigger on and turned requests on. Earlier parties aren't asked. A visit that reaches us more than 7 days later is recorded, never asked about.
When a reservation is cancelled
If a visit is cancelled, marked a no-show or transferred, its unsent request is withdrawn. The guest's next visit brings it back. A message already sent can't be pulled back.
See what it brings back
The Requests page counts Contacts, Requests, Clicked CTA, Matched and Stopped. Rosa Harlow's Google review of Juniper River North is credited to Theo Grant, the server on the reservation. A reservation naming two servers credits both. The Team Attribution Leaderboard ranks your servers, and the CRM Integration widget tracks requests, links clicked and reviews matched.
Good to know
The Webhook card shows the last update from Tock, the updates received and the time from which visits get a request.
URL shared by mistake? Click Get a new URL and email the new one to Tock. The old one keeps working until Tock switches over.
If nothing arrives from Tock for a week, a banner asks you to check with Tock that the webhook is still on.
Only the teammate who connected Tock can change its settings.
Disconnect stops asking your Tock guests and cancels the requests that haven't gone out. Your contacts, requests, business links and triggers are kept, and Reconnect picks up from new visits.
Nothing is written back to Tock, and notes, dietary details and payments are never stored.