Forum Discussion

muqeet's avatar
muqeet
Contributor 2
3 days ago

Jobber users how are you handling new requests that don't respond after the first contact?

Do you leave them sitting in New until they respond, archive them, or have some kind of process for keeping the request list clean?

I'm curious how other service businesses are handling this, especially when you have a lot of incoming requests.

What does your process look like?

2 Replies

  • HUGEHomePros's avatar
    HUGEHomePros
    Verified Community Coach

    They should be put in some sort of nurture sequence. Where you are at least texting and emailing every couple days for a month. If they respond, they get dropped in another category that kicks them out of the sequence. The Jobber pipeline is great for this. I use GHL because the automations and sequences is really good. It can work to super charge jobber not replace it. 

  • I’d avoid treating those requests as simply “new” or “archived.”

    I’d give each one a simple status:

    • New — first contact not yet completed
      • Contact attempted — waiting for a response
      • No response — follow-up attempted but still silent
      • Qualified — conversation started and need is confirmed
      • Won / Lost — clear outcome

    The part I’d really want to track is the value sitting in the “no response” bucket.

    For example, if you have 20 unanswered requests worth $X in potential work, that tells you much more than simply knowing how many requests are sitting in “New.”

    It also helps separate a follow-up problem from a lead-quality problem.

    I’m curious whether you’re currently tracking the dollar value and age of those unresponsive requests, or mainly just their status in Jobber?