● Magic Receptionist
USE CASE / OUTBOUND

Inbound was the start. Outbound is the lever.

Every shop has a list of warm leads they never followed up on - estimate-only customers who didn't book the repair, no-shows from last week, lapsed customers from 18 months ago. The lead-gen agent calls them, runs a structured script, and only escalates to a human when the prospect engages.

Three campaigns we run by default

Estimate-no-book win-back.

Pulled an estimate but never came back? The agent calls 7-14 days later, asks if they're still deciding, offers to book the slot.

No-show reschedule.

Booked a slot, didn't show? Agent calls within 24 hours, captures the reason, books the next slot - no friction, no shame.

Review request.

3-7 days post-pickup, the agent calls happy customers, asks for a Google or Facebook review, and texts the link if they say yes.

Compliance + caller-ID

Outbound calls only run against contacts who consented to be called (existing customers, not cold lists). Caller-ID matches the shop's local number. The agent identifies as a virtual assistant calling on behalf of the shop in the first sentence. We don't run robocalls and we don't run cold lists - this is post-purchase and re-engagement only.

How the list comes in

CSV upload from your CCC One / RepairShopr export, or push-API from your own DMS. The agent works the list across business hours, then hands warm responses to your team in the same inbox the inbound calls land in.

Start the intake → All use cases