The short answer
Ask the moment the deal closes — the day the contact moves to your Closed stage in Follow Up Boss — by text, with a one-tap link to your Google review form, and ask every client. Follow Up Boss tracks the stage change but has no review request of its own. ReviewNudger connects with the account owner's API key, listens for contacts entering the stages you pick (anything named like "Closed" by default), and sends one neutral request automatically.
Why agents with hundreds of closings have dozens of reviews
Closing day is the most grateful a client will ever be, and it is also the busiest day of the transaction for the agent. The review ask becomes a mental note — "I should text them next week" — and next week the client is unpacking boxes and the moment is gone. Agents who ask at closing, every time, build review pages that buyers actually read; agents who mean to ask end up with a fraction of their closings reflected on Google.
Follow Up Boss is where the relationship lives: the person, their email and mobile, and the stage that says the deal is done. It has no review-request feature, and the stage change is exactly the event that should trigger one. That is the hook ReviewNudger uses.
How the closed-stage trigger works
The account owner pastes their Follow Up Boss API key into ReviewNudger (Follow Up Boss only lets the owner register webhooks, which is why it has to be that key). ReviewNudger reads your stage list, preselects every stage named like "Closed", and lets you tick others — Sold, Past Client, whatever your team uses — then registers one stage-change webhook on your account.
When a contact moves into one of those stages, ReviewNudger reads the person — a valid primary email, and the mobile number first if there is one — applies your sending rules, and after the delay you choose sends one neutral review request by text or email with a one-tap link to your Google review form. Stage changes into other stages are ignored; a bulk re-stage of your whole database is recognized and skipped rather than texting everyone; a stage change older than a week is treated as history. Each closing asks once, and a client who closes again years later is a new event your cooldown governs.
Every closed client gets the same ask. Picking only the clients you expect to be effusive is review gating — against Google policy and the FTC consumer-review rule — and the public Google link is always on the landing page.
Teams, renamed stages, and both sides of a deal
The trigger follows your stage names, not ours, so a team that renamed Closed to "Sold — Funded" just ticks that stage at connect time. Buyers and sellers are both contacts, so both sides of a deal can be asked if both move to a chosen stage; a contact with no usable email or phone is recorded and skipped, and the connection panel shows how many.
Frequently asked questions
Why does it have to be the account owner’s API key?
Follow Up Boss only allows the account owner to register webhooks, and ReviewNudger registers one stage-change webhook on your account. An agent's or admin's key is refused at connect time with that explanation, rather than failing silently later.
Our team renamed the stages. Which ones trigger a request?
Whichever you tick. ReviewNudger reads your live stage list at connect time, preselects stages whose name contains "closed", and stores the ones you choose. Change them by reconnecting.
Will a bulk stage cleanup text our whole database?
No. A stage-change event naming a large batch of people is recognized as a bulk re-stage and recorded as skipped, and stage changes older than a week at delivery are treated as history rather than asked.
Does it write anything back to Follow Up Boss?
No. It registers one webhook and reads people; it never changes stages, notes, or contacts. Disconnecting removes the webhook.