Reviews page
The reviews page is the bridge between a 5-star private rating and a public review on Google / Yotpo / TrustPilot / a custom URL. Customers land here after submitting a 5-star feedback rating — they keep their identity token, so no re-authentication is required.
URL: {brand}.actii.me/{outlet}/reviews?t=... — the brand subdomain plus the outlet code.
What customers see
A short page with:
- A reflection of what they just rated (“You rated us 5 stars — thank you!”)
- The platform you’ve configured for this workspace
- A pre-filled review draft using their comment text (if any)
- A single button: Open in
{platform}— deep-link to the external review surface
The customer never leaves Active Reach until they tap the button. If they close the tab, the review request is saved against their contact record and surfaced on future visits.
Configuring the destination
Go to /dashboard/[ws]/feedback/settings → Review platforms.
| Platform | Configuration required |
|---|---|
| Google Business Profile | Connect via OAuth — the page-builder deep-link uses your verified place ID |
| Yotpo | API key + store ID |
| TrustPilot | Business unit ID |
| Custom URL | Any URL — Active Reach appends the customer’s review text as a query param if the destination supports it |
Reviews configuration is Shape B (per-row scoped) — different outlets can route to different platforms, or the org default can apply across all of them.
Why the review-platform connections themselves stay brand-tier
The connections (Google Business Profile OAuth, Yotpo API key, TrustPilot business unit) are registered once per brand, not per outlet. Two constraints force this shape:
- Provider model. Google Business Profile authorises a place ID via the brand’s OAuth account; Yotpo and TrustPilot key the API credentials to a brand-level store. There is no “per-outlet sub-account” model on these platforms that we could map into.
- DPDP / consent. A customer who consented to be routed to a public review surface gave that consent against the brand identity they saw on the bill. Forking the consent ledger per outlet would create per-outlet review identities the customer never agreed to.
Outlet-tier behaviour you do get: customer landing pages still embed the outlet code ({brand}.actii.me/{outlet}/reviews?t=...), per-outlet analytics roll up under each platform, and the reviews admin pages respect the chip strip’s outlet narrowing so you can read filtered aggregates.
Multiple platforms
You can configure more than one. The customer is offered all configured platforms, ranked by:
- The customer’s tier (VIPs get the platform you’ve prioritised for high-trust reviewers)
- The order channel (a customer who ordered via WhatsApp is offered the platform you’ve tagged for chat-originating reviews)
- The platform’s response rate over the trailing 30 days (highest-converting first)
What’s tracked
Every visit to the reviews page records:
- Which platform was offered
- Whether the customer opened the external link
- (Where the platform’s API supports it) whether the review was actually posted
Aggregates show up in /dashboard/[ws]/feedback → Public reviews with platform-by-platform conversion.
What’s next
- Feedback page — the upstream surface
- External review platforms — operator-side configuration