This business receives customer requests through phone messages and call transcripts, while estimates, technician decisions and invoice follow-up were handled as separate manual steps. Nothing connected the first message to the final payment.
The problem: not every message is a lead
The documented intake problem was qualification, not speed. Messages arriving in the channel included system alerts, payment updates, appointment changes, short replies and follow-ups on existing jobs. Treating all of them as new customer requests created records nobody needed.
Even for genuine requests, the work was repetitive: check whether the customer already exists, create them if not, create the lead, classify it, then move on to estimating - where notes, media, prices and labor all had to be gathered and totaled again.
What was deployed
Four systems are connected in one path:
- Request qualification - each message or transcript is checked to decide whether it represents a genuine new service request. Alerts, payments and follow-ups stop here.
- Customer match or creation - the customer is searched in the job system and reused when found, or created when not. This is what removes duplicate records at the source.
- Lead creation and classification - the request is placed in the closest job category, given an urgency level, saved as a lead, and emailed to the team.
- Estimate preparation - materials are identified from the approved scope, current material prices are collected, and a complete estimate is produced with labor, materials, margin and tax.
- Review and revision - the estimate is sent to the owner for approval. Approved estimates are written back with detailed internal notes retained.
- Technician recommendation - built from job type, ZIP code and estimate value, then confirmed, changed or cancelled by the owner before notification.
- Overdue invoice follow-up - a scheduled process checks open invoices and reminds customers with an overdue balance and a valid email address.
Where the human stays in control
Estimate approval and technician selection both remain owner decisions. The system prepares the work; it does not make the commitment. That is the difference between automating admin and automating judgment - and it is why the workflow can run unattended on intake without running ahead of the business.
