BEFORE THE REQUEST
Collect the carrier record and confirm number ownership
Prepare the current account name, service address, billing number, carrier account number, every number in scope, and the authorization documents the carrier asks for.
Keep each customer's numbers in the correct request and confirm that the existing service remains active throughout the port.
PORTING PATH
Check, submit, document, confirm, and track
The Faxoryn workflow checks portability, creates a draft order with the carrier, uploads supporting documents, adds end-customer details, requests an allowed activation window, and then confirms the order.
The signed-in account can return to Number Porting Requests to inspect the latest state and failure detail.
- 01Check the complete number for portability.
- 02Submit only the portable numbers intended for this account.
- 03Add matching identity, address, carrier, and authorization evidence.
- 04Confirm the request and follow it to the final state.
AFTER COMPLETION
Verify routing before retiring the former service
Test inbound and outbound fax, default-number behavior, team assignments, and notifications. Keep the final carrier and Faxoryn request records for later support.
FAILED OR DELAYED REQUEST
Correct carrier evidence without creating overlapping orders
When a request fails or remains in progress, inspect the carrier's reason, the number list, customer identity, service address, billing data, authorization, and requested activation window. Correct the existing request where supported instead of submitting the same number through competing requests.
Keep the former carrier active and keep every Faxoryn reference and carrier order number for support until the port reaches a final result.
CUTOVER REGISTER
Record the checks that permit the old route to close
Document the completed carrier state, active Faxoryn number, inbound sample, outbound identity, default-number behavior, member assignments, notification delivery, published contact updates, and responsible approver.
A portability check or confirmed order is not cutover evidence. Close the former service only after the intended live route has been tested and the organization accepts its fallback plan.