Use cases / Roofing / Review requests
Review requests after install (setup service)
Reviews matter, and customers rarely leave one unless asked.
The business case
This one is mainly a time-saved case, so we don't claim revenue. Assumptions (illustrative): 5 installs per week, about 3 min saved each, staff time valued at $30/h, running cost $0/mo, setup $500.
| Case | Hours saved / mo | Value of time − running cost |
|---|---|---|
| Conservative | 0.5 h | $16 |
| Expected | 1.1 h | $32 |
| Optimistic | 1.6 h | $49 |
Time saved only matters if it gets used on billable work. Track the before and after.
Requirements & gating
- AccuLynx: the API needs an API key plus the paid AppConnections add-on. verified
- JobNimbus: has an Open API. verified Coverage of the exact endpoints you need: not verified
Check what the app already does first:
- No direct native equivalent known. Still ask the owner what they already pay for.
Build steps
- Use the CRM's native review tools if they exist (not verified), or trigger on job complete.
- Ask everyone the same way, with no gating.
Test cases before go-live
- Disputed job: nothing is sent.
Tool names are examples, not endorsements. Check current features, plan tiers, and pricing before quoting a client.
Sample prompt
Draft a thank-you text after {customer}'s roof install, asking for an honest review, with the link.Pitch it to the owner
"Every install gets a review request."
Lead with the outcome, not with "AI," and show the business case using their own numbers.
What can go wrong
- No gating and no conditional incentives.
- Texting consent: Under the TCPA, automated texts generally need prior express consent, and marketing texts need prior express written consent. Honor STOP right away and keep consent records.
- Twilio/10DLC (2026): new A2P 10DLC campaigns must include public privacy policy and terms URLs (required since June 30, 2026), a verifiable opt-in, and opt-out language. Third-party lead generation and affiliate marketing are forbidden use cases. verified
- Reactivation defaults to email. Texting past customers is marketing. Use SMS only where written consent is documented.
- Call-recording consent: some states, including California, require all parties to consent (this list is not exhaustive). The safe default is to disclose recording and the automated assistant at the start of every call.
- AI voices: the FCC's February 2024 declaratory ruling (FCC-24-17) treats AI-generated voices as 'artificial voice' under the TCPA, so outbound AI calls generally need prior express consent. Further AI disclosure rules were only proposed in 2024. Keep builds inbound unless counsel approves. verified
- Failure modes: hallucinated details, missed escalations, and integrations that break silently. Add a human fallback, daily error alerts, and a weekly transcript review.
Not legal advice. Texting, calling, and recording rules vary by country and state and change over time. Have the client confirm compliance with qualified counsel before launch.
Suggested price
$300–$750 one-time setup service
Starting estimate only, not verified against market rates. Adjust for scope and support.