Skip to main content
Magic Receptionist
Contact Us

AI receptionist for auto body shops

Turn missed and overflow calls into actionable collision leads.

Inbound AI call coverage that uses approved business facts, captures collision intake, and records the caller's requested next step for the shop team.

Start a fit review Try the demo

Core call-handling output

  • AI disclosure and approved business identity
  • Caller, vehicle, damage, carrier, and drivability intake
  • Estimate or callback request capture
  • Structured lead and call evidence
  • Configured routing and escalation under the shop's approved rules

Built around the body-shop call

Capture the facts your estimator needs before the callback.

This knowledge hub explains how an AI receptionist can collect approved collision-intake details such as caller contact information, vehicle and damage context, carrier information when provided, drivability, and the requested estimate or callback next step. Exact routing, notifications, photo workflows, booking actions, and integrations depend on the plan and workflow that are actually configured for the shop.

Clear, source-bound answers support SEO discovery, GEO discovery, and AEO answer engines; the operational workflow is confirmed during setup.

How it works

A controlled path from inbound call to the business's configured next step.

Magic Receptionist does not assume every business has the same booking, transfer, SMS, CRM, or escalation setup. The operating path is verified during onboarding and changed deliberately.

  1. 01

    Caller reaches the AI path

    The receptionist answers when the business's configured forwarding, coverage, or direct-number path sends the call to Magic Receptionist.

  2. 02

    AI captures the reason

    It follows the configured intake, asks the approved questions, and records caller context without inventing business facts.

  3. 03

    Requested next step is recorded

    Booking, callback, transfer, or other next-step requests are handled only through the workflows the business has actually configured.

  4. 04

    The team gets the configured handoff

    Structured call results, email, SMS, webhook, or other downstream delivery happens only where that destination and channel are configured and verified.

Configured capabilities

Start with Magic Receptionist. Add downstream automation when it is supported, configured, and verified.

Core

Inbound AI answering, disclosure, approved facts, collision intake, next-step capture, lead evidence, monitoring, and controlled routing.

Optional configuration

Email and reporting are included where supported and configured. SMS notifications and CRM connections are separate optional workflow add-ons. Photo intake, calendar actions, management-system connections, and other downstream capabilities depend on supported, verified configuration.

What body shop owners ask

Long-form answers to the questions you actually have.

Pricing fits on a card; the rest doesn't. Real questions, real answers — the kind you'd ask another shop owner who already runs this.

How is Magic Receptionist different from an answering service?

A traditional answering service may primarily take a message. Magic Receptionist can follow a configured auto body shop intake workflow and return structured context to your team, so the next action is clearer. The configured script, available integrations, and human escalation path determine how far each call can go; some calls will still need a person to complete the next step.

What happens at 7 AM on a Monday when 12 calls hit at once?

During peak periods, the configured voice setup can handle concurrent calls within its provider and account limits. Capacity depends on the deployed configuration rather than an unlimited-call promise. Each completed call can collect the approved intake fields and leave structured follow-up context for your team.

How does it handle insurance carrier questions like "do you work with Geico?"

The receptionist can collect the carrier name and other insurance context the shop has approved for intake. It should only answer carrier-specific questions from the configured script or verified shop policy. Deductible, coverage, repair-authority, or dispute questions that are not configured should be left for the shop or insurer to answer.

Will this damage our customer relationships if it sounds robotic?

Voice tone and script behavior are configured for the business and should be tested before launch. The assistant can disclose that it is an AI assistant, follow the approved intake flow, and hand off or create a callback path when a conversation is sensitive or outside scope. We do not rely on unsupported claims about caller preference or satisfaction.

Can I keep my existing phone system, or do I have to migrate?

In many setups you can keep the existing business number and system by using a supported forwarding or routing configuration, but the exact method depends on the carrier or phone platform and must be verified during setup. Your existing CRM, PMS, dispatch, or case-management system remains in place unless a specific integration has been configured and tested.

FAQ

What body shop owners ask before they sign up.

The 8 questions we hear most. Pricing, setup, security — all answered up front.

What is Magic Receptionist?

Magic Receptionist is an AI receptionist for auto body shops. It can answer the configured phone path, collect caller name, contact details, vehicle or damage context, insurance information when relevant, and the requested next step, and give your team structured context for follow-up. Exact routing, notifications, booking actions, and integrations depend on the plan and workflow that are actually configured.

How much does it cost?

See /pricing for the plans and prices currently offered. Checkout availability, billing cadence, included usage, and usage rules are determined by the plan that is actually available at checkout. Reseller, multi-location, unusual-integration, and other non-standard requirements may use a separate fit review or written terms.

How long does setup take?

Setup depends on the selected plan, phone routing, and the workflow you want configured. We confirm the business details, intake fields, call path, and escalation rules, then verify the configured flow before you rely on it. No specific go-live time is promised unless it is stated in current written terms for your setup.

Which calls does the AI handle vs my human team?

Magic Receptionist handles the call types and coverage windows configured for your auto body shop workflow. It can collect approved intake details and leave a clear next step for your team. Calls involving carrier, estimate, or repair questions outside the configured script, or callers who need a person, should follow the callback or escalation path configured for that tenant.

What integrations does it support?

Available connections depend on the selected plan and configured setup. The current product supports verified HTTPS webhook delivery and a Zapier-compatible webhook path for supported events, and applicable plans can use email notifications. Do not assume a native third-party integration, SMS workflow, or calendar write unless it is explicitly shown as available and configured for your account.

Do I sign a long-term contract?

The current checkout and applicable service terms govern billing cadence, renewal, cancellation, and any data-retention commitments for the plan being purchased. Reseller, multi-location, and other non-standard scopes may use separate written terms. Review the billing and service terms presented for the plan you are purchasing.

What's the fair-use policy?

Included usage, overage treatment, and acceptable-use limits are governed by the current plan and /legal/aup. Use the pricing page, checkout, and current acceptable-use policy for the plan you are selecting.

Is customer call data secure?

Magic Receptionist uses authenticated access and platform security controls for customer data. Exact storage, retention, access, and deletion terms depend on the current service configuration and applicable privacy or service terms. The current privacy and service terms for the deployed workflow are the authority for those details.

Start with one shop and one controlled call path.

Coverage, intake facts, routing, notifications, integrations, and commercial terms are confirmed during onboarding and any required setup review.

Start a fit review