What is DNCR washing?
The Do Not Call Register (DNCR) is Australia’s national register of phone numbers that have opted out of telemarketing calls. “Washing” a number means checking it against the register. Voxworks builds washing into the places you manage calling data: you can wash selected contacts, wash an entire list, and see the result as a status badge beside every phone number. Each wash submits your numbers to the register and records one of three results per number:- Y — the number is on the Do Not Call Register.
- N — the number is not on the register.
- I — the number appears to be invalid.
0 becomes +61) before checking.
Running a wash
There are two places to trigger a wash:
Both triggers behave the same way:
- No confirmation step — the wash starts immediately. Washing from the Contacts page shows a toast counting down how many numbers are being washed; washing from a list’s Wash List button switches the button to a Washing… label while it runs.
- Duplicates are removed — the same number appearing twice is only checked once.
- Recent results are reused — numbers already washed in the last 30 days are skipped, and the result message tells you how many were skipped (for example, “12 numbers were already washed recently.”).
- Contacts without a phone number are ignored — if nothing in your selection has a number, you’ll see “Selected contacts have no phone numbers to wash” (or “No phone numbers found in this list” for a list wash).
If the wash fails
Washing depends on the register accepting your account’s Do Not Call Register access credentials. If numbers are submitted but no results come back, you’ll see an error toast: “DNCR wash failed —{n} numbers submitted but no results received. Check your DNCR credentials.” Register credentials aren’t managed in the app — if this persists, speak to the Voxworks team.
Status badges
Every phone number in the Contacts table and in a list’s contact table carries a DNCR status icon. Hover it for the detail, including the date the number was last washed.
The contact detail panel shows the same status as a badge beside the Phone field — DNCR Registered, Not on DNCR, or Invalid Number (with “Checking DNCR…” while it loads), plus Override Active when an override is on.
The 30-day freshness window
A wash result is treated as current for 30 days:- Within 30 days — the badge shows the stored result, re-washes skip the number, and the pre-call block applies to “on register” results.
- After 30 days — the result expires. The badge reverts to Not washed, and the number is checked again the next time you run a wash that includes it.
The pre-call block
When you schedule an outbound call from the New Call modal, Voxworks checks the contact’s number before creating the call. If the number has a wash result from the last 30 days showing it is on the register, and no override is in place, the call is blocked and a dialog appears:
Do Not Call Register Warning
The number {phone number} is on the Do Not Call Register.
Only proceed if you have consent, an existing business relationship, or another valid exemption.
- Cancel — the call is not scheduled.
- OK — the call is scheduled with a one-off, call-level override recorded against it.
- It only blocks numbers with a fresh “on register” result. A number that has never been washed, or whose wash has expired, is not blocked — washing your data first is what makes the block effective.
- Test calls are exempt. Test calls ring your own phone or browser, not the contact, so DNCR screening does not apply to them. See Test Calls.
Overrides and audit
Some calls to registered numbers are lawful — for example where the contact has given consent or you have an existing business relationship. Voxworks supports two override levels, and both are recorded.Contact-level override
Open the contact’s detail panel. When the contact’s number shows DNCR Registered, an Override DNCR checkbox appears below the contact’s fields. Ticking it opens the Confirm DNCR Override dialog, which states “This contact is registered on the Do Not Call Register (DNCR)” and asks you to confirm that:- You have obtained explicit consent from this contact to make calls
- You have an existing business relationship that permits calling
- You are otherwise in compliance with local DNCR regulations
Call-level override
Clicking OK on the Do Not Call Register Warning dialog overrides the block for that scheduled call only. The contact’s status is unchanged — the next call to them triggers the warning again.Audit trail
Overrides are auditable: enabling a contact-level override records who enabled it, when, and the confirmation reason, and every override applied at scheduling time is logged. Wash activity itself is also recorded against your team, including who ran each wash and when. For the legal framing — ACMA obligations, exemptions, and where responsibility sits — see DNCR & Opt-Out Compliance.What is enforced
Voxworks enforces DNCR compliance automatically, alongside the manual tools on this page:- Manual washes (contacts and lists), the status badges, the 30-day freshness window, and the pre-call block with its override dialog when you schedule a single outbound call against a fresh “on register” result.
- Automatic batch screening. The Batch Scheduler washes queued contacts against the register before dialling and holds blocked or unresolved numbers rather than risking them (fail-closed), via the per-batch DNCR switch that defaults to on. See Batch Screening Gates for the full design.
Next Steps
- Contact Bulk Actions — the bulk toolbar on the Contacts page, including Wash DNCR Status.
- Lists — list detail, DNCR badges per contact, and the Wash List button.
- DNCR & Opt-Out Compliance — legal obligations, override mechanics, and the shared-responsibility model.
- Batch Screening Gates — the automatic pre-dial screening design and its current enforcement status.