Feature Request

Enhance RingCX to generate and update the appropriate post-call state when an outbound call is classified as a Bad Number, instead of ending the call without a standard post-call state.

Current Behavior

Engineering confirmed that the current behavior is expected. When a destination number is identified as a Bad Number—such as an invalid, unreachable, disconnected, or otherwise non-callable number—the call does not proceed through the normal call flow.

Because the call is terminated or classified at an earlier stage, the normal post-call processing is not triggered, and no post-call state is generated or updated.

Customer Impact

The absence of a post-call state for Bad Number calls may limit the customer's ability to:

• Track the final outcome of these calls consistently.
• Apply the same post-call processing used for other outbound call outcomes.
• Maintain complete and consistent call disposition/reporting data.
• Accurately distinguish Bad Number outcomes from calls where post-call processing was not completed.

Requested Enhancement

• Provide a post-call state or equivalent call outcome for calls classified as Bad Number.

Ideally, RingCX should:

• Identify the call as a Bad Number.
• Terminate the call according to the existing Bad Number handling.
• Generate an appropriate post-call state or disposition indicating the Bad Number outcome.
• Make this outcome available for applicable reporting, analytics, and downstream processing.

Expected Behavior

• When an outbound call is classified as a Bad Number, RingCX should provide a clearly identifiable post-call outcome, such as Bad Number, Invalid Number, or another appropriate system-defined disposition.

This would allow customers to consistently track and report all outbound call outcomes, including calls that fail before entering the normal call flow.

Business Value

• Providing a post-call state for Bad Number calls would improve call outcome tracking, reporting accuracy, and automation capabilities, while giving customers a more complete view of outbound dialing activity.

Request: Please evaluate the feasibility of generating a post-call state/disposition for Bad Number calls and consider this behavior as a RingCX product enhancement.