The carrier confirms that your numbers have moved. Someone calls the main line, the receptionist answers, and the project appears ready to close.
That is a good first test. It says very little about the calls that arrive after hours, the direct numbers customers have saved, or what happens when the receptionist transfers someone to a busy department.
Separate the port from business acceptance
A number port and a working call flow are related milestones with different evidence. RingCentral’s number-porting resource center provides the official process and requirements for transferring numbers. Your acceptance plan should then prove that those numbers support the business tasks people rely on.
Before closing the project, assign an owner to the test results and agree on which failures prevent acceptance. Keep the provider’s escalation contacts available through the verification period. Do not assume a port can be instantly reversed if a test fails.
Call from outside your own system
Test inbound calls from independent networks using approved test participants. A call between two extensions does not exercise the same path as a customer calling from a mobile phone.
Check the main number, a representative set of direct numbers, and any high-priority service lines. Confirm that each call reaches the expected destination and that the person answering can hear and be heard. Record the originating network, destination number, time, expected result, and actual result so an intermittent problem can be investigated.
Follow the caller beyond the greeting
Use a simple matrix rather than relying on memory:
| Call path | What to verify |
|---|---|
| Main number during business hours | Greeting, menu selection, correct team, and two-way audio |
| Direct number with no answer | Expected timeout, voicemail, and notification delivery |
| Queue with agents unavailable | Agreed overflow destination and accountable follow-up |
| Transfer to another department | Caller remains connected and reaches the intended destination |
| After-hours and holiday call | Correct greeting, routing, and callback instructions |
| Outbound call | Expected caller identity and a working return-call path |
Use normal staff accounts for the tests. Administrator access can hide a permission issue an employee will encounter on the first busy morning. Ask staff to retrieve the test voicemail and complete a callback, not merely confirm that a notification appeared.
Verify the services that did not move
Revisit the inventory of retained lines and connected services. Where applicable, confirm the agreed treatment of fax, messaging, elevator or alarm services, and other dependencies with their responsible providers. A voice number transfer does not prove that a separately provisioned service is ready.
Validate emergency calling information and behavior through the provider’s approved test process and your organization’s responsible team. Do not place an unannounced live emergency call as a routine acceptance test.
Our guide to partial ports and retained services explains why this inventory matters before the move. Use that same inventory to close the loop afterward.
Close with evidence and named exceptions
For each failed test, record an owner, a next action, and the temporary operating procedure. Tell the affected staff what to do while the issue remains open. A workaround known only to the project team is not an operating plan.
Acceptance does not require pretending every minor issue has disappeared. It requires a clear decision about what is working, what remains unresolved, and who has accepted the remaining risk. VIcom can help build and run a cutover acceptance session around your actual phone numbers, departments, and customer call paths.
Connect with VIcom by filling out the form below.
