Close rebuilds phone number management with shared routing and per-number controls

Close removes the old personal-versus-group number split

Close's September 17 changelog says it rebuilt phone-number management so each number can use members, shared ringing, round robin, lead-based routing, phone menus, voicemail and forwarding. The vendor also says features that were previously part of its Premium Number add-on are included with each number, with rental and usage charges remaining.

The release gives users with the Manage Team Phone Numbers permission visibility across organization numbers, while other users see the numbers on which they are members. Close also added per-number controls for whether non-members may use a number as outbound caller ID and whether voice agents may dial from it.

Sources: Close Phone Number Management

A phone number is an operational identity

A sales number is not just telephony infrastructure. It can represent a region, queue, team, campaign or customer-facing identity. Before changing the model, inventory each number, business owner, inbound purpose, outbound caller-ID purpose, hours, fallback, voicemail destination, routing rule and affected CRM workflow.

Avoid naming or membership conventions that depend on tribal knowledge. If a number is shared across a team, document who is accountable for missed calls, who may change routing and which users may present the number as caller ID. Central administration is useful only when the business ownership remains visible.

Separate inbound membership from outbound identity

Close's new per-number control for non-member caller ID makes a useful distinction explicit: receiving calls on a number and presenting that number on outbound calls are different permissions. RevOps should preserve that separation. A person may need to call from a regional or campaign number without joining the inbound queue; another user may belong to the queue but not be authorized to place outbound calls under that identity.

Test permissions with representative roles after migration. Confirm a non-member cannot use caller ID unless allowed, a member sees the expected routing behavior, a team-phone administrator can manage the intended scope and ordinary users cannot alter organization-wide settings.

Voice-agent access deserves its own control

The new setting that controls whether voice agents can dial from a number should be managed separately from human caller-ID access. Record the agent identity, allowed numbers, target population, operating hours, consent or policy requirements, rate limits and escalation path. A number that is safe for human outbound calling is not automatically appropriate for automated calling.

Start with a controlled test number and non-customer records. Verify the caller ID presented, call result, CRM association, recording or transcript policy, retry behavior and transfer or handoff path. Disable automated access until those records can be reconstructed from the CRM and telephony history.

Routing changes need before-and-after tests

A rebuilt number model can change the path a call takes even when the user interface looks simpler. For each important number, place inbound tests that cover round robin, lead-based routing, menu choices, voicemail and forwarding. Use test contacts that exercise ownership and lead-routing conditions rather than only calling from an unknown number.

Keep the previous routing configuration and an expected-results matrix through the migration window. If an inbound call reaches the wrong owner or a fallback fails, the operator should be able to compare the current membership and routing rule with the last known-good configuration.

What RevOps should record

Maintain a number register with provider number ID, E.164 number, business label, owner, members, routing mode, caller-ID policy, voice-agent policy, voicemail or forwarding target and last verified date. Link every material configuration change to a named operator and reason.

Close's release simplifies the product model, but the operating model still needs explicit ownership. The useful outcome is not that every number can do everything; it is that the team can intentionally grant the right inbound, outbound and automated behaviors to each number and verify them after change.

Reconcile number inventory after the permission model changes

After migrating to the rebuilt number model, compare the configured inventory with the business register rather than assuming every existing number inherited the intended policy. For each active number, verify its members, inbound routing mode, caller-ID setting, voice-agent permission, voicemail or forwarding target and accountable owner. Flag numbers with no owner or unexpectedly broad outbound access for review before normal calling resumes.

Then sample the resulting call records. Confirm that inbound calls associate with the intended lead or contact, outbound calls present the expected identity, and automated calls are attributable to the correct agent or workflow. A centralized settings page reduces administration effort, but the post-change reconciliation is what proves the customer-facing identity and routing behavior survived the migration.