Use cases / Roofing / Quote follow-up
Roof replacement estimate follow-up
Homeowners collect several bids, and follow-up is inconsistent.
The business case
Incremental-lift model: baseline lost volume × lift × job value × gross margin − running cost. Every input below is an illustrative assumption, not an industry statistic. Measure the client's real baseline first.
- Baseline: 6 open roofing estimates per week
- Average job value $12,000, gross margin 25%, running cost $100/mo, setup $1,500
| Case | Lift (extra booked jobs ÷ baseline) | Extra gross profit / mo | Payback |
|---|---|---|---|
| Conservative | 1.5% | $1,069 | 1.4 months |
| Expected | 3.0% | $2,238 | 0.7 months |
| Optimistic | 4.5% | $3,407 | 0.4 months |
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
- Zapier, Make, and n8n connectors for the job-management app: not verified. Confirm the exact trigger exists before you rely on it.
Check what the app already does first:
- No direct native equivalent known. Still ask the owner what they already pay for.
Build steps
- Trigger: estimate sent in AccuLynx (add-on) or JobNimbus.
- The LLM drafts an email citing two findings from the inspection notes. The rep approves it.
- Warranty text is pulled verbatim from the manufacturer's terms.
Test cases before go-live
- The warranty wording matches the source exactly.
Tool names are examples, not endorsements. Check current features, plan tiers, and pricing before quoting a client.
Sample prompt
Write a follow-up referencing two findings from the inspection notes, the warranty option the customer chose (verbatim terms), and an invitation to ask questions. No pressure.
Pitch it to the owner
"Consistent, specific follow-up on every estimate."
Lead with the outcome, not with "AI," and show the business case using their own numbers.
What can go wrong
- Warranty claims must match the manufacturer's actual terms.
- 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
$1,000–$2,500 setup
Starting estimate only, not verified against market rates. Adjust for scope and support.