1300 Comms Portal — Setting Up Location Zone Routing
Published:
Overview
This guide explains how to configure location-based call routing using zones in the Fone Dynamics Portal Flow Designer, routing incoming calls to different endpoints based on the geographic zone of the caller.
Steps to Set Up Location Zone Routing
- Log in to the 1300 Comms Portal.
- Navigate to the Flow Designer and open the relevant call flow.
- Locate the Location action in the actions panel and select the Zone option.
- Drag the Zone action onto the canvas and connect it to the Incoming Call node.
- Click on the Zone action to configure it.
- Click Browse and upload the CSV zones file containing the phone number, zone name, and moli code mappings.
- Click Save on the Zone action.
- Configure the two routing paths the zone node creates:
- Condition Met — the caller’s location matches a zone entry in the CSV file; the call is forwarded to the corresponding destination number defined in the file
- Condition Not Met — the caller’s location does not match any zone entry; set this path to Hangup or an alternative routing action
- Click Save to save the flow, then click Publish to make the flow live.
Steps to Prepare the Zones CSV File
- Create a CSV file with the following columns:
- Phone Number — the destination number calls should route to for this zone
- Zone — the name of the zone (e.g. Warnambool)
- Moli Code — the moli code for the zone (required for mobile call routing)
- For each zone, add two entries — one using the zone name and one using the moli code:
- Row 1: destination number, zone name (e.g. Warnambool)
- Row 2: destination number, moli code for the same zone
- Repeat double entries for every zone in the file.
- Save the file in CSV format and upload it via the Zone action in the flow.
Key Notes
| Item | Details |
|---|---|
| Zone Action | Found under Location in the actions panel — routes calls based on the geographic zone of the incoming caller |
| CSV File | Must include Phone Number, Zone Name, and Moli Code columns for each zone |
| Double Entry Requirement | Each zone must have two rows — one for the zone name and one for the moli code — otherwise mobile calls will not route correctly |
| Moli Code | Required for routing calls coming from mobile numbers — without it, mobile callers will not match the zone |
| Condition Met Path | If the caller’s zone matches a CSV entry, the call forwards to the mapped destination number |
| Condition Not Met Path | If no zone match is found, the call follows this path — set to Hangup or an alternative action |
| Save vs Publish | Use Save to store changes, then Publish to make the updated flow active and live |
