How it works
- 1Connect Tripleseat to ReviewNudger through an OAuth application a Tripleseat admin creates in your own account — no password sharing, no partner approval to wait on. Your leads, accounts, contacts, and events stay in Tripleseat; ReviewNudger only reads which events ended and who the contact was.
- 2ReviewNudger checks your venue every few minutes. When a Definite or Closed event's end time passes, it reads the event contact's email and phone, applies your sending rules, and can send one neutral Google review request by SMS or email after the delay you choose — the morning after the reception, or once the last guest has left.
- 3Each event asks once, however many bookings it holds or how often it is edited afterwards. Prospects, tentative holds, and lost events never trigger anything, and events that ended before you connected are never backfilled. Every send is tracked with delivery status, opt-outs, and review click-through.
Why a native connection beats middleware
The same four guarantees on every native integration — because they come from the platform, not the connector.
No middleware account or per-task fees
The connection runs directly between your account and ReviewNudger. There is no third-party automation account to maintain and no per-task metering on your review requests.
No manual field mapping
ReviewNudger already knows the provider's payload. Customer name, phone, and email resolve automatically — there are no field mappings to build or quietly break later.
Built-in duplicate protection
Every incoming event is deduplicated before any message goes out, so provider retries and replays can never double-text a customer.
Opt-out compliance handled
STOP replies and email unsubscribes are recorded per customer and honored automatically on every future trigger.
Set up the Tripleseat integration
- 1Start a ReviewNudger trial and finish the short signup.
- 2In Tripleseat, have an admin open Settings › Tripleseat API & Webhooks, create a new OAuth 2.0 client application named ReviewNudger with read access to events, contacts, sites, and rooms, and paste the ReviewNudger callback address as its Redirect URL.
- 3Copy the application's UID and Secret into ReviewNudger under Settings › Integrations › Tripleseat, then approve the connection on Tripleseat's screen. If your account has more than one venue, pick the one this ReviewNudger account is for.
- 4Let a real Definite event end to confirm the trigger end to end.
- 5Done. Each ended event can now start one automatic review request under your sending rules.
Related resources
Useful next steps for choosing a trigger, setting up the request, and putting the workflow into practice.
Frequently asked questions
Do I need a Zapier account to connect Tripleseat?
No. The Tripleseat integration is native: you connect it directly inside ReviewNudger, with no middleware account, no per-task automation fees, and no field mapping to maintain.
What exactly triggers a review request?
Each time a booked event ends in Tripleseat, ReviewNudger records the event and evaluates it against your per-location send delay, cooldown, contact, and channel rules. One matching event can create one review-request journey by SMS or email.
Can a retry or duplicate webhook double-text a customer?
No. Every incoming event is deduplicated before any message is sent, and each event can create at most one review request. Provider retries and replays collapse onto the same request instead of sending twice.
What about customers who opt out?
SMS recipients can reply STOP at any time and email recipients can unsubscribe. Opt-outs are recorded per customer and honored across every future Tripleseat-triggered event.
Do I need Tripleseat partner approval or a particular plan?
No. Any Tripleseat account with API access lets an admin create an OAuth 2.0 client application under Settings › Tripleseat API & Webhooks; that application is what ReviewNudger connects through, and only a Tripleseat customer admin can approve it. If you cannot find that settings screen, ask Tripleseat support to enable API access on your account.
Which events count, and who gets the request?
Events in Definite or Closed status whose end time has passed. The request goes to the event's primary contact using the email and mobile number on their Tripleseat contact record; events with no contact, or a contact with no email or phone, are recorded and skipped, and the connection panel shows how many. Prospects, tentative holds, and lost events are never asked.
We run several venues in one Tripleseat account. How does that work?
ReviewNudger asks after events at one venue per ReviewNudger account, because each venue has its own Google listing. When you connect, ReviewNudger lists the venues your authorization can see and you pick one; another venue means another ReviewNudger account, connected through the same Tripleseat application.
Questions before you start? Email support@reviewnudger.com and a human will answer.