--- title: "AI Voice in Australia 2026: ACMA, 1300 and 1800 Numbers, and the Do Not Call Reality" description: "How ACMA's numbering plan, the difference between 1300 and 1800 toll-free numbers, the Do Not Call Register, and the 2026 commercial-radio AI-disclosure rule shape AI voice agents in Australia." canonical: https://callsphere.ai/blog/vw9d-ai-voice-australia-acma-1300-1800-2026 category: "AI Infrastructure" tags: ["Australia", "ACMA", "1300", "1800", "Compliance"] author: "CallSphere Team" published: 2026-03-19T00:00:00.000Z updated: 2026-05-08T17:26:02.917Z --- # AI Voice in Australia 2026: ACMA, 1300 and 1800 Numbers, and the Do Not Call Reality > How ACMA's numbering plan, the difference between 1300 and 1800 toll-free numbers, the Do Not Call Register, and the 2026 commercial-radio AI-disclosure rule shape AI voice agents in Australia. > Australia's voice market is small but tightly policed. ACMA hands out six-figure fines for telemarketing violations, the Do Not Call Register has more than 11 million entries, and from 1 July 2026 the Commercial Radio Code requires synthetic-voice disclosure on regular programming. AI voice agents land squarely in this regulatory zone. ## How telephony works there The Australian Communications and Media Authority (ACMA) administers the Numbering Plan 2015 under the Telecommunications Act 1997. Geographic numbers use 8-digit local + 1-digit area code (02 NSW/ACT, 03 VIC/TAS, 07 QLD, 08 WA/SA/NT). Mobile numbers start with 04. Non-geographic ranges include 1300 (shared-cost: caller pays a flat untimed-local rate, business pays the rest), 1800 (free to caller, business pays everything), and 13 (six-digit, premium-priced for big-brand inbound). Twilio Australia offers AU local DIDs, 1300, and 1800 numbers; the Sydney media edge keeps RTT under 50 ms for Australian users. NBN-driven IP migration is largely complete; the legacy copper PSTN is decommissioned in most metro areas. Number portability between carriers is available within 1-3 business days. There is no STIR/SHAKEN equivalent yet, but ACMA's "Reducing Scam Calls" code (C661:2022) requires originating carriers to identify and block spoofed CLIs at the network edge. ## Regulatory landscape Three regimes apply. First, the Do Not Call Register Act 2006: AI marketing calls must scrub against the DNC Register on a wash cycle of at most 31 days, and consent must be express, recent, and revocable. Second, the Spam Act 2003 governs SMS follow-ups and requires identification, unsubscribe, and consent. Third, the Privacy Act 1988 (with the new privacy-reform amendments coming into force 2025-2026) requires a privacy notice, purpose limitation, and breach notification. For AI specifically, the Commercial Radio Code of Practice 2026 (effective 1 July 2026) makes AI-voice disclosure mandatory on regular radio programming. ACMA has signalled it will treat undisclosed AI voice in marketing calls as a breach of the deceptive-conduct provisions of the ACL. Maximum penalties under the DNC Register Act go up to AUD 165,000 per body-corporate offence per day. ## CallSphere implementation CallSphere uses Twilio across all six verticals (Healthcare AI, Real Estate AI, Sales Calling AI, Salon AI, IT Helpdesk AI, After-Hours AI), with 37 agents, 90+ tools, 115+ DB tables, HIPAA + SOC 2, and pricing at $149 / $499 / $1499 with a 14-day trial and a 22% lifetime affiliate. Australian tenants get a Twilio AU local DID for their state, plus 1800 (Salon, After-Hours) or 1300 (Sales, Helpdesk) where the caller-cost trade-off is right. We register the operator with ACMA's DNC Register access scheme and run a daily wash. The AI agent opens with "this call is from [brand], you are speaking to an AI assistant", which doubles as DNC compliance and pre-empts the 1 July 2026 disclosure rule. Outbound concurrency is capped per tenant; recording is on by default; consent records are stored for at least 7 years. ## Build and launch steps ```mermaid flowchart LR A[Twilio AU subaccount + Sydney edge] --> B[Provision local DID + 1300 / 1800] B --> C[ACMA DNC Register access] C --> D[Privacy notice + express consent capture] D --> E[AI disclosure first sentence] E --> F[Daily DNC wash + audit log] ``` 1. Create a Twilio AU subaccount and pin to the Sydney media edge. 2. Provision a state-matching local DID and a 1800 (free-to-caller) or 1300 (shared-cost) number. 3. Subscribe to the ACMA Do Not Call Register and configure a daily wash on every outbound list. 4. Publish an Australian Privacy Principles notice and capture express consent at the form/IVR layer. 5. Configure the AI agent to disclose identity and AI status in the first sentence. 6. Enable call recording, store transcripts and consent metadata, and rotate logs monthly. ## FAQ **Should I get a 1300 or 1800 number?** 1800 is free to the caller and is the friendliest for inbound consumer support. 1300 splits the cost (caller pays an untimed-local rate, business pays the rest) and is common for B2B sales lines. **Does the DNC Register apply to my existing customers?** Calls under an existing relationship are exempt for up to 12 months after the last interaction, but you still must offer opt-out and honour it. **When does the AI disclosure rule kick in?** The Commercial Radio Code is from 1 July 2026 for radio. ACMA has signalled it expects equivalent disclosure in commercial calls now under the deceptive-conduct provisions. **Are call recordings legal in all states?** The federal TIA Act and state surveillance acts vary. Best practice is two-party consent: announce recording in the first sentence. ## Sources - [ACMA: Numbering Plan and 1800/1300](https://www.acma.gov.au/phone-number-rules) - [ACMA: Do Not Call Register](https://www.donotcall.gov.au/) - [ACMA: AI disclosure under new commercial radio rules (Feb 2026)](https://www.acma.gov.au/articles/2026-02/ai-disclosure-required-under-new-commercial-radio-rules) - [Reducing Scam Calls Industry Code C661:2022](https://www.acma.gov.au/reducing-scam-calls-and-scam-sms-industry-code) Start a [14-day trial](/trial) on a 1300/1800, see [pricing](/pricing) at $149/$499/$1499, or [contact us](/contact) for ACMA DNC setup help. ## AI Voice in Australia 2026: ACMA, 1300 and 1800 Numbers, and the Do Not Call Reality: production view AI Voice in Australia 2026: ACMA, 1300 and 1800 Numbers, and the Do Not Call Reality forces a tension most teams underestimate: agent handoff state. A single LLM call is easy. A booking agent that hands a confirmed slot to a billing agent that hands a follow-up to an escalation agent — that's where context loss, hallucinated IDs, and double-bookings live. Solving it well means treating the conversation as a stateful workflow, not a chat. ## Serving stack tradeoffs The big fork is managed (OpenAI Realtime, ElevenLabs Conversational AI) versus self-hosted on GPUs you operate. Managed wins on cold-start, model freshness, and zero-ops; self-hosted wins on unit economics past a certain conversation volume and on data residency for regulated verticals. CallSphere runs hybrid: Realtime for live calls, self-hosted Whisper + a hosted LLM for async, both routed through a Go gateway that enforces per-tenant rate limits. Latency budgets are non-negotiable on voice. End-to-end target is sub-800ms ASR-to-first-token and sub-1.4s first-audio-out; anything beyond that and turn-taking feels stilted. GPU residency in the same region as your TURN servers matters more than choosing a slightly bigger model. Observability is the unglamorous backbone — every conversation produces logs, traces, sentiment scoring, and cost attribution piped to a per-tenant dashboard. **HIPAA + SOC 2 aligned** isolation keeps healthcare traffic separated from salon traffic at the storage layer, not just the API. ## FAQ **How does this apply to a CallSphere pilot specifically?** Real Estate runs as a 6-container pod (frontend, gateway, ai-worker, voice-server, NATS event bus, Redis) backed by Postgres `realestate_voice` with row-level security so multi-tenant data never crosses tenants. For a topic like "AI Voice in Australia 2026: ACMA, 1300 and 1800 Numbers, and the Do Not Call Reality", that means you're not starting from scratch — you're configuring an agent template that's already been hardened across thousands of conversations. **What does the typical first-week implementation look like?** Day one is integration mapping (scheduler, CRM, messaging) and prompt tuning against your top 20 real call transcripts. Day two through five is shadow-mode running, where the agent transcribes and recommends but a human still answers, so you can compare side-by-side. Go-live is the moment your eval pass-rate clears your internal bar. **Where does this break down at scale?** The honest answer: it scales until your tool catalog gets stale. The agent is only as good as the integrations it can actually call, so the operational discipline is keeping schemas, webhooks, and fallback paths green. The platform handles the rest — observability, retries, multi-region routing — without your team owning the GPU layer. ## Talk to us Want to see how this maps to your stack? Book a live walkthrough at [calendly.com/sagar-callsphere/new-meeting](https://calendly.com/sagar-callsphere/new-meeting), or try the vertical-specific demo at [salon.callsphere.tech](https://salon.callsphere.tech). 14-day trial, no credit card, pilot live in 3–5 business days. --- Source: https://callsphere.ai/blog/vw9d-ai-voice-australia-acma-1300-1800-2026