A text that was technically correct and practically useless.
A customer notification that was accurate and useless.
Built by Surge, live in a client's business, measured as described.
- 16
- days it ran before it was turned off
We built a message that told the homeowner their crew was starting that day. It ran for sixteen days and we killed it.
Crews arrive at five or six in the morning. The message landed around nine, by which time the crew had been on the roof for three hours. So it did not read as helpful, it read as a system that did not know what was happening at the house. Being accurate was not the same as being useful.
It came out, the owner was told why in writing, and the acceptance test we run before anything goes live now asks the question that would have caught it: not whether the message is true, but whether the customer is glad it arrived.
- JobNimbus automation
- Business texting
Message timestamps compared against actual crew arrival times, then a judgment call the owner agreed with.
Every engagement produces at least one of these. Publishing them is the only way a prospect can tell the difference between a company that tests its work and a company that has never looked.
Anonymization
Same company as the other roofing case studies.
Not sure which of these applies to you?
The Free AI Revenue Roadmap is a 30-minute call and a one-page document naming your three highest-value opportunities. You keep it either way.
Find out where the revenue and the hours are going.
Thirty minutes on a call. A one-page roadmap with your three highest-value opportunities, reviewed by Austin before it is sent. Yours whether or not you hire Surge.