01 · Missed-call recovery
A missed call needs acknowledgment and an owner.
A possible workflow detects an unanswered business call, checks whether the number and source are eligible for follow-up, sends a clear acknowledgment, creates or updates the lead record, and alerts the assigned person. The message should identify itself accurately and say what happens next; it should not pretend an automated reply is a human conversation.
An unanswered call during defined business conditions.
Acknowledge, capture the minimum context, create the record, and alert the owner.
The assigned person calls, qualifies, and owns the final status.
Honor replies and opt-outs; track contact, qualification, estimate, and sale.
02 · Estimate follow-up
Follow the estimate state—not a blind timer.
A useful sequence begins only when a real estimate reaches an eligible status. It pauses when the buyer replies, stops when the work is won or lost, and escalates exceptions to a person. Timing, channels, message content, frequency, and consent requirements belong in the workflow definition.
- Known state. The system can distinguish drafted, delivered, viewed, accepted, lost, expired, and incorrectly marked estimates.
- Named owner. One person is responsible for exceptions and unanswered replies.
- Visible exit. A response, opt-out, sale, loss, invalid record, or manual stop ends the correct path.
- Decision metric. Compare contact, estimate decision, sale, timing, and margin context—not message volume alone.
03 · Lead routing and escalation
Route by facts the team can maintain.
Service, territory, operating hours, availability, capacity, language, and lead source can affect ownership. Automation can apply those rules consistently, notify a backup when the first owner does not act, and keep a record of the handoff.
Routing fails when business rules are undocumented, platform fields are unreliable, or nobody owns exceptions. Lerrow maps those dependencies before selecting software or building logic.
04 · Lead-to-sale attribution
Move the source through the operating record.
A possible attribution workflow preserves source and campaign context when an inquiry enters the CRM, connects it to qualification and estimate status, and returns sold-work and revenue context to a reporting layer. Where identifiers break, duplicate records exist, or offline decisions cannot be matched reliably, those limits remain visible.
The goal is not a perfect attribution story. It is a more defensible view of which sources create qualified opportunities and customers, and where the business still lacks reliable evidence.
05 · AI boundaries
Use AI for a defined task with a safe fallback.
Appropriate task
Classifying a request, summarizing a conversation, drafting a response for review, extracting fields, or supporting intake can be useful when accuracy can be checked.
Required context
The model needs current service, territory, policy, scheduling, pricing, escalation, and disclosure rules. Missing context should produce a handoff—not an invented answer.
Human control
A named person owns sensitive decisions, uncertain outputs, complaints, pricing exceptions, emergencies, and any commitment the system should not make.
Evaluation
Review accuracy, completion, escalation, customer experience, time returned, and commercial outcome. Do not call an automation useful because it generated many messages.
06 · Written workflow
Every automation needs an operating contract.
The written scope identifies the trigger, data source, actions, owner, human handoff, consent basis, stop signals, exception path, system access, third-party costs, logging, measurement, and offboarding. Clients retain control of their accounts and business data, subject to the terms and export limits of third-party vendors.
No automation guarantees leads, appointments, sales, revenue, response performance, or platform uptime. It should make work more observable and dependable within the conditions the client can actually support.