The call comes in while you're under the house.

Yes, by the rules you set. A call that meets your definition of an emergency can be transferred live to whoever is on call, or texted to them with the address and the problem while the caller is told what happens next. It never promises an arrival time you didn't give it.

Only what you approve: a service-call fee, a starting-from figure, a range for a common job. Anything beyond that becomes a booked estimate rather than a guess. The pricing it can say out loud is a list you write.

It books real slots on the calendar it's connected to and texts the caller a confirmation. Field-service tools are handled by integration where one exists; otherwise the booked slot and the job details land with you by text and email, which is what most crews actually read.

Each of them gets answered. There's no hold queue and no busy signal, because it isn't one person at one desk. That's the whole difference on the first hot week of summer.

Yes, in its first sentence, on every call. People forgive a robot for being a robot; they don't forgive it for pretending. It's in FWA's privacy policy, and I won't configure it otherwise.

Call the demo line and judge for yourself. That's what it's for. It's a natural voice having a real conversation, and it says it's an AI assistant in its first sentence. People forgive a robot for being a robot; they don't forgive it for pretending.

It books: real slots on your real calendar, with a confirmation text to the caller. Message-taking is the fallback, not the product. Booking, transfers, and texts are configured per build, around the tools you already use.

Yes. Your existing number forwards to the receptionist, so customers dial what they've always dialed. A new dedicated number works too.

Setup is $200, one time. Monthly service starts at $50, based on call volume, with the number, answering, booking, summaries, and ongoing tuning included. Month to month, cancel anytime, keep your number.