Use one current category per number
The local worksheet accepts aggregate counts for scope, not yet transferred, provider-complete but route-unchecked, route-accepted and exception in progress. Count each number once in its current category. Do not paste telephone numbers, account details or customer information into the tool.
Know what a matching total means
A reconciled total only shows that the categories add up to the stated scope. It does not verify a carrier event, successful call or permission to cancel. Those facts require their own controlled evidence outside this publication. An unknown count should remain blank, not silently become zero.
Keep changes explainable
If the project gains or removes a number, update the scope and record the reason in your own project file. If an accepted number later fails, move it to an appropriate exception state rather than counting it twice. The tool does not save or transmit the entries.
A fictional reconciliation
A project has ten numbers: two waiting, three provider-complete but unchecked, four accepted and one in exception. The total reconciles to ten, while only four have the team’s required acceptance. The arithmetic prevents a bookkeeping mistake; it is not a technical test.
Reconcile a changing project without double counting
Suppose one accepted number develops a new exception. Reduce accepted by one and increase exception by one; the scope stays unchanged. If an additional number enters the project, change the scope deliberately and place that number in its current category. Record the reason in your own controlled project log, because the local tool has no memory of the earlier situation. A negative amount, fractional number or unmatched total needs correction before the board is useful. Do not move an item into accepted simply to make the arithmetic look complete. The categories organise evidence held elsewhere; they cannot create it. Use the resulting summary to assign outstanding work, and preserve the distinction between provider-complete, route-accepted and an unresolved exception when reporting progress.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- CloudTalk porting requests — Merchant documentation · help.cloudtalk.io · Merchant-controlled · checked 2026-09-28
- CloudTalk inbound diagnosis — Merchant documentation · help.cloudtalk.io · Merchant-controlled · checked 2026-09-28