7
55 Comments

How do you handle leads that come in after hours? (quick poll)

Running a quick poll for local service business owners (HVAC, plumbing, dental, real estate, etc.)

When a lead emails or texts after hours — what actually happens?

Genuinely curious how many people are losing jobs they never even knew about. Drop your answer below 👇

When a lead contacts you after hours, what happens?
  1. I reply when I see it (hours later)
  2. I miss it completely and lose the lead
  3. I have a VA or auto-reply set up
  4. I reply within minutes — always on
Vote
on July 6, 2026
  1. 1

    We use automated responses for initial qualification (basic questions answered by AI) and then route hot leads to our async inbox. The key insight is that not every lead needs an immediate human response — they need a timely one. Setting expectations with an auto-reply that says 'will get back within 4 hours' works better than scrambling to answer instantly.

    1. 1

      "not every lead needs an immediate human response — they need a timely one" — that's a good distinction. expectation-setting does a lot of the heavy lifting.
      the nuance i'd add: it depends heavily on the category. for SaaS or B2B, 4-hour SLA is totally fine — the buyer isn't in emergency mode. for local services (plumbing, HVAC, locksmith, pest control), the lead is often in problem mode right now and whoever picks up first wins, even if the answer is just "we got you, someone will call in 20 mins."
      routing hot leads to async inbox is smart — that's essentially what CloseReply (closereply.com) does too. AI handles the first exchange, qualifies intent and urgency, then the owner sees a prioritized inbox in the morning: hot leads flagged, cold ones filtered. so the human effort goes where it actually converts.
      curious what you're using for the AI qualification layer — built in-house or off-the-shelf?

  2. 1

    I don't run a local service business, but I've seen the same problem with SaaS founders. Leads often come in while you're sleeping or working, and a few hours of delay can make a big difference. I'd be curious whether you've measured how much response time actually affects conversion.

    1. 1

      yes — and the numbers are pretty sobering. MIT did a study showing that responding within 5 minutes makes you 100x more likely to connect with a lead versus responding after 30 minutes. after an hour, most leads have mentally moved on.
      for local service businesses it's even sharper because they're not just evaluating you — they're shopping simultaneously. an HVAC lead at 10pm has three tabs open. first callback wins.
      that's the exact problem CloseReply (closereply.com) solves. when a lead comes in after hours:

      AI responds instantly, sounds like the business owner — not a bot
      asks qualifying questions (what's the issue, when do you need it, what area)
      keeps them warm and engaged overnight
      owner wakes up to a qualified, pre-conversational lead instead of a cold form fill

      the conversion lift we see: businesses stop losing the "first 5 minutes" window completely. the lead that would've gone to a competitor at 11pm is already booked by 8am.
      for SaaS it's a bit different — usually a sequence or sales rep handles it — but for solo founders taking inbound, same math applies. curious what you're using on your end for that gap?

      1. 1

        Interesting. Have you found that users are comfortable talking to an AI after hours as long as it moves the conversation forward, or do some still prefer waiting for a human?

        1. 1

          mostly comfortable — as long as it doesn't feel like a bot. that's the whole product bet.
          what we've found: people don't actually care if it's AI, they care if it's useful. if the first message asks a smart follow-up question ("what area are you in?" or "is this urgent or can it wait till morning?"), they engage. if it sounds like a generic auto-reply, they disengage immediately.
          the businesses where it works best are the ones where the AI response is indistinguishable from the owner texting back. that's when conversion holds up.
          the ones who still want a human no matter what tend to be older demographics or high-ticket decisions (think $10k+ home renovation). for a $200 HVAC service call at 11pm, they just want to know someone got their message and will show up tomorrow.
          if you're curious to see how it handles a real conversation, happy to walk you through a demo — closereply.com or just reply here.

          1. 1

            That's interesting. Have you found certain types of follow-up questions consistently work better than others, or does it depend entirely on the industry?

            1. 1

              Mostly depends on the lead source, but a few patterns hold across industries:
              The highest-converting follow-up questions are ones that acknowledge the specific problem they mentioned — not generic "how can I help?" stuff. For home services (HVAC, plumbing, etc.), urgency questions work best: "Is this something you need looked at this week, or are you planning ahead?" That one question sorts hot leads from tire-kickers instantly.
              For higher-ticket services, timeline + budget questions in the first reply tend to qualify faster. But the bigger variable I've found is speed, not question type — the same question sent in 2 minutes vs. 2 hours gets completely different response rates. First responder wins the job more often than the best follow-up question does.

      2. 1

        Neither, in my case — the intake IS the phone call. The bot answers the live call, captures the details right there in conversation (name, what they need, callback number) and logs it, so there's no form to abandon or an email that sits unread. The drop-off risk in voice is different: it's the first 3 seconds. If it sounds like a machine they hang up before any intake happens at all. Nice to hear CloseReply came from that same HVAC-guy repetition — that's the exact signal I'm waiting for. Are you finding SMS or email converts better once you've captured them?

        1. 1

          voice intake is a different beast entirely — you're right that the 3-second hang-up risk is the whole game. no form abandon, no unread email, just a dial tone. getting that first impression right is everything.
          on your question — email converts better for us once captured, but mostly because local service businesses are most comfortable there. SMS gets higher open rates but owners feel it's too casual for quote/booking confirmation. what we see consistently: mirror the channel they came in on. web form lead → email reply. text first → SMS follow-up. don't force a channel switch.
          actually — your insurance broker client might be a good fit for CloseReply on the email/SMS side. you handle the voice capture, we handle the follow-up once they're logged. the broker wakes up to warm leads with context already captured, we keep them engaged until they're ready to talk. could be a tight handoff.
          if you want to test it on that one account, happy to set you up — no cost while you're still in early validation mode. check us out at closereply.com or drop me a line at [email protected]

          1. 1

            Really appreciate the offer, Sagar — and the handoff logic is genuinely clean (voice captures, you keep them warm until they're ready to talk). Full honesty though: that specific broker is probably about to churn. Turns out their call volume is too low to justify the spend, so they'd be a weak test case right now, not a fair shot for either of us. But the voice → follow-up handoff is exactly what I'll want the moment I land a client that's actually drowning in leads (clinics, trades). Let's keep this thread warm — when I've got an account with real volume I'll ping you at that email. Rooting for CloseReply in the meantime.

            1. 1

              appreciate the honesty — and that's the right call. testing on a low-volume account would just give you bad signal on both sides.
              clinics and trades are exactly the right fit for this. when that account lands, you'll know. I'll be here.
              good luck with the build — following along.

  3. 1

    I think an auto-reply is enough for most after-hours leads, as long as it sets clear expectations.
    Something like “Thanks, got your message — I’ll reply first thing in the morning” is better than silence, because the lead knows they were heard.
    For urgent leads, though, speed probably matters a lot. A plumbing or HVAC lead at night may contact 3 people and go with whoever replies first.
    So I’d probably do both: instant acknowledgement, then personal follow-up as soon as possible. Fast response helps, but it still has to feel human.

    1. 1

      you've got the framework exactly right — acknowledgement + human follow-up as fast as possible. that combo beats both silence and a robotic instant reply.
      the piece most local businesses miss is the middle: the auto-reply says "I'll get back to you" but then nothing happens for 8 hours. lead goes cold. the acknowledgement set the expectation but nobody closed the loop.
      what CloseReply does is fill that gap — the instant reply isn't just "got it, talk tomorrow." it actually continues the conversation: asks what the issue is, what area they're in, how urgent. by the time the owner wakes up, the lead has already self-qualified and feels like they've been talking to someone. so the morning follow-up feels like step 2, not a cold start.
      still has to feel human — 100% agree. that's the whole product bet: if it reads like a bot, trust is gone before the owner even sees it.

      1. 1

        That’s a good point. The middle step is where the real value is.
        A basic auto-reply only says “we saw your message,” but it doesn’t move the lead forward. Asking a few useful questions while the person is still interested makes the morning follow-up much warmer.
        I also agree that tone matters a lot. If the first reply feels robotic, it can damage trust immediately. The best version probably feels like a helpful receptionist, not a chatbot trying to close the sale.

        1. 1

          "a helpful receptionist, not a chatbot trying to close the sale" — that's exactly the brief we give the AI. the goal isn't to convert at midnight, it's to make the 9am call feel like step 2, not a cold start.
          the questions matter too. not a form — a conversation. "what's going on with your AC?" lands very differently than "please describe your issue." same information, completely different feel.
          that's the whole product bet at CloseReply (closereply.com) — if the after-hours reply reads like the owner typed it, trust is built before the human ever picks up the phone.

  4. 1

    I set up an auto-responder that says "thanks, I'll get back to you within 24 hours" and then batch-process all leads first thing in the morning. It sets expectations without promising instant replies. For urgent ones, I have a Telegram bot that notifies me, but that's rare. Most people are fine waiting a few hours.

    1. 1

      solid system — setting expectations upfront is underrated. most people don't mind waiting if they know you got the message.
      the edge case i'd watch: the "urgent" ones. in home services especially (plumbing, HVAC, locksmith), whoever responds first usually wins the job. the lead didn't just ping you — they pinged 3 other people on Google too.
      that's what pushed me to build CloseReply (closereply.com). not to replace the morning batch for most leads, but to handle that first 5-minute window with something smarter than a generic "thanks, I'll get back to you." the AI qualifies them, asks a follow-up question, keeps them warm — so by the time you review in the morning, they're already engaged instead of gone.
      your Telegram bot instinct is right. the question is just whether you want to wake up for it or let it run itself.

  5. 1

    For most small service businesses I'd guess the answer is "nothing happens" — the lead goes cold overnight and calls a competitor by morning. The response time window for local services is brutal, sometimes just minutes. Curious what you're building to solve this — an AI that responds automatically after hours?

  6. 1

    honestly speed matters way more than people think - a lead that pings you at 9pm is way colder by 9am. i just set a simple instant auto-reply ("got your msg, will get back to you first thing") so they feel acknowledged, then i actually follow up in the morning. that alone stopped a bunch of them from going and finding someone else overnight

  7. 1

    Interesting question. I'm not in the local service industry, but I'd imagine response time has a big impact on conversions. Have you noticed whether businesses using automated replies or AI chat assistants are able to recover more after-hours leads?

  8. 1

    Speed matters more than a complete answer here. When I ran a managed services company we tracked this: the first vendor to respond won the deal far more often than the best one, so even an auto-reply that confirms receipt and books a time slot beats a thoughtful reply eight hours later. The lead at 9pm isn't comparing quotes, they're comparing who answered.

    1. 1

      "the first vendor to respond won the deal far more often than the best one" — this is the stat I wish every local business owner had tattooed somewhere visible.
      you nailed the psychology too. at 9pm they're not evaluating, they're just seeing who's awake. the moment someone confirms receipt and books a slot, the search stops. everyone else is competing for second place.
      that's exactly the gap CloseReply (closereply.com) was built for — instant response that doesn't feel like a bot, qualifies the lead, and locks in next steps before they open a second tab. not trying to replace the human conversation, just making sure you're the one they're already talking to by morning.
      ran managed services yourself — would love to know what channel the fastest-response wins happened on most. email, phone, form?

  9. 1

    For after-hours leads I would separate response speed from response quality.

    If the lead is already high intent, a fast but generic reply can still lose trust. I’d want an auto-triage layer first:

    1. Is this support, sales, partnership, or spam?
    2. Did they mention a specific workflow or budget?
    3. Are they asking for a demo, price, migration, or just information?
    4. What should wait for a human?

    Then automate the first useful step, not the entire conversation. In early-stage SaaS especially, the reply should feel like someone actually read the context.

  10. 1

    The referral angle is worth exploring. A lead who calls and hangs up is different from one who fills a form, but the outcome is the same. They move on. If we set up a simple handoff, voice-captured leads that also have a text channel could flow into closereply's response sequence automatically. What does your integration surface look like? Webhooks, API, or something simpler? Happy to sketch out what the pipeline would look like from our side if you're interested.

    1. 1

      this is exactly the kind of handoff that makes sense. you catch the call intent, we own the text follow-up. the lead never falls through.
      on the integration side — we have a webhook layer that can receive lead data (name, number, source, notes) and trigger the response sequence from there. nothing complex on your end to push to us. if you're already capturing that payload on the voice side it should be a clean connection.
      i'd rather sketch this out properly than guess in a thread. want to jump on a 20-min call this week? i'll show you what the inbound side looks like and we can map the handoff together.
      what timezone are you in?

      1. 1

        Webhook layer on your end makes the handoff straightforward. We can push the payload from our side and your sequence picks it up from there. I'm GMT+2. Let me loop in Mohannad for the call. He built the voice side and can map the handoff better than I can in text. I'll have him reach out with some times that work.

        1. 1

          perfect — webhook handoff is exactly how I'd want to connect it too. clean and simple.
          loop in Mohannad whenever he's ready. I'm flexible on timing, just have him ping me at [email protected] with a few slots and we'll find something that works across time zones.
          looking forward to it.

          1. 1

            Just sent Mohannad's email over. he included a Calendly link so you can grab whatever slot works best on your end, no back-and-forth needed. Looking forward to mapping this out.

      2. 1

        Honest answer: right now it's one broker — my first real client — so I'm resisting the urge to call it a product yet. But you're reading it right: I'm building it as a template, not a bespoke service. Insurance intake repeats a lot across agencies (claim vs. renewal vs. quote, same required fields), so the plan is to harden it on this one account until the flow is boringly reliable, then replicate. The rule I'm holding myself to: don't productize until the same thing has worked for 3-4 businesses with the same pain, or it's just a service wearing a SaaS costume.

        1. 1

          that rule is sharp — "don't productize until it's worked for 3-4 with the same pain, or it's a service wearing a SaaS costume." saving that one.
          insurance intake is a great wedge too. repetitive, high-stakes, and the agencies are notoriously bad at follow-up. once you hit that 3rd or 4th client, the pattern will be obvious.
          we went through the same thing with CloseReply — built it for one HVAC guy, then realized every local service biz had the exact same after-hours lead problem. that repetition was the signal.
          curious — are you handling the intake via email, SMS, or web form? the channel matters a lot for where the drop-off happens.

  11. 1

    [email protected] — shoot me a message, would love to hear where your thinking goes on this. happy to show you what the dashboard looks like with real data too if that's useful.

  12. 1

    voice is interesting — we're email + SMS for now, but the pain point is identical. the lead doesn't care what channel, they just care who responds first.

    what's the split between calls vs texts/emails for your broker? wondering if the after-hours window is heavier on one channel or pretty even.

  13. 1

    great question — right now closereply nails the first 60 seconds (stops the bleed before the lead even considers a competitor). follow-up sequences are on the roadmap though.

    honestly the "goes cold after the quote" pattern you're describing is something we hear constantly. first reply buys you the conversation, but if nobody owns the follow-up date it still dies. what are you testing on that side? genuinely curious what's working.

  14. 1

    This is close to what I’m testing with local service businesses. The first reply matters, but I’m seeing the bigger leak happen after the first quote or site visit. A lead can come in after hours, but it can also go cold three days later because nobody owns the next follow-up date. Curious if you’re solving only speed-to-lead, or also what happens after the first reply?

    1. 1

      right now closereply focuses on the first reply — that 60-second window that stops the lead from calling the next guy. follow-up sequences are on the roadmap.
      but the "goes cold after the quote" thing you're describing is the second big leak and honestly just as painful. first reply buys you the conversation, but if nobody owns day 3 it still dies quietly. what are you testing on that side? genuinely curious what's working.

      1. 1

        That’s exactly how I’m thinking about it too. First reply buys the conversation. But quote/site-visit follow-up decides whether the conversation turns into money. Right now I’m testing a very small version with local quote-heavy businesses: UPVC/window, aluminium/glass, interiors, painting, solar. The flow is simple:

        1. ask how they currently track quote/site-visit follow-up
        2. if it’s mostly WhatsApp/call memory, show a tiny demo
        3. demo is not “CRM” first — it’s:
          • lead status
          • quote/site visit stage
          • next follow-up date
          • “follow-up due today”
          • 3 WhatsApp follow-up messages
            The framing I’m testing is: “Never forget the next quote follow-up.”
            Still early, no big conclusion yet. But the signal quality changes when someone asks about demo, running cost, or what’s included. “Send it” is weak. “What system do you offer?” is much stronger. Curious for CloseReply: when users ask about follow-up sequences, are they thinking generic drip messages, or stage-based follow-ups after quote/site visit?
        1. 1

          really clean framing — "never forget the next quote follow-up" is way more specific than "CRM" and that specificity is exactly why the signal quality changes. "what system do you offer?" means they've already fired the old way and it failed them.
          to answer your question directly: CloseReply sits at the top of that funnel — the moment the lead comes in after hours, before a quote even exists. so we're not seeing stage-based follow-up questions yet because we're still in the "did you respond in time?" problem.
          but what you're describing is the logical next layer. we capture and qualify the lead, hand them off warm — and then someone still needs to track quote → site visit → close. right now that gap exists and most of the businesses we talk to are losing deals there too, just a different stage.
          honestly what you're building sounds complementary, not competing. the failure mode you're solving (forgetting the follow-up after the quote) is exactly where our users fall off next.
          curious — are the businesses you're testing with in India? the UPVC/solar/interiors mix sounds like it. if so, the WhatsApp-first flow makes complete sense.

          1. 1

            Yes, exactly. I’m testing this in India, and WhatsApp is the main workflow for most of these businesses. The pattern I’m seeing is: lead comes in on WhatsApp/call, someone replies, quote or site visit happens, then the next follow-up lives in memory, rough notes, or an Excel remark. So the first leak is speed-to-lead, which CloseReply handles. The second leak is after quote/site visit:
            who needs follow-up today, what stage is the lead in, and what message should go next. That’s why I’m keeping the first version intentionally small. Not full CRM, not heavy automation.

            Just:

            • quote/site visit stage
            • next follow-up date
            • follow-up due today
            • last note
            • WhatsApp message templates

            And yes, I agree this feels complementary. If the first reply creates the conversation, the follow-up layer protects the money after that conversation starts. The India/WhatsApp-first market is messy, but that’s also why the problem is visible.

            1. 1

              "the first leak is speed-to-lead, the second leak is after quote/site visit" — that's a really clean way to frame the full funnel. two distinct problems, two distinct tools.
              and you're right that keeping v1 small is the move. "follow-up due today + WhatsApp template" is something a business owner can act on in 30 seconds. that's the right unit of value to prove first before adding anything heavier.
              the WhatsApp-first market being messy is actually the opportunity — these businesses aren't going to adopt a Western CRM. they need something that fits inside the workflow they already have, not a new workflow they have to learn.
              genuinely interesting what you're building. the two problems are clearly connected — if we're both solving different parts of the same funnel, there might be something worth exploring together down the line. feel free to reach out: [email protected]

              1. 1

                Appreciate that, Sagar. That’s exactly the angle I’m trying to validate: not replacing WhatsApp, but adding a simple follow-up layer around the workflow businesses already use. I agree the two leaks are connected but separate: speed-to-lead gets the conversation started, quote/site-visit follow-up keeps the opportunity alive.
                I’ll send you a short email with what I’m testing and where the signal is coming from. Would be useful to compare notes.

        2. 1

          This comment was deleted 12 days ago.

  15. 1

    This is my whole world right now — I run a voice agent for a Spanish insurance broker. The eye-opener wasn't the call volume, it was the timing: a real chunk of calls land outside office hours, exactly when nobody's there to pick up. Before the bot, those were just gone, and the owner assumed it was a quiet day. My honest take on the poll: an autoresponder that only says "we'll get back to you" isn't enough — what wins is capturing the actual details (what they need + a callback number) so the human can pick up warm the next morning. Missing the call is bad; missing the context is worse.

    1. 1

      this is exactly the insight we built around. "assumed it was a quiet day" — that line is the whole problem. the owner doesn't even know to feel the pain.
      and you're right, a generic "we'll get back to you" is useless. closereply does exactly what you described — captures what the lead needs, qualifies them, keeps the context so when you follow up you already know their situation. the human picks up warm instead of cold.
      are you building this for the broker only or productizing it for other insurance agents too? sounds like you're closer to a product than a feature.

  16. 1

    This resonates a lot. After-hours leads don't just get answered late, they get buried under everything else competing for attention the next morning. I built FounderFlow partly because of this exact problem — making sure the lead that actually matters doesn't sit behind 40 other notifications until it's too late.

    1. 1

      totally. the morning pile-up is just as bad as the after-hours gap. lead comes in at 10pm, owner sees it at 8am, already buried under 40 other things — by then they've already called someone else. that's exactly the problem closereply fixes — replies in 60 seconds so the lead never goes cold in the first place. what FounderFlow is solving sounds like the prioritization layer on top. the two together could be deadly for local businesses honestly.
      if you want to see how we handle it — closereply.com, free trial, no card needed.

  17. 1

    This resonates. It's not really a "quiet week" problem, it's a visibility problem, the signal was there the whole time, just buried. I've seen the same pattern with founders running more than one business, except it's spread across email, Slack, and DMs instead of missed calls, so it's even easier to convince yourself nothing important is happening. Building FounderFlow for exactly this reason, curious how many other people here are flying blind across multiple channels without realizing it.

    1. 1

      convince yourself nothing important is happening" — this is exactly it. silence feels like a slow week until you see the data and realize 6 people reached out and moved on without a word.
      we built closereply for local service businesses hitting this exact wall — HVAC, plumbers, dentists, real estate. every lead gets an AI reply in under 60 seconds, 24/7, so nothing slips through invisible. owners check the dashboard and genuinely can't believe what was falling through at 9pm on a tuesday.
      free trial at closereply.com if you're curious. curious how FounderFlow handles the multi-channel noise too — are you scoring/ranking leads or just surfacing everything in one place?

  18. 1

    We work with local service businesses on the voice side at SmartSphere. The after hours gap is the same story on calls, they go to voicemail and most owners don't realize how many people hang up without leaving a message. We track a dashboard showing missed calls vs booked appointments and the gap is always bigger than they expect. Is closereply text-only or do you handle missed calls too?

    1. 1

      the voicemail hangup problem is real — most owners only count the voicemails, not the hangups. and the gap between those two numbers is where all the money is leaking.
      closereply is email + SMS for now — missed calls aren't in scope yet. but honestly what you're doing on voice and what we do on email/SMS is the same problem from two angles. a lead who calls and hangs up at 9pm is the same person who fills out a web form and doesn't hear back. they just move on.
      the dashboard you're building sounds powerful. are you doing outbound callback automation or just the tracking + reporting side? asking because there could be a real referral play here — if a lead hangs up and then fills out a form, closereply catches it on the text side. could be a nice handoff.

  19. 1

    100% this. that's actually the scariest part — most local business owners i've talked to had no idea how many leads they were missing until we showed them the data. they assumed "no reply = not interested." but a huge chunk were just people who moved on to whoever called back first.

    that's the whole reason i built closereply — not just to reply fast, but to make the invisible visible. every lead gets logged, every reply tracked. owners are genuinely shocked when they see what was slipping through at 9pm on a tuesday.

  20. 1

    The interesting question isn't how quickly someone replies after hours.

    It's how many businesses have no idea they're losing opportunities because the missed conversations are invisible. You can't optimize a problem that never gets measured.

    1. 1

      yeah this is the thing nobody talks about. the missed calls, the unanswered texts — they just disappear. the owner assumes it was a slow week. never occurs to them that 6 people already hired someone else.
      i saw this firsthand with an hvac guy in texas. showed me his phone — 11 missed calls from one weekend. genuinely thought business was quiet. every single one had booked a competitor by monday.
      that's literally why i built closereply. not even about speed at first — just wanted owners to finally see what was happening. the dashboard alone changes how people think about their business.
      free trial at closereply.com if you want to check it out. no card, takes like 10 min.

      1. 1

        That HVAC example actually made me think about the business a little differently.

        It wasn't the missed calls that caught my attention—it was what the dashboard changes once owners finally see the pattern.

        I don't think I can explain where that line of reasoning leads properly in a thread without oversimplifying it.

        If you're interested, what's the best email to reach you on?

        1. 1

          [email protected] — shoot me a message, would love to hear where your thinking goes on this. if it's relevant i'm happy to show you what the dashboard looks like with real data too.

          1. 1

            Thanks! I’ve just sent it over.

            Looking forward to hearing your thoughts whenever you have a chance.

Trending on Indie Hackers
I sent 43 cold emails with my own tool. 17 replied. 1 paid. Here’s the unofficial launch. User Avatar 217 comments I built for one user. Myself. User Avatar 78 comments I built a web-based vector editor from scratch and integrated an AI Agent. Need just ONE beta tester! User Avatar 53 comments Why Your Users are Leaving in Silence (and How to Fix the "Leaky Bucket" with AI) User Avatar 21 comments AI prices dropped 97% since 2023. So why are AI bills 3x higher? User Avatar 20 comments Launched 580 landing pages in 1 week. Solo. No team. User Avatar 12 comments