Case study 01
AI-enabled CRM for a field-service business
A US tree-care company needed calls, estimates, and invoice follow-up on one record. We built it around a voice agent, a proposal editor with AI, and follow-ups that stop when a proposal is accepted.
Problem
The commercial path was split. A customer called, someone checked the calendar, a proposal was assembled from notes and photos, and an accepted job still needed an invoice and instructions for the crew. Email, SMS, and the calendar continued alongside that work.
The company needed those steps to share one record, with a manager still reviewing an invoice or a work order before it went out.
Results
AI voice agent
Feb 13 – Oct 19, 2026
Callers who wanted an estimate inside the service area, booked on the call
- This company, 94 of 151 callers
- 62%
- Industry average
- 28%
Industry average: 28% of inbound leads booked, ServiceTitan 2025 Home Services Benchmark Report, via Sameday.
- real calls answered
- 786
- after hours, 18% of all calls
- 144
- accepted within 60 days of the first call, from 50 callers
- $145k
- from 8 after-hours callers who would have reached voicemail
- $19k
Automated follow-ups
May 14 – Aug 14, 2026
$205k
accepted in 47 proposals after an automated follow-up
- Within 24 h18
- 24 to 48 h6
- Later23
Time from a follow-up email to acceptance
- jobs a month
- ≈16
- accepted a month
- ≈$68k
- median job
- $2,300
- signed online by the client
- 12
From the call to the payment
Every step lands on the same record.
Call or new lead
Voice agent
Checks the calendar and books the visit.
- Google Calendar
- Outlook
Proposal
Drafted with the AI assistant, edited by the office.
Follow-ups
Email and SMS on a schedule until the client answers.
- Resend
- Twilio
Accepted
The client signs online. Proposal follow-ups stop.
Invoice
Drafted on acceptance with the work order. Nobody retypes the job; a manager reviews and sends.
Invoice follow-ups
Reminders carry a pay link.
- Resend
- Twilio
Paid
The payment is recorded and synced to the books.
- Stripe
- QuickBooks
What we built
Voice agent
- Answers the business number and recognises returning callers
- Checks the ZIP code against the service area
- Offers open slots, books the visit, and confirms it to both sides
- Tags the lead and writes a summary after every call
- Callback requests alert the team by email
Proposals
- Templates with packages, optional items, and hidden cost lines
- Job photos, versions, and drafts; the job address picked on a map
- Matching editors for invoices and work orders
- A public link where the client accepts with an e-signature
AI assistant
- Works inside every document editor
- Changes line items, prices, and notes in proposals, invoices, and work orders
- Staff can dictate; speech is transcribed
- Models were compared on 29 real conversations before a switch
Follow-ups
- One engine for proposal and invoice reminders
- Email and SMS steps, with delays from minutes to days
- Each message carries the client's name, the total, and the link
- Unsubscribe link in every email; SMS only with consent, from A2P 10DLC registered numbers
- Stops on acceptance; overdue steps are skipped
Client chat
- The client replies to the proposal or invoice email
- The reply lands unread on the right lead: who wrote, when, about which document
- The manager answers from the dashboard, without opening a mailbox
- The client gets the answer in the same email thread
Plant Health Care
- A catalog of products, brands, and application rates
- Products, rates, and prices pulled into each job
- Application records filled in on a phone
- Follow-up proposals from site observations
- Neighbor-notice reminders before pesticide jobs
- Recurring treatment programs with scheduled visits and invoices
Integrations
The CRM calendar is the single source of truth: Google and Outlook both sync through it.
Google Calendar
Two-way sync for each team member. The voice agent books against it.
Outlook Calendar
The same two-way sync through Microsoft Graph. Edits in Outlook flow back.
QuickBooks Online
Customers matched, invoices and payments synced, payouts recorded as deposits. Failed syncs retry.
Stripe Connect
Each business connects its own account. Invoices carry pay links; payments and refunds come back.
Twilio
Numbers for the voice agent and SMS, with STOP and START opt-out.
Resend
Outgoing email runs through a queue. Client replies come back into the lead's chat.
See it work
Technical path
The first backend ran on n8n. We later replaced it completely with a custom backend: React, TypeScript, Supabase, and serverless functions.
We designed and built the system end to end over about 11 months. Each business on it gets its own workspace, team roles, and connected accounts.