Understand the status of your outbound calling numbers.

The pool groups numbers into Healthy, Watch and Flagged views. Review the number involved, its recent dialing activity and the last reputation check. These views help you decide which numbers need attention without treating every number in the pool as identical.

Open a number to inspect its available reputation data. EmberDial displays spam risk and provider scores when those values exist. If a number has no reputation data yet, the interface says so and keeps it on Watch until a check returns a result. Missing data is not proof that a number is clear.

For flagged numbers or numbers with medium or high spam risk, the interface offers reputation actions. A pending review has a visible status, so you can see that a request is already in progress.

• Request review: start the reputation review process and follow its status. Carriers decide the result; submitting a request does not guarantee a label will be removed.
• Rest & recover: remove the number from the dialing rotation while it rests. Resting a number does not establish that its reputation has recovered.
• Retire & replace: retire the number through the available workflow. Retirement is permanent and requires confirmation in the product.

A pool status and a provider score are information for your team to act on. They do not guarantee how every recipient’s phone will display a call. Check the data’s freshness and the review status before deciding what has changed. A new or replacement number also needs monitoring.

In a demo, ask to see a number with available scores, a number without data, and the actions your role can use. Discuss who on your team reviews the pool and handles numbers that need attention. That makes the feature part of an operating process, rather than a promise of a particular answer rate.

Number management supports the wider calling workflow. See how your team can schedule callbacks and return supported missed calls, or review the steps from trial setup to a first call.