From Signed to Live in 48 Hours: Here's What Happens

Most contractors assume setup is a project. It's not. Your only job is to hand us three things and then get back to running your business.

1. Call forwarding activation. You forward your existing business number to us. On most cell carriers, that's a 30-second code you dial. We send you the exact string to enter — copy, paste, done.

2. Calendar access. We need read/write access to the calendar you actually use to schedule jobs. Google Calendar, Outlook, or a field-service app — if it has an integration option, we connect it. If it doesn't, we set up a simple shared calendar and sync it to yours.

3. Your service list and coverage area. Tell us what you do (plumbing, HVAC, electrical, drain cleaning — whatever applies), what zip codes or counties you cover, and which jobs are true emergencies versus standard next-day calls. A five-minute voice note or a quick email works fine.

That's it. No forms to fill out, no software to log into, no training calls. We do the rest. Most owners spend under 20 minutes total on their end of this process.

The moment your onboarding is confirmed, our team starts the build. You won't see any of this — you'll just see the result.

Call routing logic. We configure which calls ring through to you immediately (true emergencies: burst pipe, no heat in winter, electrical panel trip) versus which ones the AI handles end-to-end and books straight to your calendar.

Trade-calibrated qualifying scripts. A plumbing call sounds different from an HVAC call. An emergency drain call at 11 PM sounds different from a water heater replacement inquiry at 2 PM. We write the qualifying questions specifically for your trade and your job types — not a generic "how can I help you?" loop. The AI knows to ask the right follow-up: when did it start, is water actively leaking, is the system completely out, how old is the unit.

Emergency escalation rules. We set hard thresholds for when the AI stops handling the call and routes it live to your cell. You define the line — we enforce it automatically, 24/7, including weekends and holidays.

After-hours behavior. After-hours calls get a different script than business-hours calls. We configure the exact hours you want each mode to run and what the AI offers during each window.

By hour 8, the core system is built and ready for the next phase.

With the core system built, hours 8 to 24 are about making it work with your real-world schedule and catching anything that needs adjustment before test calls begin.

Calendar integration confirmed. We run a live booking test against your calendar to confirm jobs land in the right slot, conflicts are blocked, and the confirmation SMS fires to the customer immediately after booking. If your calendar has any quirks — blocked times, buffer rules, multi-tech scheduling — we account for them here.

Business-hours and after-hours routing confirmed. We verify the time-of-day triggers using your local timezone. A midnight call in Phoenix should behave differently than a midnight call in Miami if your coverage windows differ.

Script refinement pass. We review the qualifying scripts for tone and accuracy — does the AI use the right terminology for your trade, does it handle "I don't know" answers without breaking, does the emergency path trigger at the right threshold. If you want to review the script text yourself at this stage, we send it over and you reply with any changes.

To understand what your AI Receptionist handles on every inbound call — from lead qualification to booking confirmation — review the full product breakdown before your go-live.

By hour 24, the calendar is live, the scripts are locked, and the system is ready for QA.

No system goes live without running every scenario we can throw at it. This phase is purely QA — you don't need to be involved unless you want to listen in.

We run test calls across four call types:

• Standard booking call — a new customer calling during business hours, requesting a non-emergency service. The AI qualifies, books, and fires the confirmation.
• Emergency call — a caller describing an active problem (burst pipe, no heat, gas smell). The AI escalates immediately to your cell.
• After-hours call — same scenarios, but triggered after your business-hours window closes.
• Out-of-service-area call — a caller from outside your coverage zone. The AI declines politely and does not book a job you can't run.

We run a QA checklist against every test: Did the call answer within two rings? Did qualifying questions fire in the right order? Did the booking land on the calendar? Did the escalation SMS reach the owner's cell? Did the confirmation text reach the test customer number?

You approve before we go live. If anything in the QA results needs a change, we fix it and re-test before flipping the switch. There is no go-live without your sign-off.

Day 3 is the simplest day of the whole process — for you.

Call forwarding is active. The next inbound call to your business number hits the AI Receptionist. If it's a bookable job, the customer gets qualified, the appointment lands on your calendar, and you receive an SMS: job type, customer name, time, address.

You don't log in anywhere. You don't check a dashboard. You look at your calendar and see a booked job you didn't have to answer a call to get.

If it's an emergency, your cell rings. You answer it the same way you always have — except now the AI has already gathered the customer's name, address, and problem description before routing to you.

That's the live handoff. The system is running. You're already recovering revenue you were losing to voicemail. Start your onboarding today and your phone is live before the week is out.

Going live is not the end of our job. The first 30 days are when we do the most active optimization work.

Weekly call review. We listen to a sample of actual calls from your line every week. If the AI is stumbling on a question type, mispronouncing a trade term, or missing an escalation it should have caught, we fix the script and push the update — no action required from you.

Real-data script adjustments. Test calls simulate scenarios. Real calls reveal the weird stuff — customers who give partial addresses, callers who describe emergencies in non-obvious ways, calls that come in during edge-case hours. We adjust based on what's actually hitting your line.

Direct escalation path. If something breaks — a call that should have booked didn't, an escalation that should have fired to your cell didn't — you contact us directly. Not a ticket queue, not a chatbot. We have a dedicated point of contact for every active account.

Performance check at Day 30. We pull call volume, booking rate, and escalation data and send you a plain-English summary: calls answered, jobs booked, emergencies routed. If you're not tracking toward the $5,000 recovered threshold by Day 30, we tell you what we're doing to close that gap before Day 60.