The First 60 Seconds of a Lead

The whole case for an AI front office rests on what happens in the first minute. Not the features. The minute. A lead calls, texts or fills out a form, and either a conversation starts that ends in a booking, or it doesn't. Here is what that minute looks like, second by second, when an AZMUTHE front desk is on the line.

Second 0: the lead arrives

A call comes into your business line. Or a text. Or a web form. Or an Instagram DM at 9:40 PM. Every one of those lands in the same place and is treated the same way: a lead that needs a conversation now. There's no queue, no hold music, no "we'll get back to you." If three arrive at once, three conversations start.

Seconds 1 to 3: the answer

On a call, the AI Assistant picks up on the first ring with your business name and a greeting that sounds like your front desk, because it was trained on how your front desk talks. On a text or a form, the reply goes out in seconds, and it reads what the lead wrote: "Hi Maria, got your note about the AC not cooling upstairs."

That first response is the moment the lead stops calling other companies. Research on buying behavior is consistent that the first to respond usually wins, and the difference between three seconds and three minutes is the difference between first and third.

Seconds 3 to 20: what's going on

The Assistant asks what's happening and listens. It knows your services, so it recognizes the job: a tripping breaker is a same-day service call; an EV charger install is an estimate; a consult for a treatment series is a consult. It knows your triage rules, so a burning smell gets flagged urgent and a flickering light gets scheduled normally.

It captures what you'd want captured: the address, the property type, whether it's an existing customer, the insurer if there is one, photos if that helps. Nothing is asked twice.

Seconds 20 to 35: the first objection

Most leads have one question before they'll book. "Do you charge for the estimate?" "Are you on my insurance program?" "How much is a service call?" "Do you do Saturdays?"

The Assistant answers with what you've approved it to say. Not a made-up number, not a dodge. Your actual policy, in your words. If the question is outside its rules, it says so honestly and offers to have a person follow up, with the context attached.

Seconds 35 to 50: the booking

This is where it stops being a receptionist and starts being a front office. The Assistant reads your real calendar, applies your rules (zones, drive times, which tech does what, which provider does consults on which days) and offers actual times. "I've got tomorrow between 1 and 3, or Thursday morning. Which works?"

The lead picks. The appointment is created in your calendar or dispatch board. Not a scheduling link, not a "someone will confirm." Booked.

Seconds 50 to 60: the confirmation and the record

A confirmation text goes to the lead with the time, the address, the tech's or provider's name, and anything they need to prepare. The lead's details land in your CRM as a record with a source, a job type and an outcome. Tomorrow morning, this lead appears in your brief as one line: came in 9:40 PM, web form, booked for Thursday.

Sixty seconds. The lead you paid for is on the calendar.

What happens when it doesn't fit the script

Not every minute goes this cleanly, and the design accounts for it:

• The lead wants a human. Handed off immediately, with the transcript, to whoever's on call.
• The job is outside your service area or rules. Captured, declined politely if you've said to, or escalated to a person if it's a judgment call.
• The lead isn't ready to book. Details captured, a follow-up scheduled, and the Closer takes it from there if there's an estimate involved.
• Something can't be undone. A refund, a cancellation of someone else's slot, a deposit. It asks before it acts. It never moves money without your say-so.

Why the minute matters more than the feature list

A front office can have every feature and still lose the lead if the first minute is slow. The reason to measure this in seconds is that the customer is measuring it in seconds: they have three tabs open and a phone in their hand. Every second you're not answering is a second someone else is.

For the older overview of how the phone side works, see how AI phone answering works. For what happens after the first minute, when an estimate is involved, see the open-estimates playbook.

Frequently asked questions

Does the lead know it's an AI? It says what it is when asked and never pretends otherwise. What most leads notice is that someone answered instantly and booked them.

What if my calendar rules are complicated? They're built in during the build. Zones, drive-time buffers, which tech handles what, provider schedules. The Assistant books the way your dispatcher would.

Can it handle two calls at once? Any number. There's no line and no busy signal.

What if it makes a mistake? Every action is logged and readable, and anything it can't undo it asks about first. Mistakes are visible in the brief the next morning and fixed in the build.

Bring one recent lead you know you lost. We'll walk through what the first sixty seconds would have looked like. See if you qualify.