How to Move From a Human Answering Service to AI Answering: A 7-Day Plan

Moving from a human answering service to AI answering comes down to doing three things in the right order: find out exactly how and when your current contract ends, make sure you control your phone number, and run the AI on part of your calls before you move the rest. A week is enough to set up, test and run that first live slice. Your old service may still need to stay on through its notice period, and a number that has to be ported out can add time, so the plan below keeps both running until the switch is safe.

Key takeaways

• The contract sets your real end date. As of October 2026, Ruby's FAQ says a cancellation outside an introductory period is effective at the end of the then-current monthly billing period, and Smith.ai's AI receptionist page says "If you ever cancel, we need 30 days' notice".
• Find out who controls your number. If you forward calls to the service, switching is a forwarding change. If the number was ported to them, you'll need to port it out first; FCC rules require carriers to complete simple ports within one business day.
• Run both for a few days. Put the AI on one slice of calls, such as after-hours, and leave the human service on the rest.
• Measure both the same way: complete messages, time to callback, booked jobs and complaints. Don't trust anyone's benchmark, including ours.
• Don't let calls drop during the switch. Google's Local Services Ads help page says "Missed calls may negatively affect your responsiveness."
• Keep a rollback written down until the old service has actually ended.

What decides your timeline before day one?

Four checks decide whether this is a one-week job or a longer one. Do them before you touch the phones.

Cancellation terms. These differ by vendor and plan, so read yours. Two examples, as of October 2026: Ruby's FAQ says you cancel by phone or email, and that outside a money-back or trial period, "your cancellation is effective at the end of the then-current monthly billing period." Smith.ai's AI Receptionist pricing page describes a month-to-month service and says "If you ever cancel, we need 30 days' notice, and then you're done." If you're on an annual contract, look for auto-renewal dates and early-termination terms.

Who controls the number. There are three common setups:

1. You forward your number to the service. The number stays with your carrier. Switching means pointing the forwarding at the AI instead.
2. The number was ported to the service. Ruby's FAQ, for example, says "Oftentimes you can even port your number to Ruby, and we can host it for you." If that's you, the number has to be ported to your new provider or back to a carrier before the old service ends.
3. Your listings show the service's number. If your Google listing or ads show a number the service owns, fix that first. Google's guidelines say "The phone number must be under the direct control of the business" (Google).

Your data. Export the messages, call logs and any recordings you want before the account closes. Ask the vendor how long they keep data after cancellation, and get the answer in writing.

What does the 7-day plan look like?

This is a suggested plan, not a vendor promise. The days are a sequence; if a step takes longer, the next one waits.

Day 1: paperwork

Answer four questions in writing: when can the old service end, who controls the number, what data you're keeping, and what the receptionists are told to do on each kind of call. Don't give notice yet unless waiting would cost you another full billing period; you'll know far more by day 7. If the number has to be ported out, start gathering what the new provider needs. T-Mobile's transfer page, for example, asks for a "Number transfer PIN," the account number and the billing ZIP code, and warns "do not cancel your account until after the transfer process has been completed." Treat any port the same way: the old account stays open until the number has moved.

Day 2: build the AI from what already works

Your current service's instructions are a ready-made setup sheet. Turn each instruction into either an answer (hours, service area, payment methods, licensing) or a rule (who gets lockouts after 9 p.m., what to say about prices, when to transfer). Write the greeting with your business name first. If the AI records calls and your old service didn't, add a recording notice: federal law allows recording when "one of the parties to the communication has given prior consent" (18 U.S.C. § 2511), but Washington, for one, requires "the consent of all the participants in the communication" (RCW 9.73.030). This is not legal advice; our call-recording consent guide covers the states.

Day 3: test the calls your service handles most

Use your old service's call log to pick the tests. If half your calls are lockouts and a fifth are price shoppers, test those first. Add the calls that are easy to get wrong:

• A caller asking for a receptionist by name. Long-time customers may ask for the person they're used to. The AI should take the message without pretending to be that person.
• An existing job. "Where's my technician?" should become a message for the dispatcher, not a new booking.
• A caller who speaks Spanish from the first word. Have a fluent speaker run it.
• A child or pet locked in a car. The National Weather Service says it is never safe to leave a toddler, disabled person or pet locked in a car, so the first instruction should be to call 911.

Our trial test-call script has a fuller list with pass and fail notes.

Day 4: go live on one slice

Pick the slice where a mistake costs least and you learn most. After-hours is the usual choice, because the human service keeps handling the busy daytime calls while you watch how the AI does overnight. How to split depends on how calls reach the service today (next section).

Day 5: score both the same way

Review every AI call from the slice and a matching sample of the human service's messages from the same hours on a recent day. Use the comparison table further down. Look for patterns rather than single bad calls: a word the AI keeps mishearing, a question it can't answer, a message field that's always empty.

Day 6: fix, then widen or hold

Fix what day 5 found, re-run the tests that touch the fixes, and decide whether to widen. A sensible next slice is weekends, then daytime overflow (calls you don't pick up). If something important still fails, hold the slice where it is. Waiting costs you a few days; cutting over too early costs you customers.

Day 7: decide and write it down

You have three choices:

1. Cut over. Move all forwarding to the AI, give notice to the old service if you haven't, and put the end date on the calendar.
2. Stay hybrid. Keep the human service for some calls, such as business hours, and the AI for the rest. That's a fine outcome if the numbers support it.
3. Extend the test. Keep the slice running another week and fix the open issues.

Whichever you pick, write the rollback: the exact forwarding code or setting that sends calls back to the old service, and who is allowed to use it. Keep it until the old service has ended.

How do you split calls during the parallel run?

How you split depends on how calls reach your current service today.

If you forward your number to the service, you change the forwarding destination. On a mobile line that can be a code: Verizon lists "*72 + the 10-digit number" to forward all calls, "*71 + the 10-digit number" to forward only calls you don't answer, and *73 to stop (Verizon); T-Mobile lists *21 for all calls and *61 for no-answer forwarding, with a no-answer delay you can set from 5 up to 30 seconds (T-Mobile). Business phone systems often have schedules or ring groups instead; check yours.

Splitting by time. For an after-hours slice, switch the forwarding to the AI at closing and back to the service at opening. If your phone system can do that on a schedule, use it. If not, set two phone alarms and assign one person to make the change. A missed switch at 8 a.m. is how a parallel run quietly fails.

Splitting by overflow. Leave the human service as the main destination and send calls it can't take to the AI, if your service supports transferring overflow to another number. Ask them.

If the number is ported to the service, you can often still forward from the service's side to the AI while the port-out is arranged. Ask the service what its settings allow, and don't cancel until the port is complete.

Whichever way you split, call your own number from another phone at the start and end of each slice to confirm where it lands. Our guide to keeping your phone number with an AI receptionist covers forwarding and porting in more depth.

How do you compare the AI with your current service?

Score both sides on the same calls, the same hours and the same questions. Here is a simple sheet:

Two cautions. First, the AI's slice and the human service's sample have to cover similar hours, because a Tuesday 2 p.m. caller and a Saturday 1 a.m. caller want different things. Second, booked jobs depend on your callback as much as on the answer, so track the callback time on both sides. Our guide to reading your call log shows how to pull those numbers.

For cost, check how each side bills. Ruby, for example, publishes plans such as $395 a month for 100 minutes, and its FAQ says calls are rounded up to the nearest 60-second mark and that it includes hold time (Ruby). Read your own last three invoices for minutes or calls used, overage and add-ons, and compare that with the AI plan at the same volume. Our guide to per-minute and flat-rate pricing walks through the math.

What usually goes wrong, and how do you avoid it?

These are the failure points worth planning around:

• Cancelling before the number has moved. If the service hosts your number, cancelling first can leave callers with nothing. Port first, confirm, then cancel.
• Forgetting old forwarding settings. An old "forward when busy" rule pointing at the service can keep sending some calls there after you think you've switched. T-Mobile's short codes page lists ##004#, which "Resets call forwarding to default," a clean way to start over on that network.
• Calls dropping during the switch. Google's Local Services Ads ranking page says "Missed calls may negatively affect your responsiveness," so test each change with a real call.
• Switching in your busiest week. Pick a normal week, so your callbacks can keep up while you watch both systems.
• Leaving the team out. Tell anyone who takes callbacks where messages will now arrive, and in what format.
• Testing only in English. In the Census Bureau's 2018-2022 survey, Spanish speakers made up 61.1% of U.S. residents who spoke a language other than English at home. If your old service handled Spanish calls, test that the AI does too.

Where does TheKeyBot fit?

Disclosure: TheKeyBot, which publishes this blog, makes an AI receptionist. Here is what its pages say that bears on a switch.

• KeyBot Lite is $149 a month with 100 calls included, then 50 cents a minute: it answers 24/7 in English and Spanish, takes the message and sends it to your phone, with no quoting or booking (pricing). Its page describes setup as a setup wizard, a Telegram connection and forwarding your line, and says you control the forwarding: "after hours, on weekends, when you're on a job, or 24/7." That suits an after-hours slice.
• Core is $500 a month with 500 AI minutes, then 45 cents a minute, with the AI receptionist, scheduling, GPS dispatch, POS and payments (pricing). That's the plan that quotes and books, so it fits a shop whose current service books appointments.
• Numbers. TheKeyBot's FAQ says it can port your existing business number, provide a new number, or let you forward calls from your current system. Every plan includes a dedicated AI phone number, and the pricing page says you can upgrade from Lite to Core and keep your number.
• Trials and terms. Lite's first 5 answered calls are free (up to 7 days), Core, Pro and Elite include a 14-day free trial, and there are no setup fees or contracts (pricing).

A 14-day trial covers a 7-day plan with room to extend. Our 24-hour setup checklist covers the first day in more detail, and AI receptionist vs human answering service covers whether to switch at all.

Frequently Asked Questions

How long does it take to switch from an answering service to AI?

Setting up and testing the AI can fit in a few days, and a first live slice of calls can run within a week. The old service may need to stay on through its notice period, and porting a number out adds time, so plan the end date around your contract.

Should I cancel my answering service before I start?

No. Keep it running while the AI handles a slice of calls, and give notice once your results are in, unless waiting would cost you another full billing period.

Can I keep my phone number when I switch?

Yes. If you forward your number to the service today, you just change the forwarding; if the number was ported to the service, port it to your new provider and don't cancel until the port is complete.

What calls should the AI take first?

Start with after-hours calls, then weekends, then daytime calls you don't answer. Each step should only happen after the previous slice has run cleanly.

How do I compare the AI with my current service?

Score both on the same hours and the same measures: complete messages, urgent calls flagged, time to your callback, jobs booked, complaints and cost. Use your own call log, not a vendor's benchmark.

What if the AI doesn't work out?

Keep a written rollback: the forwarding code or setting that sends calls back to the old service. Keep the old service until you're sure, and test the rollback once so you know it works.

Sources

1. Ruby, FAQs: https://www.ruby.com/faqs/
2. Ruby, plans and pricing: https://www.ruby.com/plans-and-pricing/
3. Smith.ai, AI Receptionist pricing: https://smith.ai/pricing/ai-receptionist
4. 47 CFR § 52.35, "Porting Intervals," Cornell Legal Information Institute: https://www.law.cornell.edu/cfr/text/47/52.35
5. T-Mobile, "Transfer your phone number": https://www.t-mobile.com/support/account/transfer-your-phone-number
6. T-Mobile, "Self-service & short codes": https://www.t-mobile.com/support/plans-features/self-service-short-codes
7. Verizon, "Call Forwarding FAQs": https://www.verizon.com/support/call-forwarding-faqs/
8. Google Local Services Help, "About ad rankings": https://support.google.com/localservices/answer/7527305?hl=en
9. Google Business Profile Help, "Guidelines for representing your business on Google": https://support.google.com/business/answer/3038177?hl=en
10. 18 U.S. Code § 2511, Cornell Legal Information Institute: https://www.law.cornell.edu/uscode/text/18/2511
11. Revised Code of Washington 9.73.030: https://app.leg.wa.gov/RCW/default.aspx?cite=9.73.030
12. National Weather Service, "Children, Pets and Vehicles": https://www.weather.gov/safety/heat-children-pets
13. U.S. Census Bureau, language spoken at home, 2018-2022 ACS (December 7, 2023): https://www.census.gov/newsroom/press-releases/2023/language-at-home-acs-5-year.html
14. TheKeyBot, pricing: https://www.thekeybot.com/pricing
15. TheKeyBot, KeyBot Lite: https://www.thekeybot.com/lite
16. TheKeyBot, FAQ: https://www.thekeybot.com/faq