If you run a 1300 or 1800 number for a business with branches in more than one city, someone has almost certainly mentioned MOLI codes to you: probably in passing, probably without explaining them. They’re the mechanism that lets a single advertised number send a caller in Perth to your Perth office and a caller in Brisbane to Brisbane.
They’re useful. They’re also less precise than the sales pitch suggests, and understanding the gap is what stops you designing a call flow that quietly annoys a portion of your customers.
1. What a MOLI Code Is
MOLI stands for Mobile Origin Location Indicator. You’ll also see the same acronym expanded as Mobile Location Information, and written as "MoLI" in industry documents. They refer to the same underlying concept.
A MOLI code is a short numeric code, three digits, that identifies the approximate geographic area a mobile call originated from. The originating mobile carrier attaches it to the call as it’s handed over, so the receiving service can tell roughly where the caller was standing when they dialled.
Each code maps to a named area in a lookup table maintained by the Australian telecommunications industry body (Communications Alliance, now operating as the Australian Telecommunications Alliance). The table covers the whole country, from the capital cities through to regional centres. As published examples, 001 corresponds to Sydney and 120 to Perth; your provider will supply, or point you at, the current full list.
2. Why They Exist
The problem MOLI solves is specific to mobiles. A landline number carries its geography in the number itself: an 02 number is in New South Wales or the ACT, an 08 number is in WA, SA or the NT. A network handling a call from a landline already knows roughly where it came from.
Mobile numbers carry no geographic information at all. An 04 number tells you nothing about where the person is; Australians keep their mobile numbers when they move interstate, and the number was never tied to a place to begin with. When the overwhelming majority of calls to a national 1300 number arrive from mobiles, "route this caller to their nearest branch" becomes impossible without extra information.
MOLI is that extra information: a location signal generated by the network based on where the call entered it.
3. How the Code Reaches Your Phone System
- A customer dials your 1300 number from a mobile.
- The originating mobile carrier identifies the area the call is coming from and attaches the corresponding MOLI code.
- The inbound number service receives the call along with the code.
- Your routing plan, configured with your provider or in your phone system portal, reads the code and selects a destination.
- The call is delivered to that destination, and the code is typically also available in your call records and reporting.
Two important boundaries:
- MOLI information travels on inbound numbers only: 13, 1300 and 1800 services. It has no effect on ordinary geographic numbers, so pointing your 02 number at multiple branches won’t give you location routing.
- Landline-originated calls carry no MOLI. Your routing plan needs a defined behaviour for calls with no location data, which for landlines usually means routing on the caller's area code instead.
4. Using MOLI for Location-Based Routing
A typical multi-branch routing plan looks like this:
| Call Origin | Signal Used | Destination |
|---|---|---|
| Mobile, Sydney region MOLI | MOLI code | Sydney queue |
| Mobile, Perth region MOLI | MOLI code | Perth queue |
| Mobile, regional MOLI with no branch | MOLI code → state mapping | Nearest state office |
| Landline, 03 area code | Calling number | Melbourne queue |
| No location data available | Fallback rule | National queue or IVR question |
Most providers let you group MOLI codes so you’re not maintaining hundreds of individual rules. You assign whole regions or states to a destination and refine only where you actually have a branch. Layer time-of-day rules on top and you can also use location routing to follow the sun across Australian time zones, sending early east-coast calls to a site that’s already open.
5. The Accuracy Problem
This is the part worth taking seriously. MOLI granularity is regional, not suburban. A single code can cover a very large area, particularly outside the capitals, so it will reliably tell you "this caller is in south-east Queensland" and won’t reliably tell you "this caller is in Chermside rather than Ipswich".
Other limitations to design around:
- It reports the network's view, not the caller's intent. Someone driving through Albury to get to a job in Wagga is routed on where they are, not where the work is.
- Travellers are misrouted by definition. A Melbourne customer ringing from a Gold Coast holiday gets your Queensland branch, which may know nothing about their account.
- Coverage boundaries aren’t administrative boundaries. Areas reflect network coverage groupings, so a caller near a state border may present a code from the other side of it.
- No data is a normal case, not an error. Landline calls and some routing paths simply have no MOLI, and your plan must handle that gracefully.
The rule of thumb
Use MOLI to make a good default choice, never a locked-in one. Route the caller to the most likely branch, then let the person answering transfer them in one step if the guess was wrong. Businesses that treat MOLI as authoritative, refusing to serve a caller because the code says they belong to another region, create exactly the experience the routing was supposed to prevent.
Where precision matters (dispatching a technician, quoting a delivery) combine the two: use MOLI to pre-select the likely region, then confirm with a single question. An AI voice agent is well suited to this, since it can simply ask "which suburb are you in?" and route on the answer, using the MOLI code as the fallback if the caller doesn’t answer clearly.
6. MOLI and Triple Zero
The same underlying idea appears in Australia's emergency call service, and the two contexts are often confused, so it’s worth separating them.
When someone calls Triple Zero from a mobile, the originating carrier passes a location indicator to the emergency call service so the call can be directed to the right emergency service organisation for that area. This has been governed by industry guidelines for many years. The Australian Telecommunications Alliance publishes standards covering mobile location indicators and location information for emergency calls and the location areas correspond to standardised mobile service areas that group network cells together.
Since around 2015, that has been supplemented by more precise handset-derived location data being pushed to emergency services. The broad location indicator remains part of the picture, but it’s not the only signal any more.
For a business, the practical connection is this: MOLI doesn’t help emergency services find your staff. Emergency call location for your phone system depends on the service address you’ve registered, which is a separate obligation. If your team works remotely or across sites, see the emergency calling section of our compliance guide and make sure anyone calling Triple Zero states their actual location out loud.
7. A Practical Routing Design
For a business with three branches and a single 1300 number:
- Map your branches to MOLI groups, not individual codes. Assign each state or major region to the branch that should own it.
- Set a fallback for every gap. Regions with no branch, landline callers, and calls with no location data all need an explicit destination.
- Add a confirmation step where it matters. "It looks like you're calling from Western Australia, is that right?" costs three seconds and prevents the worst misroutes.
- Make transfer between branches one click. Misroutes are inevitable; a painful transfer is not.
- Log the MOLI code against every call. After a month you’ll know exactly where your calls originate, which is useful marketing data as well as a way to check whether your routing groups are sensible.
- Review quarterly. If a large share of calls is routing to the national fallback, your groupings need work.
Don’t overbuild this. A two-branch business usually needs three rules and a fallback, not a fifty-rule matrix. Complexity in a routing plan is paid for by whoever has to debug it at 8am on a Monday.
8. Questions for Your Provider
- Does my inbound number service support MOLI-based routing, and is it included or an add-on?
- Can I group MOLI codes into regions myself, or does every change require a support request?
- Is the MOLI code exposed in my call records and reporting?
- What happens to calls with no MOLI data, and can I set that fallback?
- Can I combine MOLI routing with time-of-day and overflow rules?
- Can the code be passed to my CRM or screen pop so the agent sees where the caller is?
Question 2 matters more than it looks. Location routing is only valuable if you can adjust it when you open a branch, close one, or change trading hours and a provider who charges for each change will leave you running a routing plan that stopped matching your business two years ago.