What Is Actually Happening to Answer Rates
If you have run outbound calling in Australia for more than a few years, you have watched a number get quietly worse. The same list, the same people, the same offer, and a connect rate that used to be tolerable is now not. The usual explanations are all plausible and mostly wrong: people do not answer unknown numbers any more, everyone is on mobiles, the market is saturated.
Those things are true and they are not sufficient, because they do not explain the pattern most businesses actually see, which is that outcomes differ sharply between numbers. One of your numbers connects at a rate you can live with. Another, dialling the same list on the same platform in the same hour, does not. If the cause were general consumer behaviour, both numbers would perform the same. When two numbers perform differently, the difference is in the numbers or in how they are presented — not in the market.
The useful reframing: your call now passes through a filtering pipeline before a human being ever gets a choice about it. Some of that pipeline is a published rules system, and you can be precisely compliant with it. Some of it is a reputation system, and you can only influence it. Almost every failed attempt to "fix answer rates" fails because it applies a reputation remedy to a rules problem, or a rules remedy to a reputation problem.
Two Systems, Commonly Mistaken for One
These are genuinely separate. Different operators, different obligations, different failure signatures.
| Network blocking | Reputation labelling | |
|---|---|---|
| Who does it | Your provider and the terminating carrier, under a registered industry code. | Carrier screening services, handset operating systems, and third-party call-identification apps installed by the recipient. |
| What it decides | Whether the call is carried at all. | Whether the recipient sees a warning, a category label, or nothing. |
| Basis | Rules. Number validity, conformance, rights of use, format. | Statistics. Volume, duration, complaints, user blocks, crowd-sourced reports. |
| Symptom you see | Calls fail immediately or return an error. Nothing rings. Often 100% failure to a given destination network. | Calls connect and ring normally. Answer rate collapses. Failure is partial and varies by handset. |
| How fast you can fix it | Same day, once the configuration is corrected. | Weeks. Reputation is earned back through behaviour, not through a form. |
| Can you appeal | Yes — this is a compliance matter with a defined path through your provider. | Sometimes, partially, per vendor. There is no single register to correct. |
The diagnostic distinction, in one sentence
If your calls do not ring, it is a rules problem. If your calls ring and are not answered, it is a reputation problem. This one sentence saves most businesses several thousand dollars, because the rules problems are cheap to fix and the reputation problems cannot be fixed by buying anything.
What the Rules Actually Require
Australia's anti-scam framework on the voice side runs primarily through a registered industry code, C661:2022 Reducing Scam Calls and Scam SMs, which replaced the earlier 2020 code. Its purpose is to set out how providers identify, trace, block and otherwise disrupt scam calls and scam messages. It is a code registered with the ACMA, which means compliance is not optional for providers, and the ACMA has issued directions to comply where it found providers falling short.
Two of its consequences matter directly to a legitimate business making ordinary calls.
Invalid and non-conforming CLI is blocked
Since 2021, providers have been required to block outbound calls presenting calling line identification that is invalid or does not conform — unallocated ranges, malformed numbers, numbers that cannot exist in the Australian numbering plan. This is not discretionary filtering. A call presenting a number that is not a real Australian number is supposed to be stopped, and it is.
Rights of use matter
The code framework carries obligations directed at traffic using numbers the sender does not hold rights of use to. In plain terms: you may present a number your business actually holds, or one you have a documented right to present on behalf of the party who holds it. Presenting somebody else's number because it looks better is the exact behaviour the framework exists to stop.
CLI must be enabled for telemarketing
The telemarketing and research calls industry standard requires calling line identification to be enabled, and a number that can be called back to be available for at least 30 days afterwards. A withheld number on a telemarketing call is a standards problem before it is a deliverability problem.
The scale is not small
Providers have reported blocking more than 2.2 billion scam calls since December 2020 and more than 788 million scam SMS since July 2022, on ACMA figures. A filtering system operating at that scale will produce false positives, and legitimate businesses with sloppy configuration are exactly what a false positive looks like.
Read this the right way round
None of the above is a regulator being difficult. It is the reason your own staff receive far fewer scam calls than they did in 2020. The framework is working, and the cost of it working is that a business presenting a number it does not hold, or a number that does not exist, now looks exactly like the traffic the framework was built to stop. You are not being penalised for being a business. You are being caught by a rule you can comply with in an afternoon.
Six Reasons Your Calls Fail
In roughly descending order of how often they turn out to be the cause.
| # | Cause | Signature | Fix difficulty |
|---|---|---|---|
| 1 | Presenting a number you do not hold. Often inherited: an old head-office number kept after a move, a number belonging to a related entity, or a client's number presented by an agency dialling on their behalf without documentation. | Total or near-total failure to some networks, works fine to others. Inconsistent by destination. | Easy — present a number you hold, or document the authority properly. |
| 2 | Presenting an unallocated or malformed number. A typo in a trunk configuration, a number in a range that was never allocated, an international format where a national one is expected, an extension presented as a CLI. | Immediate failure, frequently on every destination. | Easy — one configuration correction. |
| 3 | Withholding CLI. Historically common for outbound teams who did not want callbacks. Now it is the fastest way to be ignored, and for telemarketing it is a standards breach. | Calls connect. Answer rate is catastrophic. Recipients report "private number". | Easy technically. Requires an operational decision about handling callbacks. |
| 4 | Presenting a number nobody can call back. Technically valid and allocated, but rings out, hits a disconnected recording, or reaches a mailbox nobody empties. | Calls connect. Answer rate declines steadily over weeks as reputation accumulates against the number. | Easy — route the number to something that answers. |
| 5 | Volume and duration profile. Hundreds of calls an hour from one number with a median duration of eight seconds looks, statistically, exactly like the thing being filtered — regardless of your intent. | Progressive degradation. Fine on Monday, poor by Thursday. Recovers slightly over a quiet weekend. | Moderate — requires changing how you dial, not what you present. |
| 6 | Accumulated complaint and block signals. Recipients pressing block, reporting the number in an app, or complaining. Each signal is small; they compound. | Slow decline over months, concentrated on mobile destinations. | Hard — this is reputation, and it is repaired by behaviour over weeks. |
Note where the difficulty sits. Causes one through four are configuration. They are free to fix, they are fixed same-day, and in our experience they account for the substantial majority of "our outbound stopped working" reports. Causes five and six are behavioural, take weeks to repair, and are the only ones people ever want to talk about. Check the cheap four first.
Presentation Numbers and Rights of Use
This is the single most misunderstood area, and it is worth being precise, because the wrong mental model here causes both compliance exposure and lost calls.
What it means to hold a number
Australian numbers are administered under the numbering framework the ACMA maintains. A carriage service provider is issued rights of use over ranges, and allocates numbers from them to customers. When your business is allocated a number, you hold a right of use over it for as long as the service continues — which is also why who holds the rights of use over your 1300 number matters so much when you change providers. Holding a number is what entitles you to present it.
Overstamping, and when it is legitimate
Presenting a CLI other than the one natively attached to the calling service is a normal, necessary function. A twelve-person office with forty extensions presents one main number. A field technician's mobile presents the office number so callbacks reach the office. A contact centre presents a state-based local number so the recipient sees a familiar area code. None of that is a problem.
It becomes a problem in exactly one situation: when the number being presented is not one your business holds or has documented authority to present. Two patterns cause almost all of the trouble.
| Pattern | Why it happens | What to do instead |
|---|---|---|
| The inherited number. A number from a previous provider, a closed office, or a merged entity is still configured as the presentation CLI years later. | Nobody audited the trunk configuration after the change. The number may since have been returned to the pool and reallocated to somebody else. | Audit every presentation CLI against your current service inventory. If you cannot point to the service it belongs to, stop presenting it today. |
| The agency dialling as the client. An outsourced sales, collections or appointment-setting operation presents the client's number so callbacks reach the client. | Commercially sensible and often what the client asked for — but frequently arranged in an email and never documented at the carriage level. | Keep this arrangement, and document it properly: written authority from the rights-of-use holder, held by the party presenting, and disclosed to the provider carrying the traffic. |
The uncomfortable one
If you run an outsourced calling operation and you present client numbers with nothing more than a verbal agreement, you have both a compliance gap and a deliverability risk, and the deliverability risk will bite first — silently, in the form of calls that never ring, on some networks only, with no error message reaching you. Fix the documentation because it is correct, and you will get a deliverability improvement for free.
Where the Scam Warning Comes From
A red banner reading something like "suspected scam" is not the same event as a blocked call, and it does not come from the code discussed above. It comes from a reputation layer, and there are at least four independent sources of it on any given handset.
Carrier screening
Network-side services that assess calls and either warn the subscriber or divert them. Opt-in or default-on depending on the carrier and plan.
Handset software
Operating-system features that silence, screen or flag unknown callers. Behaviour differs between platforms and versions, and the recipient may not know theirs is on.
Call-identification apps
Third-party apps built on crowd-sourced reports. A handful of users tagging your number is enough to produce a label that then shows to everybody with that app.
The recipient's own list
Personal blocks and "silence unknown callers" settings. Invisible to you, permanent until they change it, and entirely their right.
Three consequences follow, and they are worth internalising because they explain why this problem feels arbitrary.
| Consequence | What it means for you |
|---|---|
| You cannot see it. | Nothing in your call records indicates a label was shown. From your side a labelled call is indistinguishable from an ordinary unanswered one. This is why measurement has to be done with your own handsets. |
| There is no single register to correct. | Some vendors operate business-number registration or dispute processes. They cover their own product only. There is no central authority that clears a number everywhere. |
| It is not about legitimacy. | These systems infer intent from behaviour, because they have nothing else to work with. A legitimate business dialling like a scam operation gets treated like one. That is the system functioning as designed, not a malfunction. |
Carriers have also implemented anti-spoofing measures that examine whether a call arriving from outside the network presents a number belonging to that network — a pattern that is almost always spoofing and occasionally a badly configured legitimate business. If your calls fail specifically to one network and specifically when presenting a number allocated by that same network, this is worth raising with your provider.
Why Mobiles and Landlines Behave Differently
Most Australian business calling now terminates on mobiles, which is where nearly all of the labelling and screening capability lives. This produces a diagnostic signal worth using.
Fixed line
Little to no reputation labelling. If a call fails here, suspect a rules problem — CLI validity, rights of use, format.
Mobile
Full stack — carrier screening, OS features, apps, personal blocks. If a call rings here but is not answered while fixed-line answer rates hold, suspect reputation.
Per network
Screening defaults differ by carrier. Divergence between the three major networks is itself evidence, and tells you which conversation to have.
The point is not that one destination type is better. It is that comparing behaviour across destination types isolates the cause for free, using calls you were going to make anyway.
The Afternoon Diagnostic
Before you change anything, buy anything, or ring your provider, do this. It takes about two hours and it tells you which of the two problems you have — which determines everything you do next.
| Step | What to do | What it tells you |
|---|---|---|
| 1. Inventory | List every number your business presents on outbound calls, across every trunk, queue, dialler, softphone and mobile app. Beside each, write the service it is allocated to and who holds it. | Any row where you cannot name the service is cause 1 or 2, and you have found your problem before making a single call. |
| 2. Call back every one | Ring each presented number from an outside line. Time how long it takes to reach a human or a monitored mailbox. | Any number that rings out, plays a disconnection message, or reaches an unmonitored mailbox is cause 4. |
| 3. The four-handset test | From your own platform, place a call presenting each number to a mobile on each of the three major networks and to a fixed line. Photograph the screen. Note ring, no-ring, label, silence. | No ring anywhere is a rules problem. Rings everywhere with a label on mobiles is reputation. Divergence by network narrows it to one carrier's screening. |
| 4. Pull the numbers | For each presenting number over the last 90 days: attempts, connects, median duration, and the proportion under 10 seconds. | High volume with a very low median duration is cause 5, and no configuration change will fix it. |
| 5. Ask the recipients | On the next twenty calls you do connect, ask: "out of interest, what did my call show up as on your phone?" | The only direct visibility available into the labelling layer. Twenty answers is usually enough to see the pattern. |
| 6. Then ring your provider | Present the inventory, the four-handset results and the 90-day figures. | Turns an unanswerable question into a specific one. A provider can act on "this number fails to this network from this trunk"; nobody can act on "our calls do not work". |
Do step 1 even if you think you know
The inventory is the step everyone skips and it is the step that most often ends the investigation. Businesses that have changed provider, moved office, acquired another entity, or added a dialler at any point in the last five years very frequently discover a presentation number nobody can account for. That is not carelessness — it is what happens when four systems each hold their own copy of a setting and nobody owns the list.
The Fix, in Order of Impact
Ordered by expected improvement per hour of effort, not by how interesting each one is.
| Action | Effort | Effect | |
|---|---|---|---|
| 1 | Present a real number you hold, on every outbound call, consistently. Allocated, dialable, answered, and the same one every time for a given team or purpose. | Hours | Resolves the rules problems outright and starts building the only reputation asset you actually control. |
| 2 | Make every presented number reach a human quickly. A queue, a receptionist, or an AI answer that identifies the business and takes a message. Never a ring-out. | Hours | Removes cause 4 and materially changes how recipients respond to a number they do not recognise but can verify. |
| 3 | Stop withholding CLI anywhere. Including on mobiles and softphones used by field staff. | Hours | Large. Withheld numbers are close to unanswerable in 2026, and for telemarketing this is also a standards requirement. |
| 4 | Document rights of use for every number you present on behalf of someone else. Written authority from the holder, held by the presenter. | A day | Closes the compliance gap and removes the most common silent-failure cause for agencies. |
| 5 | Spread outbound load across purpose-specific numbers. Not a rotating pool designed to evade filtering — separate numbers for genuinely separate functions, each of which answers. | Days | Moderate. Reduces the single-number volume profile without pretending to be many businesses. |
| 6 | Change the dialling pattern. Fewer attempts, longer gaps, no repeat dialling within a short window, and stop calling numbers that have never once connected. | Weeks | The only real remedy for cause 5. Also reduces complaint generation, which is what feeds cause 6. |
| 7 | Warm the call. An SMS or email before the call, so the number is expected. Requires a lawful basis for the message. | Weeks | Frequently the largest single answer-rate improvement available, because it converts an unknown number into an expected one. |
| 8 | Register with the labelling vendors that offer it. Per-vendor, product-specific, no central register. | Days | Small to moderate, and only after the first six. Doing this before fixing configuration is how businesses conclude "we tried everything". |
Two of these deserve emphasis. Item 2 is undervalued because it is framed as an inbound improvement. A recipient who missed your call and rings the number back is your highest-intent contact of the day; if that number rings out, you paid for the outbound call and threw away the result. And item 7 changes the question the recipient is answering — not "should I answer an unknown number?" but "is this the call I was told about?" Those produce very different behaviour. Our note on sending SMS from the same system that makes the calls covers the mechanics; the Do Not Call Register and outbound calling rules cover when you may.
The SMS Side, and Why It Is a Separate System
Messaging has its own regime and it is worth keeping the two apart in your head, because the labelling behaviours look similar and have entirely different causes.
The SMS Sender ID Register came into operation under an ACMA standard, required to be implemented in full by no later than 15 December 2025, and from 1 July 2026 messages sent from unregistered alphanumeric sender IDs are labelled as unverified and grouped in a single thread on the recipient's handset. Registration checks draw on Australian Business Register information. That is a register with a defined process and a defined outcome.
Do not generalise across the two
There is no voice equivalent of the Sender ID Register. Registering your sender IDs does nothing for your call answer rates, and a clean voice configuration does nothing for an unverified label on your messages. Businesses regularly assume one fixed the other, then conclude the fix did not work. Treat them as two separate pieces of work with two separate checklists. Ours on the messaging side is the Sender ID Register guide, with what the unverified label looks like in practice.
What AI Dialling Changes
AI-assisted outbound is now genuinely useful, and it changes the risk profile in both directions.
| What improves | What gets riskier |
|---|---|
| Fewer, better-targeted attempts. The single most effective way to protect a number's reputation is to stop dialling contacts who will never answer, and this is exactly the kind of prediction that works well. | Volume becomes cheap. When an agent costs cents rather than minutes of a person's time, the constraint that used to keep dialling patterns sane disappears — and the filtering layer notices. |
| Consistent disclosure. An AI agent can be relied on to identify the business and state the purpose on every single call, which humans under pressure do not. | Complaint sensitivity rises. An automated call that is unwanted generates complaints more readily than a human one, and complaints feed the reputation layer. |
| Instant callback handling. Every presented number can be answered immediately, at any hour, which is remedy 2 above solved permanently. | Regulatory exposure. Telemarketing standards on disclosure, hours and CLI apply regardless of whether a human or a system is speaking, and from 10 December 2026 automated decisions affecting a person's rights or interests carry a privacy-policy disclosure obligation. |
The net position: AI is a strong remedy for causes 2 and 4 and a strong accelerant for causes 5 and 6. Use it to make fewer, better calls that always answer their own callbacks — not to make more calls. We set out the boundaries in which calls to automate and the December 2026 automated-decision obligation.
Four Things That Do Not Work
Rotating through disposable numbers
Burning a number every few weeks and moving to the next is the defining signature of the traffic being filtered. It works briefly, trains the systems to distrust your whole range, and leaves you with a set of numbers nobody answers.
Local-area numbers as a trick
A local number for a region you genuinely operate in and answer calls to is legitimate and sensible. Dozens of area codes for an office in one city, presented to make calls look local, is neighbour-spoofing — heavily filtered and increasingly recognised by recipients.
Hiding the number
Withholding CLI to avoid callbacks, complaints or block lists. It removes the recipient's ability to verify you, which is the one thing that makes an unknown number answerable — and for telemarketing it breaches the standard.
Paying for a clean-up before fixing configuration
Reputation services and per-vendor registrations have a real, modest place — after the configuration is correct. Bought first, they produce no improvement, because they do not address a rules problem, and the business concludes nothing can be done.
What all four have in common: they try to change how the call appears rather than what the call is. The systems on the other side are specifically built to see through appearance and measure behaviour. The remedies that work all involve becoming easier to verify — a real number, answered, used consistently, called back promptly — because verifiability is the actual signal being measured.
How We Handle This
We are a carriage service provider, so this is our compliance obligation as well as your problem, and it is worth saying what that means concretely.
Numbers we allocate to you are allocated to you, and the rights of use are documented — which is what makes them portable when you leave and presentable while you stay. We will configure presentation numbers per team, per site, per queue and per mobile app, and we will tell you if a number you have asked us to present is one we cannot verify you hold, rather than passing traffic that will fail quietly on some networks. When outbound calls to a particular destination network start failing, we can look at what the trunk actually presented and trace it, because we operate the platform and the network rather than reselling somebody else's.
What we cannot do, and nobody can, is clear your number in a labelling system we do not operate. What we can do is make sure that when a recipient checks whether you are real — by ringing the number back, which is what people actually do — the answer is immediate and obvious. That is the part of your reputation you own.
The summary
If your calls do not ring, it is a rules problem: CLI validity, format, rights of use. Those are same-day configuration fixes and they are free. If your calls ring and are not answered, it is a reputation problem driven by volume, duration, complaints and blocks — repairable only through weeks of different behaviour. Run the inventory first, because a presentation number nobody can account for is the single most common finding. Present one real number per purpose, make sure it answers, never withhold CLI, and document authority for any number you present on someone else's behalf. Then, and only then, consider per-vendor registration. And keep voice and SMS separate: the Sender ID Register fixes message labelling and does nothing at all for your answer rate.
Related reading: the Do Not Call Register and outbound calling rules, the SMS Sender ID Register, protecting your phone system from toll fraud, who owns your 1300 number, and the Scams Prevention Framework and what it asks of telcos.