SibiFirewood, the tension you're describing is exactly where most family firewood / hardscape crews get stuck, and your husband's instinct is directionally right. What a lot of people miss is that the problem isn't really "AI" vs "a person" — it's "no one answers after 4 rings" vs "someone with a real timeline." Rural, relationship-driven customers will tolerate a lot, including a recorded greeting that asks for the address and what they need, as long as they still feel like they're talking to you and not a call center.
Two things from the replies worth locking in before anything else. First, roselvaggio's ring-first idea (let the line ring to you or your team 3–4 rings and only drop to the AI when you're truly tied up) is the pattern that keeps the personal connection intact. That's the setup that protects you on the relationship side. Second, HilltopAdOS is right about framing: if the first thing they hear is "I'm an AI," they're deciding whether to hang up before they know what you do. The callers who stay are the ones who hear the task before the identity — "thanks for calling [business], what's the address and what do you need help with today?" — and only find out it's automated if it comes up.
A few practical layers on top that keep you from missing calls without trading away the connection:
1) Write a voicemail greeting that works even if you never turn the AI on. "You've reached [business]. I'm on the loading dock / out on a delivery right now. If this is time-sensitive leave your address and I'll call you back within the hour during business hours, or first thing in the morning after hours. You can also text this number and I'll get right back to you." The greeting sets the expectation, names the callback window, and points to a text-back as the fast path — none of which requires AI, and it works the same for the caller who wants a person and the one who just wants their order taken.
2) Auto-text the missed call inside 60 seconds, with a question in it. "Hey, this is [you] at [business]. Looks like we crossed — what do you need and what's the delivery address? Reply with the details and I'll call you back with a price." A question keeps the reply rate high and gives you the address and volume before you dial, which is what turns a missed ring into an order instead of a "we'll get back to you" that cools. Most phone apps on the market (and Jobber's own missed-call follow-up) can do this without a third tool.
3) Set one call-forwarding rule by time so you're not surprised at home. Business hours: main number rings your work phone, then the office line, then voicemail. After hours and on days you don't deliver: main number goes straight to the greeting plus the missed-call text, not to a personal cell that's sleeping. A separate on-call number for true emergencies (storm damage, delivery to a commercial site at close) keeps the family line quiet on a Tuesday night when the call is really just "when do you open in the spring?"
4) Use a Jobber online booking / request form as the off-hours fallback instead of relying on a live voice. Put the link in your voicemail greeting, in your Google Business Profile "Request a Quote" button, and on the website. Same fields you'd capture on a live call: delivery address, what they need, how much / how often, photos of the stack or the drop-off spot, best time to be home. The rural customer who calls at 8pm because the truck just offered a price can drop the request into the form, and in the morning it's sitting in Jobber with the address and the scope — no voicemail transcript to decode, no "I think they said they wanted the split kind."
5) Keep the AI in the overflow/after-hours lane only, and test its failure handling, not how human the demo sounds. If you do run Jobber's AI Receptionist, scope it narrow: it takes the address, what they need, and how many cords or tons, then writes a callback task or booking into Jobber. What matters is what it does when a caller says something it hasn't been trained on — a bulk commercial order, a split-firewood-vs-pet-coal question, a "we also do land clearing" — does it hand off to a human inside the call, or does it keep asking and make the caller feel like they're on hold? Turn the "I'm an AI" disclosure off if it's causing the hang-ups you're hearing, and run it only on overflow rings so the relationship callers still reach you directly.
6) Give a real opt-out early. "If you'd rather talk to a person, just say 'operator' / 'person' and I'll page [you]." For a conservative, relationship-first base, an easy escape valve is often what keeps them from hanging up entirely.
You don't have to pick between not missing calls and not sounding like a call center. The voicemail greeting plus the text-back plus a request form covers the missed-call problem today. The AI, if you want it, only has to be better at the overflow rings it's scoped to than voicemail already was. Start with the greeting and the form, see what actually gets logged over 30 days, and only add the AI where the gaps show up.
