Choose a response target your team can measure. Then design what happens when the lead is incomplete, the customer does not answer, or the request needs judgment.
Capture enough to act.
Record when the inquiry arrived, its source, requested service and usable contact details. Keep service and billing addresses separate. Preserve the permission actually given; a website inquiry is not blanket permission for automated calls.
Give the request an owner.
A note saying “call back” is incomplete without a responsible person or team and a due time. Taking human ownership should prevent another automatic attempt from racing the office.
Measure the right moments.
Track inquiry received, first attempted response, first two-way conversation, appointment booked and unresolved handoff. A dial attempt is not a conversation. A conversation is not a booked appointment.
Time to first attempt · Time to first conversation · Booked appointments · Open handoffs · Requests that stopped contact
Use a short qualification path.
Confirm the service and address, then check coverage and appointment eligibility. For an emergency, unusual scope or uncertain answer, follow the business’s defined review path. An AI should not improvise a promise to close the conversation.
Make callback rules explicit.
For an approved workflow, define permission evidence, local calling hours, attempt limits and when follow-up ends. Stop when the person opts out or the office takes over. Review applicable requirements before activating a calling program; this is a workflow guide, not legal advice.
Close the loop.
Save useful facts and next actions in the lead record. Verify saved appointments and connected-calendar results. Otherwise distinguish “not ready,” “not eligible,” “needs a person” and “unable to reach.” They need different next steps.
Pilot the difficult cases.
- A customer asks to stop contact midway through qualification.
- The address changes after appointment options are offered.
- No reachable appointment is available.
- The calendar provider stops responding.
- The person asks for a human.
- A source delivers the same lead event twice.
Run these cases before using speed as a headline metric. A fast process that leaves the office guessing creates more work later.