What changed
Genesys Cloud now provides visibility into outbound calls that carriers block using analytics-based call blocking. When a call receives a SIP 603+ response, Genesys Cloud includes the reason for the block and contact information for the provider that blocked it, visible from the interaction's Details tab.
Vendor documentation (opens in a new tab)Why it matters
Analytics-based blocking often looks like a dial failure or a no-answer, which hides why outbound connect rates drop. Seeing the 603+ reason and the provider contact means outbound and callback teams can prove a number is being blocked and request remediation, instead of guessing at dialer or trunk faults.
CxCave practical context
Who should care
- Administrators
- Supervisors
Implementation considerations
NO ACTION REQUIREDAdd SIP 603+ to the checks your team runs when outbound connect rates fall, and keep the blocking provider contact process with your number registration and reputation records.
CxCave recommendation, not a vendor mandate unless explicitly stated.
