A new lead can reach your inbox and still go nowhere. The missing piece is often an agreed owner, a recorded next action, or a clear distinction between “message sent” and “customer reached.”
This walkthrough produces a basic follow-up process your office can run in a shared spreadsheet or an existing lead system. It does not require buying new software. Use a system with access limited to the team members who need the information.
Create a lead register with useful fields
Start with one row per potential job, not one row per message. Record:
- Lead ID and date received.
- Customer name, preferred contact method, service requested, and location.
- Known source, or “unknown” when you cannot establish it.
- Assigned owner and backup.
- Current status, next action, and due date.
- Outcome and reason if the job does not proceed.
If the same homeowner calls after submitting a form about the same job, link the conversation to the existing record. A separate project may need its own record. Keep notes relevant to the work; avoid copying unnecessary sensitive details into a general team sheet.
Define statuses that mean something observable
| Status | What must be true |
|---|---|
| New | The request arrived and needs an initial review. |
| Attempted contact | Someone tried to reach the customer; a conversation is not yet confirmed. |
| Qualified | The requested work and location fit, with enough information to agree the next step. |
| Assessment scheduled | The customer and business agreed a time. |
| Estimate sent | The proposal was delivered and a follow-up action is recorded. |
| Booked / not proceeding | The outcome is confirmed, with a reason when known. |
Adapt these to your trade. Do not mark a job “booked” because someone clicked a button. Google Ads similarly distinguishes initial leads from later qualified and converted outcomes; see its lead-goal definitions. Your internal status names should reflect your own workflow.
Assign an owner and a backup
Write down who reviews new requests during business hours and who takes over during absences. Decide what happens outside those hours. If urgent calls need different handling, document that path separately.
Choose a response target your team can actually support. Review missed targets before promising a shorter one publicly. A notification to several people is not a substitute for assigning responsibility.
Write two messages your team can adapt
Request acknowledgment“Thanks for contacting [business] about [service]. We’ve received your request. [Team/person] will contact you during [business hours] to confirm the details and discuss the next step. This message does not confirm an appointment.”
Estimate follow-up“Hi [name], I’m checking that you received the proposal for [project]. Is there anything you’d like us to clarify about the scope or next steps? You can reach [person] at [contact].”
Replace every placeholder before use. Communicate through the channel the customer requested or agreed to use, honor requests to stop, and keep a service conversation separate from unrelated promotional messaging.
Agree the next follow-up with the customer where possible. Avoid repeatedly sending automated messages after they have already answered.
Test a handoff before relying on the process
Create a labeled test request. Have the owner record its status and next action, then ask the backup to continue using only the record. If they need to ask what happened, add the missing context.
For example: “Panel-upgrade inquiry; coverage confirmed; customer requested an afternoon callback; Jordan to call Tuesday.” That gives a colleague more to work with than “follow up.”
Review the exceptions each week
Filter for unassigned leads, overdue next actions, unanswered attempts, and estimates with no outcome. Pick a recurring review time as an internal operating habit, not a universal response benchmark.
Investigate the reason behind each stall. An unserviceable location calls for clearer coverage; an unanswered request calls for a routing or staffing fix. Use the same definitions over time so the report stays comparable.
