An outbound DID monitoring report should connect each phone number’s identity, approved usage, connect rate, conversations, complaints, and campaign context to a clear management action. A dashboard full of totals is not enough if nobody can tell which number changed or who is responsible for reviewing it.
The objective is not to react to every daily fluctuation. It is to maintain consistent number-level history, compare similar activity, and investigate changes that are material, sustained, or supported by other warning signals.
Start With the DID Inventory Fields
Every report row should identify the number being evaluated. Include the DID, provider or source, acquisition and activation dates, registration status, assigned user or pool, market, campaign, warm-up stage or operating profile, and monitoring owner.
Without these fields, managers may compare a newly warmed number with an established DID or confuse a campaign change with a reputation problem.
Include Usage and Distribution
Record daily call activity against the number’s current cap or approved range. Also show whether calls are being distributed across the available pool or concentrated on a few DIDs.
- Calls placed during the review period.
- Current warm-up stage or managed-use profile.
- Assigned campaigns and users.
- Material changes in volume, hours, or distribution.
- Rapid retries or unusual short-call patterns.
A number below its numerical cap can still require review if its activity changed abruptly or no longer matches its assignment.
Connect Attempts to Conversations
Include connect rate, live conversations, meaningful conversations, and connected duration where those measures are available and consistently defined. ProspectBoss uses 10% or higher as a practical campaign benchmark, while recognizing that results vary by audience, industry, timing, data, identity, and offer.
Use the trend rather than treating one percentage as a verdict. Compare the DID with its own recent history and with similar numbers serving the same campaign.
Reporting rule: State the numerator, denominator, period, and population behind every rate. A percentage without those details can hide a very small or mismatched sample.
Add Reputation and Experience Signals
Track verified label reports, complaints, opt-outs, blocking observations, registration changes, and technical failures separately. Do not combine them into one unexplained “health score” unless the underlying components remain visible.
A low connect rate alone does not prove a Spam Likely label. Likewise, one reported label does not prove every recipient sees the same display. Record the evidence and its source.
Document Context and Recent Changes
Note whether the team launched a new list, market, script, offer, user, schedule, or dialing configuration. If several numbers change after the same event, that shared context may be more important than the performance of one DID.
Keep campaign-quality measures separate from number-health signals while displaying them together for investigation.
End Every Review With a Decision
Use a defined action field: continue, hold at the current stage, adjust distribution, reduce activity, pause, investigate, remediate, or retire. Add the decision owner, reason, completion date, and next review.
Illustrative report note:
DID: identified internally.
Observation: connect rate declined across two comparable periods.
Context: campaign and schedule unchanged; usage increased materially.
Action: reduce to prior range, verify registration, and review again on the assigned date.
Owner: named operations manager.
The ProspectBoss number-monitoring framework recommends daily review for active warm-up numbers, weekly campaign and user reviews, monthly trend analysis, and immediate review after major changes or critical alerts. This reporting template organizes the evidence behind those reviews.
Frequently Asked Questions
What belongs in a DID monitoring report?
Include identity, assignment, stage, usage, connect rate, conversations, duration, complaints, opt-outs, label reports, registration, context, action, owner, and review date.
Should managers review only team averages?
No. Team averages can hide individual numbers that are declining or carrying uneven activity.
Is 10% a guarantee of number health?
No. It is a practical ProspectBoss campaign benchmark, not proof that a number is healthy or permanently protected.
How should small samples be handled?
Show the call count and avoid strong conclusions from limited activity. Continue monitoring for usable evidence.
Who should own the report?
Assign a manager or operations owner who can investigate and complete the resulting action.
Manage Outbound Numbers With Better Visibility
See how ProspectBoss connects controlled calling, number health, follow-up, and performance evidence.
