The inquiry-to-estimate handoff checklist

← All guides and worksheets

Choose a recent ordinary inquiry, one that arrived through two channels, one that stalled, and one that was never a fit. Follow each from the original message through the estimate or closing reason. Use records your business is allowed to access, and remove customer details before sharing examples with a provider.

For every handoff, write down who noticed the inquiry, where they entered it, who became responsible, and how the next person knew to act. An unanswered notification and a missing owner are different problems. Connecting more systems will not fix an assignment rule that nobody has agreed on.

• List each entry point: website form, phone, email, referral, and any lead platform you actually use.
• Name the record that determines the current status: the job system, CRM, or a deliberately maintained shared list.
• Record the current first-response owner and a backup for time away.
• Mark where information gets retyped or a person must remember to check another inbox.

Capture enough to decide the next action. A name and message alone may leave the team chasing the service location, type of work, or preferred callback window. Conversely, a long intake that requires a homeowner to diagnose the work can create avoidable friction. Ask for the facts your team actually uses.

Keep the original inquiry available beside the summary. A summary should make a message easier to review; it should not replace the source when the scope or timing matters. Store the inquiry source separately from a guess about whether the prospect is qualified.

• Stable inquiry ID, received time, source channel, and a link to the original message.
• Customer-provided contact details, service location or area, and preferred contact method.
• Requested work, relevant timing, and the specific facts still missing.
• Assigned owner, current status, next action, and due time.
• Related customer, job, and estimate IDs when confirmed; leave uncertain matches for review.

A matching phone number is a clue, not always proof of the same job. One household can request two projects. Match the person and the request before merging records.

A useful pipeline says what must happen next. Adapt the example below to your business, including who can change a status. An acknowledgment means the message arrived; it does not mean someone reviewed the request, reserved a visit, or committed to a price.

Decide who approves message wording, which channels may be used, when contact is appropriate, and when the sequence ends. Start with draft messages or internal reminders if the team has not agreed on those rules. Customer replies should create a visible task, not simply disappear into a paused sequence.

A reply about a start date requires someone with current scheduling knowledge. A pricing objection requires someone authorized to discuss the estimate. Do not let a reminder workflow invent availability, discounts, scope changes, or promises to close the loop.

• Stop scheduled reminders when a customer replies, opts out, accepts, declines, or reports a wrong contact.
• Recheck the current record immediately before a message sends, including activity entered by the team.
• Assign questions and complaints to a named person with a due time.
• Set a maximum number of follow-ups and a clear final status.
• If access or a connection fails, expose the failure and leave a manual next step.

Use fictional test inquiries and a controlled destination before any customer-facing launch. Ask the team to predict what should happen in each case, then compare that prediction with the actual record and message. Keep the evidence: status, assigned owner, source links, and whether a message was sent.

Start with one channel and one owner. Review the next real batch together. Track the share of inquiries with an owner and next action, time to a useful human response, and records that required correction. Treat estimate acceptance as a separate outcome with several possible causes; a completed handoff is not proof that automation won a job.

• The same inquiry arrives twice: one coordinated next action, without losing either source.
• The same customer requests a second job: the new request remains distinguishable.
• A reply arrives just before a reminder: the reminder is held and the reply is assigned.
• An estimator is unavailable: the agreed backup can see and accept the handoff.
• The CRM connection fails or retries: no duplicate customer messages and a visible recovery task.
• A teammate changes the estimate status manually: the follow-up reflects the current status.

Download the plain-text template and paste it into a shared document, or copy the version below. Fill it in with your team. No email address or account is required.

Download: Inquiry-to-estimate handoff worksheet (.txt) ↓

INQUIRY-TO-ESTIMATE HANDOFF WORKSHEET

Business / workflow:
Workflow owner / backup:
Review date:

1. CURRENT PATH
Entry channels:
Record that determines current status:
Where information is retyped:
Where work waits for a person to notice:

2. MINIMUM RECORD
[ ] Inquiry ID, received time, source link
[ ] Customer contact, service area, preferred contact method
[ ] Requested work, timing, missing facts
[ ] Owner, status, next action, due time
[ ] Confirmed links to customer, job, and estimate records
Our rules for duplicate inquiries versus separate jobs:

3. EACH HANDOFF (COPY FOR EACH STEP)
Current status:
Person responsible:
Action required:
Due-time rule:
Required information:
Exit condition:
Backup if the owner is unavailable:

4. FOLLOW-UP RULES
Approved channel and message:
Contact window:
Maximum follow-ups / final status:
Reply, opt-out, acceptance, decline, wrong-contact stop rules:
Person responsible for answering a reply:
How current status is rechecked before sending:
What happens when a connection fails:

5. TEST BEFORE LAUNCH
For each case, record: expected result / observed result / pass or fix.
[ ] Duplicate inquiry through two channels
[ ] Second job from an existing customer
[ ] Reply immediately before a reminder
[ ] Owner unavailable
[ ] Connection failure and retry
[ ] Estimate status changed manually

6. REVIEW
Inquiries reviewed:
Inquiries with an owner and next action:
Time to useful human response:
Records requiring correction and why:
Smallest improvement to try next:
Person responsible / review date:

Bring the handoff that still depends on memory and the tools involved. Adam can help determine whether a rule in your current system, a setup session, or a scoped connection is enough.

A one-on-one AI setup session is $295; team working sessions start at $950. Full custom automations start at $2,500. Scope, fixed phase pricing, and completion checks are agreed before custom work starts; software subscriptions and usage charges are separate.

Discuss an inquiry handoff ↗

See scope and pricing · See setup sessions

Related capabilities

• Lead response and follow-up capability
• Sales follow-up capability

Keep planning

• Use your existing tools or build custom automation?
• Plan your first small-business automation