Inbox and lead routing
Proving the lead survived the handoff
Every distributed lead gets its own 24-hour clock starting at the moment it arrived, not at a fixed batch hour. When the clock expires the agent checks the CRM for evidence a human actually worked it, reminds the rep once if not, and escalates if it stays cold.
- Who it is for
- Any owner who distributes leads to reps by email and has no way to prove the lead reached the CRM and got worked.
- Deployed for
- CertaPro of Grand Haven and CertaPro of Kalamazoo, distributing leads across residential and commercial sales representatives in two territories.
- Status
- Built, awaiting owner approval before going live
The goal
Close the gap between the email and the CRM. A lead can die silently in that gap, and the first anyone hears about it is when the customer calls a competitor.
Distinguish a lead that a human actually worked from a lead that is simply sitting where the automation dropped it. This is the hard part and it is where naive monitoring fails.
Nag as little as possible. One reminder to the rep, then escalation. A watchdog that cries wolf gets muted, and a muted watchdog is worse than none.
Cost, against the human alternative
A skill on an existing deployment. Deployment pricing is published at $10,000 for Core and $25,000 for Sovereign, with skill development hours at the published rate.
Anchor title: Residential Sales Coordinator reconciling distributed leads against the CRM every day. Typical fully-loaded cost is $60,000 to $70,000 a year including payroll tax, benefits, paid time off, ramp time, and turnover. That is a market range for the title, not a quote of anyone actual salary. The goal is not to replace that person. It is to put them in their most productive role. A coordinator who stops auditing a spreadsheet for leads nobody touched can spend that hour actually calling the homeowner, which is the work that closes jobs.
The real cost being avoided is the lost job, not the labor. That number is the owner to supply, not ours to guess.
The goal is not to replace humans. It is to put them in their most productive role. Nobody gets cut here. Your billing manager stops doing data entry and starts working collections. Your GM stops chasing paperwork and starts selling. The agent absorbs the repetitive half of a job so the person keeps the half that actually needs a person.
This is a typical fully-loaded annual range for that title, meaning base pay plus payroll tax, benefits, paid time off, ramp time before the person is productive, and the cost of refilling the seat when they leave. It is a market range for the role, not a quote of anyone actual salary.
Security
- Read-only against the CRM. The watchdog observes, it does not edit records.
- Reminders to representatives are internal mail. External customer contact is never generated by this skill.
- Escalation goes to one named person. The ladder is written into the procedure document rather than inferred at runtime.
- The definition of work being done was derived from live CRM data, not assumed, precisely because getting it wrong in either direction is expensive.
Output
- A per-lead clock, starting at the received timestamp of that specific lead.
- A single reminder to the assigned representative when the deadline passes with no evidence of work.
- An escalation to the owner if the lead stays cold after that.
- Silence when the lead was worked. Leads that were handled are closed out and never mentioned again, which is what makes the alerts credible.
Ongoing cost to maintain
- Runs hourly on a schedule. The evaluation is deterministic, so the recurring cost is hosting rather than model inference.
- The clock design means the sweep frequency and the deadline are decoupled. Increasing sweep frequency does not increase cost meaningfully and does not create duplicate alerts.
The framework that keeps it safe and keeps it cheap
- Derive the success definition from real data before writing the rule. The critical finding in this build was that the CRM automatically creates three records within seconds of a lead arriving, so the naive test for activity is satisfied by the automation itself and proves nothing. A watchdog built on the naive test would have blessed every dead lead in the system.
- Ship the skill built but not armed until the owner has approved the reminder wording, the escalation ladder, and the definition of work being done. Automation that contacts your staff should not go live on an engineer decision.
- Written procedure, owner-editable, with the rulings dated and attributed.
The procedures behind this
Each of these is a written document with a plain-English section for a person, a machine-readable section for the agent, and a dated changelog.
- certapro-lead-crm-watchdog
- certapro-wet-walk-scheduler
- w1-lead-pipeline
- lead-advisement
Where every claim on this page comes from
- Per-lead clock design, the received-time start, and the hourly sweep are specified in the canonical CertaPro Lead Follow-Up Watchdog document, version 1.1 dated 2026-08-14.
- The finding that the CRM auto-creates three records within seconds of lead arrival, and that this defeats naive activity checks, is recorded in the same document as a live-data discovery.
- Status is recorded in the canonical document as built, not enabled, pending owner approval of wording and ladder. This page reflects that status honestly.
- The companion wet walk scheduler is documented separately at version 1.0 dated 2026-08-17 and is explicitly blocked on an external data source, which is also stated rather than hidden.
Questions people ask about this
How do you know whether a rep actually worked a lead?
By first finding out what the CRM does on its own. In this deployment the CRM automatically creates three records within seconds of a lead arriving, so simply checking for activity proves nothing, it only proves the automation ran. The working definition had to be derived from live data to exclude the automatic records and detect genuine human action.
Why give each lead its own clock instead of a nightly sweep?
A fixed batch hour is wrong for almost every lead. A lead that arrives at 4:15pm is either checked eight hours early or fifteen hours late. Each lead carrying its own deadline of received time plus 24 hours means every lead gets the same fair window.
Will this spam my sales team?
One reminder per lead, and only when there is no evidence of work. Leads that were worked are closed out silently and never mentioned. That restraint is the reason the alerts stay credible.
Is there a version of this in your business?
The discovery call is a working conversation, not a demo. Bring the process that annoys you most.