Document

Client Intake Handoff Checklist

A practical checklist for service businesses that want fewer missing details, fewer repeated questions, and cleaner handoffs from first contact to next step.

Client Intake Handoff Checklist

A client should not have to explain the same thing three times before the business knows what to do next.

Use this checklist when requests arrive through forms, phone calls, email, referrals, direct messages, or walk-ins and the next step still depends too much on memory.

1. Name every intake path

List every place a request can enter:

  • website form
  • phone call
  • direct email
  • Facebook or Instagram message
  • referral from a partner or client
  • Google Business Profile message
  • walk-in
  • text message
  • quote request
  • booking request

If the team cannot name every intake path, requests will keep hiding in side channels.

2. Capture the minimum useful context

For each new request, the team should know:

  • who the client is
  • what they need
  • how urgent it is
  • how to reach them
  • what service or location is involved
  • whether a quote, booking, callback, or handoff is needed
  • who owns the next step

Do not collect everything. Collect enough to move the request forward without creating extra back-and-forth.

3. Make the first reply useful

The first reply should answer three things:

  • we received it
  • here is what happens next
  • here is when you should hear from us again

A fast reply that creates no next step still leaves the work fragile.

4. Protect the handoff

A request is not safe until the next person can answer:

  • what is this about?
  • what has already happened?
  • what is the next action?
  • who owns it?
  • when is it due?

If the next person needs to ask for the whole story again, the handoff is weak.

5. Keep one visible open list

Every open request should appear somewhere visible with:

  • status
  • owner
  • next step
  • due date
  • last touch
  • outcome when closed

The list can live in a CRM, spreadsheet, board, inbox label, or simple tracker. The tool matters less than whether the team actually trusts it.

6. Review the list before the day ends

Before closing the day, check:

  • new requests not answered
  • callbacks due today
  • quoted but not followed up
  • waiting on client
  • waiting on internal handoff
  • anything with no owner or date

If it has no owner or no date, it is not really under control.

A simple first fix

Pick one intake path and tighten it this week.

Good first fixes:

  • add one missing form question
  • write a better first reply
  • create a callback status
  • assign one owner per new request
  • add a follow-up date field
  • create a daily open-request review

Read the missed follow-up checklist

Book a Follow-Up Leak Review