What should happen when an inquiry comes in

Christian B., M.D. & Madison K., M.B.A. · Backend Ops · updated november 2026

the short answer

When an inquiry comes in, it should land in one place that captures the details of the job, sorts it toward the work you want most, and gets a real reply within 24 hours. Build that by hand first, then implement the system behind it.

  1. 01The first reply is the first touch point of a long project.
  2. 02Intake gathers the details you need before the first call.
  3. 03Every inquiry lands in one place, triaged toward the jobs you want.
  4. 04Speed to lead: a real reply with a next step inside 24 hours.
  5. 05Run it by hand first, then implement the system behind it.
// rather watch?
open on youtube ↗

Take in better information at the door

// what intake gathers
  1. 01The projectWhat they want built, and where.
  2. 02Size and timingRough scope, timeline and budget range.
  3. 03What existsPhotos, plans and who else is on the build.
  4. 04How they found youThe source, so you know what is working.

The first reply is the first touch point of a project that may run for months. Most businesses meet it with a name, a phone number and a note that says call me. So the first call gets spent gathering basics, and nobody can prepare for the job until it is already underway.

Good intake takes the responsibility off the client to find the right words we need for a clear understanding of what the job may require. The questions do that work: what they want built and where, the rough size and timeline, the budget range, photos or plans. They answer once, in their own language, and you walk into the first call prepared.

Where the inquiry lands, and how it gets triaged

// the front door
the way it runs now
  • Inquiries scattered across inbox, texts and DMs
  • Every inquiry looks the same until someone calls back
  • The best jobs wait behind the easy ones
the way it runs with it built
  • Every inquiry lands in one place with a record
  • Sorted on arrival toward the jobs you want most
  • One named person owns the reply

An inquiry that lands in a shared inbox, a text thread or a DM has no home. Everyone assumes someone else answered it. So every inquiry, however it arrived, should land in one place where it gets a record, one named owner and a lane.

That place is where triage happens. Because intake already holds the details, each inquiry can be sorted on arrival: the full projects you want most, smaller jobs that need a different path, and poor fits that deserve a kind, honest no. Choosing the right clients is worth more than finding more of them.

// what it looks like set up
arrives byDMTextWebsite
what they sent · DM“Hi! Love your work. Can you do our kitchen?”Then the intake link, answered once in their own words.
what it lands withreply due in 23h 52m
Project
Full kitchen remodel, new build
Size
Cabinetry, stone, lighting
Timeline
Start in spring
Budget range
$80K to $120K
Has
Plans + 8 photos
Owner
One named person
Want most
Full projects, answered first
    Different path
    Smaller jobs, their own route
      Honest no
      Poor fits, a kind reply

        Every inquiry still reaches the owner. Nothing is answered or closed for them.

        Speed to lead: a real reply inside 24 hours

        A fast reply only counts when it already knows what the client asked for.

        Speed to lead matters. The business that answers first, with something real, usually gets the first call. The standard we hold is a reply within 24 hours that confirms the ask, names who owns it, sets the next step with a date and says what to prepare. Silence reads as no.

        Triage is what makes that window possible. When the details are already captured and the inquiry is already sorted, the owner is not starting from zero. The reply goes out fast because the thinking is done, and the jobs you want most get answered first.

        Build it by hand, then implement the system

        // hand first, system second
        1. 01Ask it by handRun the intake questions and send each reply yourself.
        2. 02Keep the listEvery inquiry, its lane, who replied, and when.
        3. 03Find the patternSee which inquiries become the projects you want.
        4. 04Implement the systemCapture, sort and alert behind what already works.

        We run the front door by hand before any system touches it. Ask the intake questions yourself, write each reply yourself, and keep one simple list of every inquiry: what it held, where it came from, which lane it went in, who answered and when. A few weeks of that list becomes the spec.

        Then we implement the system behind what works: intake that captures the details, every inquiry recorded and sorted on arrival, and a nudge to the owner before the 24 hours run out. Everything still reaches the owner. Nothing is answered or closed on their behalf, and people who go quiet get a polite follow-up.

        // what it feels like when this is missing
        1. 01Shared inboxI thought someone else already answered that one.
        2. 02Lost in textsOur best inquiry this month came by text and just sat there.
        3. 03Cold first callWe spend the whole first call explaining how we work.
        4. 04Wrong jobs firstWe spent the week quoting small jobs while the big one waited.
        // when this isn’t the right call
        • 01Inquiries are rareThen the front door is not your problem yet. Demand is. Before you polish the reply, you need a channel that brings new inquiries in steadily, like search, content or referrals you actually ask for. That is the first thing to build, and it is work we do.
        • 02You are already turning work awayThen a faster front door only brings in more of what you cannot deliver. The limit is capacity: the team, the seats and the rhythm behind the work. Fix that first, so every job you win is one you can take on and deliver well.

        Not sure which one is slowing you down? Book a growth call and we will map it with you, or join us on After Hours Live and watch us work through it.

        // questions owners ask
        How fast should we reply to a new inquiry?+

        Within 24 hours, with a real next step in the reply. Speed to lead matters, but a quick thank-you with nothing after it reads as silence. What matters most is that the client knows what happens next and when.

        What should our intake ask?+

        Ask what they want built and where, the rough size, timeline and budget range, photos or plans if they exist, and how they found you. More importantly, intake takes the responsibility off the client to find the right words we need for a clear understanding of what the job may require. A good intake lets the owner come into the first call prepared, with the right information already in hand. Keep it to what you will use, since every extra question adds friction between a customer and a submitted inquiry.

        How do we triage inquiries without losing good ones?+

        Sort on arrival using what intake captured: the full projects you want most, smaller jobs with a different path, and poor fits that get an honest no. Everything still reaches the owner, so nothing is filtered out unseen.

        Should we automate the first response?+

        Not before it works by hand. Run the intake and send the replies yourself for a few weeks and keep a list. Once you know what a good reply holds, implement the system behind it, so it captures and sorts without answering for you.

        Keep reading

        Operating Notes
        All of Operating NotesHow a project-based service business grows past its capacityClarity · Rhythm · Systems · Ceiling→

        See where your business is holding it up

        Book a growth call and we map how the work runs with you and find the stage that is slowing it down. Or join us on After Hours Live and watch us build a real business system, live.