+45%
Increase in Appointment Updates
2 hrs
In Bandwidth Saved Per Week
Revive refers home seller leads to real estate agents and only gets paid when a home sells. That means the business relies heavily on agents updating the status of their leads. Agents were supposed to log into a dashboard weekly and update deal progress. In reality, that didn't happen consistently. Deals would sit in "Appointment Booked" with no confirmation on whether the onsite even took place. To compensate, ISAs were spending roughly two hours per week calling agents individually to get status updates. It was a manual workaround for a broken feedback loop.
One of the most important metrics in the pipeline is how many leads become qualified. But when appointment outcomes aren't being confirmed, reporting becomes unreliable. And when reporting is unreliable, it's difficult to evaluate whether lead generation is actually working.
Instead of adding more reporting requirements or chasing agents for updates, I removed the friction entirely.
If an agent had an onsite appointment the day before, they now receive a simple SMS asking if it happened. They reply yes or no. The deal stage updates automatically in the CRM. No dashboard login. No manual data entry. One text message.
Today 9:41 AM
Hi Max, this is Revive. Did your onsite visit at 33 Almond Tree Ln happen? Reply YES or NO.
Yes
Delivered
iMessage
Result
45% increase in appointment updates
From less than half confirmed to reliable pipeline reporting
HubSpot doesn't support inbound SMS parsing or conditional deal updates based on text replies. To build this, I needed a tool that could sit between Sakari and HubSpot and handle the routing logic. I built two n8n workflows that work together: one that sends the outbound SMS and one that processes the agent's reply. The loop at the end is key — if an agent has three unconfirmed appointments, they don't get three texts at once. They get one, reply, and immediately get the next one.
Runs every 3 days at 9 AM PT. Scans HubSpot for deals where an onsite was booked but the outcome was never recorded, groups them by agent, and sends one confirmation SMS per agent at a time. Each sent deal is flagged so it won't get picked up again on the next run.
Outbound — Appointment Confirmation Request
Fires the moment an agent replies. Routes the response through a Yes / No / Unclear switch — unclear replies get flagged for manual review in Slack. A yes moves the deal to "Met With" in HubSpot; a no marks it "Denied." The workflow then checks for more pending deals and fires the next SMS automatically if there are any.
Inbound — Processing the Agent's Reply
This wasn't a strategy change. It was a feedback loop fix. The data was always there. The agents just had no low-friction way to provide it. Replacing a weekly dashboard login with a single text reply changed the behavior overnight.
The 45% improvement in confirmed appointment data meant the team could finally trust their pipeline numbers — making it possible to evaluate lead generation performance accurately, identify which channels were producing leads that converted, and allocate budget accordingly.
Friction is the enemy of compliance.
Asking agents to log into a dashboard weekly created enough friction that it simply didn't happen. A text they could reply to in seconds had near-perfect compliance.
Sequencing beats batching.
Sending one confirmation at a time and chaining the next automatically kept the interaction simple. A batch of texts would have felt like spam and gotten ignored.
Clean data enables everything downstream.
Better reporting accuracy meant the team could finally evaluate channel performance, optimize spend, and trust the numbers they were presenting to leadership.