Set Up VoxPro: 15-Minute Phone Migration Guide

First, choose the kind of migration you actually need

A phone migration can mean two different things:

1. Call forwarding: Your current business number stays with your carrier. Incoming calls are redirected to a dedicated VoxPro number. This is the quickest and easiest arrangement to reverse.
2. Number porting: Your number permanently moves from one provider to another. The FCC says customers can generally keep a number when switching between wireline, IP, and wireless providers in the same geographic area. Simple ports are generally processed within one business day, though more complex changes can take longer.²

For a fast launch, forwarding is usually the cleaner starting point. You can prove the call flow without canceling service or waiting for a permanent number transfer. If you later decide to port, do not cancel the old account before the transfer completes.

The 15-minute preparation checklist

VoxPro's setup is done for you. Its website describes a 20-minute onboarding conversation, agent build, approval, and a typical go-live within 24 hours.¹ The 15 minutes here are your preparation time before that conversation.

Minutes 0-3: choose when VoxPro answers

Pick one coverage mode before discussing scripts:

• All calls: VoxPro answers every inbound call.
• Overflow: Your team gets the first chance; VoxPro answers after a set number of rings or when lines are busy.
• After hours: Your team answers during scheduled hours; VoxPro covers evenings, weekends, and holidays.

Do not choose based on what sounds advanced. Choose based on the actual failure point. A salon with a staffed front desk may need overflow during the Saturday rush. A plumber may need full after-hours coverage because the most urgent calls arrive when the office is closed.

Write down the hours, ring delay, and holiday rules. That eliminates vague instructions such as "pick up when we cannot."

Minutes 3-6: write the five facts callers always need

List the information a competent receptionist would need on day one:

• Services you offer and jobs you do not accept
• Service area, locations, or ZIP codes
• Business hours and emergency availability
• Starting prices, trip fees, or rules for discussing price
• Scheduling system, appointment length, and lead time

Use plain language. A useful note says, "We repair residential central AC systems within 25 miles of Dallas, but we do not service window units." A weak note says, "We handle HVAC calls."

Add common caller wording, too. Customers may ask for a "tune-up," "maintenance visit," or "AC check" even though your calendar uses one service name. Those phrases help the agent map natural speech to the right action.

Minutes 6-10: define qualification and handoff rules

Now decide what the agent should collect and when a person must take over. Start with a short intake set:

• Caller name and callback number
• Service address or preferred location
• Reason for the call
• Urgency and preferred appointment time
• Any industry-specific detail needed before booking

Then define hard boundaries. Examples include:

• Transfer active water leaks, gas odors, or safety concerns immediately.
• Text the owner when a quote is above a set value.
• Do not give legal, medical, or licensed technical advice.
• Send existing billing disputes to a named staff member.
• Never promise a price or arrival time that is not in the approved rules.

A handoff is not a failure. It is part of a safe call flow. The goal is to automate repeatable work and make exceptions reach the right human with context.

Build one clear call path, not twenty scripts

A small service business rarely needs a giant decision tree to launch. Begin with the path most callers follow:

1. Greet the caller using the business name.
2. Identify the reason for the call.
3. Check location and service eligibility.
4. Collect the required details.
5. Book, transfer, or create a follow-up task.
6. Send the approved confirmation.

That core path can handle most routine inquiries. Add branches only when the outcome truly changes. "New customer" and "existing customer" may need different questions. "Emergency" and "routine appointment" need different urgency rules. Ten versions of the greeting do not improve the result.

Minutes 10-13: connect the destination

Decide where each successful call should land:

VoxPro says it can connect to calendars or CRMs, qualify leads, book approved appointments, and send follow-up details.¹ During onboarding, name the exact destination instead of saying "send it to the team." A shared inbox address, calendar name, or primary and backup phone number is testable. "The team" is not.

Minutes 13-15: plan five test calls

Do not launch after one friendly demo. Test the edges that can expose a bad rule:

1. A normal new customer requesting your most common service
2. An existing customer changing an appointment
3. A caller outside your service area
4. An urgent request that should transfer to a human
5. A Spanish-speaking caller, if bilingual coverage is enabled

For each call, verify the greeting, questions, qualification, booking or transfer, and follow-up message. Check the destination system, not just the conversation. A caller can have a good experience while the appointment lands on the wrong calendar.

What launch day should look like

Imagine a two-technician HVAC company switching on overflow coverage. The owner keeps the existing public number. Calls ring the office first; if nobody answers, the call forwards to VoxPro.

At 10:18 AM, both technicians are working and the office line rings. VoxPro answers using the company name, confirms the homeowner is inside the service area, asks whether the system is cooling at all, and offers an approved appointment window. The homeowner receives a confirmation, and the dispatcher sees the booking without listening to voicemail.

At 10:31 AM, another caller reports a burning smell. The emergency rule triggers a transfer to the on-call phone. The technician receives the call with the caller's name, address, and issue already captured.

The phone number customers know never changed. The difference is what happens when the team cannot answer.

Forwarding is also your rollback plan

A safe migration has a simple way back. Before launch, record:

• The carrier setting or forwarding code used
• The original ring behavior
• The number receiving forwarded calls
• The person authorized to disable forwarding
• The support contact for both services

If a test fails, turn off forwarding, fix the rule, and test again. Do not improvise while real customer calls are arriving.

If you choose permanent number porting instead, the process needs more care. The FCC advises customers not to terminate existing service before initiating the move.² Keep the account active, provide accurate account details to the new provider, confirm the activation window, and test inbound and outbound calling after the transfer.

The first week is calibration, not reconstruction

Review a small sample of calls every day for the first week. Look for patterns:

• Callers use a service name the agent does not recognize.
• A question is being asked even when it does not affect the outcome.
• A transfer rule fires too often or not often enough.
• Appointment length or travel time creates calendar conflicts.
• Follow-up details reach the wrong person.

Make one clear change at a time. If you change the greeting, qualification questions, transfer rules, and calendar behavior together, you will not know which change helped.

Keep a short log with the call type, expected result, actual result, and adjustment. After a week, the call flow should reflect how your customers really speak, not how you imagined they would speak during setup.

Common migration mistakes

Canceling the current phone service too early

Forwarding and porting are not the same. Keep the current carrier active until a port is complete and verified. For a forwarding launch, keep it active because it still owns the public number.

Sending every exception to the owner

If every pricing question, reschedule, complaint, and urgent request transfers to one phone, automation has only moved the interruption. Define which issues require judgment and which can become a message or follow-up task.

Giving the agent your whole employee handbook

The agent needs call-handling rules, not every internal document. Start with services, locations, hours, prices, booking rules, escalation triggers, and approved answers. Add detail when real calls show a gap.

Testing the conversation but not the result

A perfect greeting is irrelevant if the calendar entry is wrong or the alert never arrives. Every test should end with a destination check.

Your one-page migration brief

• Coverage mode and schedule
• Current public number and carrier
• Services, exclusions, and service area
• Approved pricing language
• Required intake questions
• Booking destination and appointment rules
• Primary and backup transfer numbers
• Emergency and human-handoff triggers
• Follow-up destination and message type
• Five test scenarios
• Rollback owner and procedure

That is enough to move from a general idea to a testable call flow. VoxPro handles the build, scripts, routing logic, calendar or CRM connection, and tuning with your approval.

Start with forwarding, prove the flow, then expand

The lowest-risk migration is usually incremental. Forward overflow or after-hours calls first. Review the outcomes. Expand to full coverage when bookings, transfers, and notifications consistently reach the right place.

You do not need to redesign the business to stop sending callers to voicemail. You need accurate facts, explicit boundaries, real destinations, and five good tests. Prepare those in 15 minutes, use the onboarding conversation to refine them, and the system can usually be ready within VoxPro's stated 24-hour launch window.

Learn how an AI receptionist works inside each call, or review VoxPro pricing and coverage options.