More Good Reviews lifetime deal

Locations and requests are a shared account budget

One code costs $79 for twenty locations and five thousand requests per month. Each additional code adds twenty locations and another five thousand requests, up to five codes at $395 for one hundred locations and twenty-five thousand requests.

The allowance is not five thousand requests for each of twenty locations. A twenty-location account averaging two hundred fifty requests per location would already use the entire entry pool. If a sequence creates additional billable requests, follow-ups need room too; confirm the exact counter behavior in the account.

The current billing documentation says even an empty project counts as one location seat. A workspace full of unused client drafts can therefore consume capacity. Keep the project/location inventory aligned with the real customers rather than only counting sites currently sending campaigns.

Resolve the white-label inconsistency before selling access

The dedicated lifetime terms updated October 12, 2026 explicitly enable agency features at three or more redeemed codes. This agrees with the plan table, which includes white-label branding and unlimited agency team members from Plan 3. A marketplace FAQ still says five codes are needed, so the sources are not fully synchronized.

Plan 3 at $237 is the smallest agency tier supported by the dedicated terms. Before selling a fully branded client service, confirm that the desired login, domain and client-access functions are included. Do not buy five codes solely because of the conflicting FAQ if three codes cover the actual requirements.

The lifetime terms say codes cannot be redeemed while an active Stripe subscription controls the account. If a subscription is added after code redemption, the purchased request and location allowances are added to the subscription; when it ends, the account returns to the lifetime plan. Follow that lifetime-specific process rather than assuming the direct Business-to-Agency subscription migration rules are identical.

Trigger the request after a real customer event

Choose whether the process starts after signup or after a charge. The documentation says a charge trigger becomes available when the project has charge history. Without that data, the project normally uses signup dates. Connecting a billing source and importing charges are therefore functional prerequisites, not cosmetic setup.

Set an appropriate delay, request channel, reminders and stop conditions. Test with a consented internal sample before importing a customer list. Confirm that an existing reviewer or opted-out customer does not continue receiving unnecessary prompts.

Budget requests around the busiest month and actual follow-up behavior. A large location allowance does not help if one client’s campaign consumes the shared request pool. Review the usage page and decide who receives limit alerts before promising a monthly service level.

Separate the platform licence from delivery charges

Current official documentation says SMS uses your own provider connection. The licence therefore does not include unlimited free text-message delivery. Provider, destination-country, phone-number and messaging charges can remain outside the lifetime price.

Email sending also depends on correct domain configuration and customer permissions. Custom branding does not automatically establish deliverability. Verify a representative message, reply path and unsubscribe process before treating a connected domain as a completed campaign setup.

The founder says current features include AI and that future resource-intensive capabilities may offer BYOK or require a third-party account. Do not turn that into a promise of unlimited free model usage forever. Existing automation services used to supply customer events may also have their own task limits.

Request honest feedback without promising five-star outcomes

The marketing emphasizes getting more positive reviews and describes star-based routing. A request tool cannot determine whether a customer is happy or guarantee a rating. Design the process around an honest review opportunity and a useful feedback channel for every customer.

Google’s review policy prohibits discouraging negative reviews or selectively soliciting positive ones. Keep the public review opportunity available regardless of a customer’s sentiment. A private support route can help resolve a complaint without withholding the public review link from dissatisfied customers.

A customer still needs to complete the review on the third-party platform. The founder explains that collecting feedback on a hosted page does not automatically post a review to Google or Facebook on the customer’s behalf. Syncing existing reviews and drafting business replies are different functions.

AI-assisted replies should be checked for accuracy, especially when the review describes a service failure or contains personal information. A plausible apology is not evidence that the underlying issue was investigated. Start with approval of drafts before enabling automatic responses.

Current limits supersede old stacking answers

Older questions mention stacking as many as twenty-one codes. The current exact offer and founder FAQ limit new stacking to five. Historical answers should not be used to quote a larger new licence.

For more capacity, the dedicated terms say later subscriptions add to redeemed-code limits and the account returns to its code-based lifetime plan when the subscription ends. Additional capacity beyond five codes must use paid plans or add-ons. Confirm the lifetime-account quote; direct subscription per-location allocations are not automatically the same as the shared code allowances.

A Reddit thread raises concerns about the product’s availability. Public product pages alone do not establish the history of every account or guarantee service continuity.