Sent estimates should not rely on memory.
For home-service owners, follow-up is one of the easiest leaks to miss. A good lead gets an estimate, the owner gets busy, and the next touch depends on somebody remembering. FieldLayer turns stale estimates into a human-reviewed follow-up queue.
What usually breaks
The estimate was sent four days ago. The customer has not replied. The CRM says “sent,” but nobody owns the next move, so a warm job quietly cools off.
What FieldLayer installs first
AI watches for stale sent estimates, drafts a short follow-up, and flags anything risky. The owner or office manager approves, edits, or rejects the message before it reaches the customer.
- AI sweeps estimates by age, value, and last customer touch.
- AI drafts a helpful follow-up tied to the actual job context.
- Human approves before sending.
- Outcome is logged: sent, waiting, won, lost, no action, or follow up later.
Install map
Define stale
Set the first rule: for example, sent estimate with no reply after 3 business days, or high-value estimate with no scheduled follow-up.
Create the rescue queue
Surface the customer, job type, estimate value, last touch, and recommended next action in one owner-visible list.
Draft the next touch
AI writes a short, specific follow-up that sounds like the business and references the job without inventing details.
Approve before send
The human decides whether to send, edit, call instead, mark lost, or wait. AI does not chase customers on its own.
Learn from the correction
If the owner changes tone, timing, or channel, that correction becomes the next draft rule.
Why this is a Starter Kit workflow
Follow-up is close to revenue, easy to inspect, and safe to keep human-reviewed. The first install is not “AI sells for you.” It is a stale-work queue, a drafted next move, and a clear approval decision.