Connect Follow Up Boss to Sendoso & Reviews [Updated 2026]
Most agents lose past clients not because the relationship soured but because nobody followed up. The deal closes, the commission hits, the next listing demands attention, and the family you just helped buy a home drifts into the cold-lead pile. Eighteen months later they sell with someone else — usually someone who simply stayed in touch. Past-client follow-up is the highest-ROI marketing a brokerage owns, and the first thing that breaks when a team gets busy.
This guide is for teams already running Follow Up Boss who want the closing event to trigger the follow-up automatically: a closing-day gift through Sendoso, a Google review request sequenced to land while the keys are still warm, and a long-tail nurture that keeps you top of mind until the next move. Repeat business is the foundation: according to the National Association of Realtors, roughly a third of sellers find their agent through a referral from a past client or friend. We will map the exact integration — which webhook fires the chain, what Sendoso sends, when the review ask goes out, and how to keep it from spamming people — plus a comparison of where Follow Up Boss wins on its own, a worked example, a decision checklist, and an honest section on when this is the wrong call.
TL;DR
Past-client follow-up automation connects three systems — your CRM (Follow Up Boss), a corporate gifting platform (Sendoso), and your review engine (Google Business Profile) — so that one event, a closed transaction, fires a coordinated sequence: gift, review request, and nurture. The integration is event-driven: when a Follow Up Boss deal moves to "Closed," a webhook triggers the downstream actions instead of an agent remembering to. Done right, it reclaims the referral and repeat business that 60–70% of agents leave on the table, and it does so without anyone touching a spreadsheet.
Repeat and referral clients can drive over 60% of an established agent's volume. That is the prize this workflow protects. The rest of this post is the build.
Who this is for
This integration earns its keep for a specific profile. You are a team or brokerage closing at least 40–50 transactions a year, running Follow Up Boss as your system of record, and you understand that your database — not Zillow — is your cheapest source of deals. You have a budget that can absorb a $25–$75 closing gift per client, and you want gifting and reviews to happen every time.
You are likely a team lead, an operations manager, or a solo agent who has outgrown manual follow-up. The pain you feel is specific: review counts that stall for months, past clients who "forgot" you, and a gifting program that exists in theory but fires for maybe one in five closings. The opportunity is real because people move often — according to the US Census Bureau's Current Population Survey, roughly 8% of Americans relocate each year, and every move is a transaction your past clients could route to you.
Red flags — skip this build if: you close fewer than 20 deals a year (the automation overhead outweighs the volume), you have no gifting budget at all (Sendoso has a per-send floor), or you are not yet on a real CRM and are tracking clients in a spreadsheet. Fix the foundation first; automating chaos just produces faster chaos.
The volume context matters. The market is large but not infinite: according to the NAR 2025 Annual Real Estate Report, US existing-home sales totaled 4.06M units in 2024. Most agents touch a tiny slice of that, which is exactly why retaining the clients you already won beats chasing strangers.
Why the closing event is the right trigger
Every reliable automation needs a clean trigger — a single, unambiguous moment that says "now." For past-client follow-up, that moment is the deal closing. When a deal record moves into a closed stage, Follow Up Boss emits a webhook carrying the contact, the property, and the deal value. That event is your starting gun.
The mistake teams make is triggering on the wrong thing — a calendar date, a manual tag, an agent's memory. All of those decay. The closing event does not: it happens once per client, carries the data you need, and is recorded whether or not anyone remembers to act on it. Anchoring the sequence to deal.stage_updated is the difference between a follow-up program that runs and one that lives in a "we should really do that" backlog.
Speed matters because attention is perishable. The window where a client is most willing to leave a review and most receptive to a gift is the first 7–10 days after closing. The first two weeks post-close capture the warmest review and referral window. Miss it and conversion drops sharply, which is why the trigger has to be automatic, not a Friday-afternoon task that slips.
| Trigger source | Fires every time? | Carries deal data? | Typical delay to first touch |
|---|---|---|---|
| Deal moved to "Closed" (webhook) | Yes (~100%) | Yes | 1–2 days |
| Calendar reminder | Partial (~60%) | No | 7–14 days |
| Manual tag by agent | No (~20%) | Sometimes | 14–30 days |
| Monthly batch review | No (~40%) | Yes | Up to 30 days |
The integration map
Here is the full chain at a glance. The Follow Up Boss closing event is the trigger; everything to its right is a downstream action with its own timing.
| Step | System | Trigger / timing | Output |
|---|---|---|---|
| 1. Closing detected | Follow Up Boss | deal.stage_updated → Closed | Webhook with contact + deal |
| 2. Closing gift | Sendoso | Day 1–2 | Physical gift / eGift shipped |
| 3. Review request | Google Business Profile | Day 3–5 | SMS + email with review link |
| 4. Tag + segment | Follow Up Boss | Day 1 | Contact tagged past-client |
| 5. Anniversary nurture | Follow Up Boss | +12 months | "Home-versary" touch |
| 6. Value touch | Follow Up Boss | Quarterly | Market update for their ZIP |
The orchestration layer — the thing that listens for the Follow Up Boss webhook and decides what to send when — is where teams either write brittle scripts or use a workflow platform. This is where US Tech Automations sits in the stack: it receives the deal.stage_updated payload, branches on deal value and property type, and calls the Sendoso and Google Business Profile APIs in the right order with the right delays, so a single closing event reliably produces a gift, a review ask, and a tagged contact without an agent in the loop.
Where it gets nuanced is the conditional logic. A $1.2M luxury closing and a $310K first-time buyer should not get the identical gift. US Tech Automations reads the deal value off the Follow Up Boss payload and routes to a different Sendoso gift tier and nurture cadence, so spend scales with relationship value instead of blasting everyone the same cookie tin. That branching — not the webhook itself — is the part teams most often get wrong by hand.
A worked example
Picture a 14-agent team in Phoenix that closed 312 transactions last year and pulled a Google review on roughly 11% of them — about 34 reviews, badly clustered around whichever month someone remembered to ask. They wire Follow Up Boss to Sendoso and Google Business Profile through an orchestration layer. When a deal hits Closed, the deal.stage_updated webhook fires; the workflow branches on the recorded sale price — according to the Zillow Research 2025 Q1 home values index, median single-family home values in their market sit near $440,000 — sends a $45 Sendoso closing gift on day 2, then triggers an SMS review request on day 4 with a one-tap Google link. Over 90 days, review capture climbs from 11% to 38% of closings — roughly 89 new reviews on the same volume — at a gifting cost of about $14,000 (312 × $45). The team did not hire anyone or change how it sells; it changed when the follow-up fired, from "manual, sometimes" to "automatic, every time."
How the gifting step actually fires
The Sendoso step is the part clients remember. When the closing webhook lands, the workflow looks up the contact, selects a gift tier by deal value, and calls Sendoso to ship it to the address on file. The agent is notified so they can send a personal text the same day — the automation handles logistics, the human handles warmth.
Two failure modes to engineer around. First, address quality: Sendoso can only ship to a valid address, so validate the mailing address from the Follow Up Boss record before calling the send API. Second, double-sends: if a deal bounces between stages, you can fire two gifts. The fix is an idempotency check — tag the contact gift-sent the moment the Sendoso call succeeds, and skip any contact already carrying that tag.
This is the second place US Tech Automations does concrete work: it performs the address validation and the gift-sent idempotency check before every Sendoso call, so a flapping deal stage never ships two gifts and a malformed address never silently fails. The gifting platform handles fulfillment; the orchestration handles the guardrails that keep the program clean.
Closing gifts in the $25–$75 range are typical for residential agents. Spend scales with deal value, but even the floor of that band, sent reliably, beats a premium gift sent occasionally.
Sequencing the review request
Reviews are the compounding asset here, and timing is everything. Online reputation is not optional: according to BrightLocal's Local Consumer Review Survey, the large majority of consumers read online reviews before choosing a local business — and real estate is as local as it gets. Ask too early — before the client has settled in — and you get silence. Ask too late and the enthusiasm has cooled. The sweet spot is day 3 to day 5 after closing, after the gift has landed (gratitude primes the ask) but while the experience is still vivid.
The mechanics: the workflow sends an SMS first (open rates on transactional SMS dwarf email), with a single tap-through to your Google review link. Email follows as a backstop 48 hours later if no review is detected. The "if no review detected" condition is what keeps you from nagging people who already left one — the workflow checks review state before sending the reminder.
A note on compliance: never gate the gift on a positive review or bulk-solicit in a way that violates Google's review policies. The automation asks every closed client equally; it does not cherry-pick for five-star likelihood — the ethical and durable approach.
| Channel | Timing | Why this order |
|---|---|---|
| SMS review ask | Day 4 | Highest open rate, one-tap link |
| Email backstop | Day 6 (if no review) | Catches non-texters |
| Personal agent note | Day 4 (manual) | Human warmth, automation-prompted |
| Re-ask suppression | Ongoing | Skips clients who already reviewed |
Follow Up Boss on its own vs. the integrated stack
Follow Up Boss is a strong CRM, and for many teams its native features cover the basics. Here is where it wins unassisted versus where the Sendoso-plus-reviews integration adds something it does not do natively.
| Capability | Follow Up Boss native | FUB + Sendoso + reviews (integrated) |
|---|---|---|
| Lead routing & CRM | Strong, built-in | Same (FUB remains system of record) |
| Action plans / drip | Yes (email/text sequences) | Yes, plus event-triggered branching |
| Physical / eGift sending | No | Yes (via Sendoso, value-tiered) |
| Automated review requests | Limited | Yes (timed SMS + email, suppression) |
| Spend per closing | $0 (CRM only) | ~$25–$75 gift + platform cost |
| Setup effort | Low | Medium (one-time wiring) |
Where Follow Up Boss alone wins: if all you need is a text-and-email drip to past clients and you have no gifting budget, its native action plans handle that without adding tools. The integration earns its complexity only when you want physical gifting and systematic review capture layered on top.
When NOT to use US Tech Automations
Be honest about fit. If you close fewer than ~20 deals a year, the orchestration layer is overkill — Follow Up Boss action plans plus a quarterly manual gift round serve you fine and cost nothing extra. If your gifting budget is zero, skip the Sendoso integration; a well-timed personal text and a native review-ask sequence captures most of the upside. And if your past-client database lives in a spreadsheet or three different inboxes, fix data hygiene first — automation amplifies whatever it is pointed at, including a mess. There are also teams whose review needs are fully met by a single-purpose review tool already wired to their CRM; if that works, a broader platform adds cost without adding outcomes. Adopt this stack when volume, budget, and a clean database all line up.
Decision checklist
Before you build, run through this. Every "no" is a reason to fix something first.
Are you closing 40+ transactions a year? (Below that, native action plans suffice.)
Is Follow Up Boss your single system of record, with deal stages kept current?
Do you have a per-closing gift budget of at least $25?
Are past-client mailing addresses captured cleanly in the CRM?
Do you have a Google Business Profile and a short review link ready?
Have you decided your gift tiers by deal value (e.g., standard vs. luxury)?
Is someone accountable for the personal, human touch the automation prompts?
If you checked all seven, you are ready to wire it. If not, the gaps are your real first project.
Common mistakes
The teams that get the least from this build tend to repeat the same errors. Avoiding them is most of the win.
| Mistake | Consequence | Fix |
|---|---|---|
| Triggering on a date, not the closing | Misses or mistimes follow-up | Trigger on the closing webhook |
| Same gift for every deal value | Overspends on small, underspends on large | Branch gift tier on deal value |
| Asking for a review before the gift lands | Lower response, feels transactional | Sequence gift first, ask day 3–5 |
| No double-send guard | Duplicate gifts on stage flapping | Idempotency tag before each send |
| Gating gifts on positive reviews | Policy risk, erodes trust | Ask every client equally |
Benchmarks: what "good" looks like
Use these as directional targets, not promises — your market and gift quality move the numbers.
| Metric | Pre-automation (typical) | Post-automation target |
|---|---|---|
| Closings with a review request | 10–15% | 90%+ |
| Review capture rate | 8–12% of closings | 30–40% |
| Closing gift coverage | ~20% of closings | 100% |
| Days from close to first touch | 14–30 | 1–2 |
| Past-client referral share of volume | Flat | Rising YoY |
On why staying in touch beats chasing new leads: according to the Realtor.com 2025 Housing Market Report, median listing time on market is roughly 60 days. Every transaction is slow and expensive to win, so retaining a relationship you already paid to acquire is the cheapest growth you have.
Glossary
Webhook: An automated message a system (Follow Up Boss) sends to another the instant an event occurs, carrying the event data. The opposite of polling.
Deal stage: The pipeline status of a transaction in the CRM (e.g., Active, Pending, Closed). The move to "Closed" is the trigger here.
Idempotency: A guarantee that running the same action twice produces the same result once — the guard against double-sending gifts.
eGift: A digital gift (gift card, e-voucher) delivered by email through Sendoso when a physical item is impractical.
Suppression logic: A condition that stops a message from sending — e.g., skip the review reminder if a review already exists.
System of record: The single authoritative source for a data type. Follow Up Boss stays the system of record for contacts and deals.
Nurture cadence: The long-tail schedule of low-pressure touches (anniversary, market updates) that keep a past client warm.
Setting it up without breaking it
A few build notes. Wire it in a sandbox or with a test contact first — you do not want your first live webhook shipping a real gift to a test record. Map the Follow Up Boss deal stages explicitly; "Closed" might be one of several closed-type stages, and the trigger should fire on the right one(s). Build the suppression and idempotency checks before you turn on volume, not after the first duplicate-gift complaint.
The orchestration and conditional branching are the parts worth offloading; that event-driven branching is modeled in the agentic workflow platform, the layer that reads the closing payload and routes the gift, review, and tagging steps. For real-estate-specific patterns — listing alerts, lead routing, and past-client nurture — the real estate AI agents page covers the adjacent workflows on this same trigger model.
Deeper context lives in our companion guides: past-client follow-up with Follow Up Boss and Sendoso and the broader past-client farming and referral playbook. If your bigger problem is the front of the funnel, the Zillow-to-Follow-Up-Boss lead follow-up integration covers the new-lead side of the same CRM.
Key Takeaways
The closing event is the only reliable trigger. Anchor the entire follow-up chain to the Follow Up Boss
deal.stage_updatedwebhook, not a date or someone's memory.Sequence matters: gift on day 1–2, review ask on day 3–5, then long-tail nurture. The gift primes the review; the review compounds.
Branch on deal value. A $1.2M closing and a $310K closing should get different gift tiers and cadences — same workflow, conditional logic.
Build the guards first. Idempotency tags prevent double-sends; suppression logic prevents nagging clients who already reviewed.
Be honest about fit. Below ~20 closings a year or with no gifting budget, native Follow Up Boss action plans are the right, cheaper answer.
Frequently Asked Questions
How does Follow Up Boss trigger the gift and review sequence?
It fires a webhook when a deal moves to a closed stage. That deal.stage_updated event carries the contact and deal data to an orchestration layer, which then calls Sendoso to ship the gift and Google Business Profile (via SMS/email) to request the review on a timed schedule. Nothing depends on an agent remembering — the closing itself is the start signal.
When should the review request go out after closing?
Day 3 to day 5 is the sweet spot. That gives the closing gift time to land first (gratitude lifts response) while the buying experience is still fresh. Asking on closing day feels transactional; asking weeks later misses the warm window. The automation should also suppress the reminder for anyone who has already left a review.
How much should I budget per closing gift through Sendoso?
Most residential agents spend $25–$75 per closing gift, scaling with deal value. A first-time buyer might get a $30 eGift; a luxury closing might warrant a $75+ physical gift. The workflow branches on the deal value from Follow Up Boss so spend tracks relationship value automatically rather than treating every client identically.
Will this violate Google's review policies?
Not if you build it correctly. The rule is to ask every closed client equally and never gate the gift on a positive review or cherry-pick who you solicit. Automated, even-handed review requests sent to all closings are policy-compliant; selectively asking only happy clients (review gating) is not. Keep the ask neutral and universal.
Do I need US Tech Automations, or can Follow Up Boss do this alone?
Follow Up Boss alone handles email/text drips well, but it does not natively send physical gifts or run timed, value-tiered review sequences. If you want gifting and systematic review capture layered on top, you need an orchestration layer between the CRM, Sendoso, and Google. If a text-and-email drip is all you need and you have no gifting budget, Follow Up Boss native action plans are enough.
What happens if a deal bounces between stages and re-triggers?
Without a guard, you could ship two gifts. The fix is an idempotency check: the workflow tags the contact gift-sent the instant the Sendoso call succeeds and skips any contact already carrying that tag. The same suppression principle applies to review asks — check whether a review already exists before sending a reminder.
Ready to wire your closing event to gifts and reviews? Start by mapping your Follow Up Boss deal stages, then see pricing and build the workflow so every closing fires a gift, a review ask, and a nurture touch automatically — no spreadsheet, no missed past client.
About the Author

Helping businesses leverage automation for operational efficiency.
Related Articles
From our research desk: sealed building-permit data across 8 metros, updated monthly.