Turn missed calls into booked jobs.

It answers inbound calls, identifies what the caller needs, asks the qualification questions you've defined, checks whether the job fits your service area and rules, offers real appointment windows, books the job, updates your calendar and CRM, and sends your team a short summary. Anything outside those configured rules gets escalated rather than improvised.

One credit covers up to three minutes of an AI Receptionist call. Start Small includes 50 credits and additional credits are $1.75 each. The Managed AI Receptionist plan includes 200 credits, with additional credits at $1.50. Most routine bookings finish inside a single credit, and each call shows the credits it used alongside its summary.

When your included credits run out, nothing is cut off: calls keep being answered at your plan's additional-credit rate, billed automatically to your card. There is no hard cap — your phone line never goes dark mid-month — and per-call usage stays visible so the bill is never a surprise.

Standard setups go live in 3–5 business days: discovery, configuration, a test cycle you review, then connection to your number. Custom workflows, unusual integrations, or multi-location businesses take longer — we give you the real timeline before you commit rather than after.

Yes. It checks availability in your configured calendar workflow and books qualified jobs into it while the caller is still on the line — using your arrival windows, buffer rules, and any slots you hold back for diagnostics or emergencies.

Standard connections to systems like Housecall Pro, Jobber, ServiceTitan, Google Calendar and Calendly are part of the managed setup, along with CRM record updates and webhook or API connections. Unusually complex implementations — deep multi-location routing, non-standard data models, or systems with no API — are scoped under Custom / Advanced Setup. We confirm exactly what your business uses during onboarding.

It follows the escalation path you defined during setup. When a call falls outside its configured rules, it recognizes that, tells the caller plainly instead of guessing, collects the details a person will need, and routes or summarizes the request to the right team member. Safety situations and commercial accounts are common escalation triggers, and you decide what else belongs on that list.

Calls are recorded, transcribed and summarized — that is how the AI books the job, updates your records, and hands off cleanly when a person takes over. A recording and consent disclosure can be configured into the opening of every call flow, which matters because several US states require all parties to consent. We agree the exact disclosure wording with you during onboarding.

Yes. Language handling is part of configuration — including which languages to support and whether it should switch automatically when a caller starts speaking another one. The call summary tells you which language was used.

No. A phone bot answers and reads a script. An AI employee completes the operational workflow — qualifying the lead, booking the job, updating your records, and telling your team what happened. And it's managed: LScale designs it, tests it, launches it, and keeps tuning it based on real calls. Voice is where we start, not the whole model.

Yes, by consultation. The packaged AI Receptionist covers the common home service call patterns. Beyond that — unusual booking logic, additional systems, or AI employees working in chat, email, or your CRM — we scope it with you first and tell you honestly whether it's a good fit.

The part that matters to your business is the managed layer around it. LScale handles setup, configuration, testing, launch, tuning, reporting, and escalation rules — and stays accountable when something needs to change. We select and maintain the underlying technology so you don't evaluate, integrate, or babysit it, and we update it as better options appear without you having to rebuild anything.