Moving a business number to Quo: a migration and continuity workbook

Moving a business number is a continuity project. Customers may use the number printed on old invoices, search listings or vehicles, while staff may depend on it for verification messages and existing conversations. A successful migration preserves the business purpose of that number rather than merely showing a new provider in an account dashboard.

This workbook follows a fictional repair business considering Quo. The owner wants a shared calling and texting arrangement, but the existing number also receives supplier calls and occasional account verification messages. Before a port request, the business needs an inventory of those dependencies and confirmation of the intended number and service eligibility. Port timing and messaging registration can involve separate requirements; obtain the current instructions for the actual country and account.

Quo was previously known as OpenPhone. Use the current provider documentation and account name when preparing a migration, while recognizing older references in existing records. This is an acceptance plan, not a promise of a specific port duration or uninterrupted operation in every carrier situation.

Design the work around the actual completion event

1. Establish who controls the number

Identify the current account holder, the person authorized to request a transfer and the evidence required by the existing and receiving providers. Match the account information before proposing a change date.

A published business number may sit in a former employee account whose details nobody has checked recently.

2. Inventory the quiet dependencies

List where the number appears and what services send messages to it. Include customer records, supplier contacts and authentication arrangements. Separate a phone-system requirement from a third-party service whose acceptance of a number must be confirmed independently.

A number can handle customer calls while failing an unrelated verification use case that the business assumed would continue.

3. Define coverage during the change window

Agree who watches the old and new arrangements, who can communicate a temporary alternative and how unresolved customer requests are recorded. Confirm the actual port process with the providers before promising a completion window.

An unstaffed transition period can turn a short technical change into a lost customer conversation.

4. Check calls and texts as distinct journeys

Prepare inbound, outbound and message cases relevant to the business. Include the devices and staff roles that will use them. Confirm any registration or account setup required for the intended messaging use.

A successful inbound call does not establish that every texting or outbound identification requirement has been met.

5. Rehearse the shared customer handoff

Give a covering teammate an active repair conversation with the customer goal, approved promise and next action. Verify that relevant information remains accessible through the working arrangement rather than a personal memory.

Two people having access to a number does not establish that either has accepted the next response.

6. Close the old arrangement only after reconciliation

Check transfer completion, required conversation access, billing dependencies and any remaining numbers or services. Ask the existing provider what cancellation would affect. Preserve records according to the business retention policy.

An early cancellation can remove a dependency or access route the team still needs during transition.

A worked batch: distinguish clean work, repaired work and unresolved work

Use the following fictional batch for a repair business moving its published customer number to a shared phone operation. Its purpose is to make the operating definitions inspectable before a live rollout. It is not a Quo benchmark. The batch contains 120 candidate accepted number-migration checks; 90 satisfy the agreed criteria on the first review. The remaining 30 need clarification, correction or a decision. After controlled repair, 15 of those held cases become usable and 15 remain unresolved.

The first-pass share is 90 / 120, or 75.0%. The final usable share is 105 / 120, or 87.5%. Those figures describe different things. A report showing only the final number would conceal the intervention needed to get there. A report showing only first-pass work would overlook the value recovered through a legitimate correction. Keep both, with the reason each held case entered or left review.

Rehearsal measure	Fictional input or calculation	Interpretation for this task
Candidates inspected	120	Every candidate remains in the starting denominator
Accepted without repair	90	The agreed conditions were met at first inspection
Initially held	30	Work needing a separate decision or correction
Released after repair	15	A subset of held work, counted once after approval
Still unresolved	15	Visible work awaiting an owner or missing evidence
Final usable output	90 + 15 = 105	Approved accepted number-migration checks, not all candidates

For this example, one accepted number-migration check is an operating outcome, not automatically a customer, sale or financial return. Define its completion evidence from the playbook above. If a later commercial result matters, track it in a separate column and follow the same reference into the next system. Changing the unit halfway through the report can make a larger count look like an improvement when it merely answers a different question.

Put review and repair into the operating cost

Assume 2 minutes to inspect each candidate, 12 additional minutes for each successfully repaired case, and an internal labor rate of $35 per hour. These are invented workload assumptions. Initial inspection takes 120 × 2 / 60 = 4.00 hours. Successful repair adds 15 × 12 / 60 = 3.00 hours. Keep any investigation of the 15 unresolved cases as a separate estimate; the present calculation has not priced that unknown work.

With a hypothetical $65 allocation for supporting tools, the scoped batch cost is $65 + (4.00 + 3.00) × $35 = $310.00. Dividing by 105 approved outcomes gives $2.95 per accepted number-migration check. The $65 allocation is not a quoted Quo subscription. Replace it with the actual incremental charges appropriate to your configuration, and avoid allocating the full same shared subscription to several batches without a consistent rule.

For a repair business moving its published customer number to a shared phone operation, the $310.00 estimate answers a bounded process question. It excludes unspecified recovery work, broader project setup and a downstream commercial result. The 105 approved accepted number-migration checks need their own completion evidence; they should not be relabelled as customers or profit. Decide whether that defined output and the remaining 15 unresolved cases justify the next controlled stage with the available staffing.

Test sensitivity before deciding that volume is the answer

Hold the scoped cost constant and suppose ten fewer candidates meet the final acceptance criteria. Approved output would fall to 95, and the cost per usable outcome would rise to $3.26. This is a sensitivity exercise, not a prediction about Quo. It shows why the acceptance definition and the treatment of exceptions matter when comparing a clean-looking dashboard with the work performed outside it.

Alternatively, examine the incremental repair work. At the assumed labor rate, one 12-minute repair costs $7.00 before any extra charge. That is a useful boundary for deciding which corrections deserve attention. A correction that preserves an important relationship or prevents an incorrect release may be worthwhile even when it is slower. A low-value case that repeatedly consumes review time may belong in a held or excluded category instead.

Capacity also has a denominator. The scoped 7.00 hours must fit into the actual coverage available for a repair business moving its published customer number to a shared phone operation. If the team has eight hours allocated to this task, it cannot promise unlimited same-period processing merely because the software accepts more inputs. Schedule the remaining review visibly, reduce the batch or assign additional qualified coverage. A queue hidden in a spreadsheet is still part of the operation.

Run the six acceptance exercises with a second operator

For a repair business moving its published customer number to a shared phone operation, run the exercises against the exact selected Quo configuration. The accepted unit is a accepted number-migration check, so a successful screen or integration connection alone does not settle the result. Keep safe source records and separate demonstrated behavior from a requested capability. Retain the unexpected case because it may reveal why one of the 15 unresolved outcomes cannot yet be approved.

Exercise 1: Establish who controls the number

Review the ownership information with the authorized business contact and list every unresolved mismatch.

The migration request uses verified account details and a named person can resolve an ownership question. Record the input reference, the observed result and the responsible next operator. If the result depends on a manual convention, retain that convention with this exercise so the next person can repeat it.

Exercise 2: Inventory the quiet dependencies

Walk through the business systems that use the number and inspect the recovery route for each critical account.

Every important dependency has a confirmed intended route or a separate transition action before the port. Record the input reference, the observed result and the responsible next operator. If the result depends on a manual convention, retain that convention with this exercise so the next person can repeat it.

Exercise 3: Define coverage during the change window

Simulate a customer asking about an active repair while the usual coordinator cannot access the expected route.

The covering person can preserve the request and give an approved continuation without inventing a completion time. Record the input reference, the observed result and the responsible next operator. If the result depends on a manual convention, retain that convention with this exercise so the next person can repeat it.

Exercise 4: Check calls and texts as distinct journeys

Use approved test contacts to inspect each required route and record the actual receiving device and business identity.

Each required journey has evidence from the intended arrangement and unsupported routes remain visibly unresolved. Record the input reference, the observed result and the responsible next operator. If the result depends on a manual convention, retain that convention with this exercise so the next person can repeat it.

Exercise 5: Rehearse the shared customer handoff

Have the original coordinator leave the controlled conversation and ask another teammate to continue it.

The teammate can identify the current commitment, responsible person and authoritative repair record. Record the input reference, the observed result and the responsible next operator. If the result depends on a manual convention, retain that convention with this exercise so the next person can repeat it.

Exercise 6: Close the old arrangement only after reconciliation

Reconcile the original inventory against the demonstrated new routes and obtain answers for the remaining gaps.

The business can explain why each old service is retained or closed, with no critical dependency assumed away. Record the input reference, the observed result and the responsible next operator. If the result depends on a manual convention, retain that convention with this exercise so the next person can repeat it.

Keep an operating record someone else can continue

For a repair business moving its published customer number to a shared phone operation, keep one reference for each accepted number-migration check. Use that reference across the input, the accepted result and any exception record. It allows a reviewer to follow the work without relying on a customer’s name, a screenshot title or the memory of the person who first handled it. Where the destination system assigns its own identifier, retain both references and explain the relationship.

Record field	What to put in it	Why it belongs in this workflow
Input reference	The original request, item or approved brief	Connects the result to the actual starting point
Configuration version	The relevant rule, template or account arrangement	Makes an observed result reproducible
Completion evidence	What establishes an accepted accepted number-migration check	Keeps the outcome definition stable
Exception reason	The missing fact, conflict or failed requirement	Directs repair toward the cause
Current owner	The person or queue that accepted the next action	Makes continuation visible
Review point	When the case or configuration needs another decision	Prevents unfinished work from disappearing

For one accepted number-migration check, write what the evidence establishes before proposing an explanation. In a repair business moving its published customer number to a shared phone operation, the note needs the starting reference and the accepted next responsibility as well as a visible result. Keep the supporting source small enough to inspect. A large screenshot collection should not replace an explicit decision about this particular outcome.

Before increasing the workload for a repair business moving its published customer number to a shared phone operation, review the held accepted number-migration checks by their actual cause. Use the six exercises to locate an input, configuration or responsibility gap, then repeat the affected route after its repair. The first ordinary accepted number-migration check does not establish that a different unresolved case has become acceptable.

Make the next decision from the evidence

Authorize the production move only when ownership, eligibility and continuity responsibilities are understood. Keep provider confirmations with the inventory rather than turning an indicative date into an unconditional customer promise. A migration with a small, explicit unresolved list can be reviewed; a migration based on undocumented assumptions cannot.

After the move, inspect real customer journeys and the first relevant bill. The acceptance result should include the number, the team and the surrounding business records. If a route still needs repair, assign it and preserve the temporary arrangement until the dependency is resolved.

Keep a short decision note for this specific Quo use case: the work approved, the conditions still outstanding, the owner of each outstanding decision and the next review date. A conditional approval is useful when its boundaries are visible. It becomes misleading when an unresolved requirement is presented as an observed capability.