How does predictive routing handle +61 number formatting when the campaign triggers on the Sydney edge? Running a standard predictive dialer setup on mypurecloud.com.au and the outbound calls keep getting rejected before they even hit the agent queue. Campaign ID is camp-7731-au. The predictive algorithm calculates the dial ratio, but right before call setup, the system drops the international prefix. ACMA compliance rules flag it as an invalid local format, so the call gets marked as DISPOSITION_FAILED with a 400 BAD_REQUEST.
Checking the /api/v2/analytics/predictive-campaigns/{campaignId}/calls endpoint shows the caller ID arriving as 0412345678 instead of +61412345678. The Architect flow pred-9942-syd has the number formatting block set to E.164, but it’s bypassing the formatting block entirely during the predictive calculation phase. Logs from the Sydney edge show PREDICTIVE_CALL_SETUP_FAILED: NUMBER_FORMAT_MISMATCH.
Tried toggling the auto_format_e164 flag in the campaign JSON payload. Didn’t change jack all. The predictive dialer still strips the prefix during the agent availability calculation. Latency on the Sydney edge is sitting around 180ms, which shouldn’t cause this, but the routing logic definitely expects a clean international string.
SDK documentation mentions outbound_number_formatting, but that only applies to manual outbound campaigns. Not seeing a config switch for predictive. Can’t find a way to force the dialer to preserve the prefix.
Payload looks like this:
{
"campaignType": "PREDICTIVE",
"dialRatio": 1.5,
"outboundNumberFormatting": "E.164",
"acmaComplianceEnabled": true
}
Response comes back with:
{
"code": 400,
"message": "Predictive call setup failed. Number format does not match ACMA outbound requirements.",
"details": "Expected E.164 format starting with +61. Received 04XXXXXXXX."
}
Flow is definitely set up right. Number porting records are clean. Predictive engine keeps mashing the prefix right when it calculates the agent forecast. Still digging through the /api/v2/predictive-routing/campaigns schema to see if there’s a hidden override flag…