1300 Comms Portal — Setting Up Postcode Routing
Published:
Overview
This guide explains how to configure a postcode-based call routing flow in the 1300 Comms Portal Flow Designer, routing incoming calls to different endpoints based on the caller’s postcode input.
Steps to Set Up Postcode Routing
- Log in to the 1300 Comms Portal.
- Navigate to the Flow Designer.
- Click New Flow, enter a name for the flow (e.g. Postcode Routing), and click Create.
- Locate the Location action in the actions panel and select the Postcode option.
- Drag the Postcode action onto the canvas and connect it to the Incoming Call node.
- Click on the Postcode action to configure it.
- Click Browse and upload the CSV file that contains the postcode-to-number mapping.
- Click Save on the Postcode action.
- Configure the two routing paths the postcode node creates:
- Condition Met — the caller’s postcode matches an entry in the CSV file; the call is forwarded to the corresponding endpoint defined in the file
- Condition Not Met — the postcode does not match any entry in the CSV file; 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 Postcode CSV File
- Create a CSV file with two columns:
- Column 1 — Postcode (e.g. 2000)
- Column 2 — Destination number the call should route to
- Add one row per postcode-to-number mapping.
- Save the file in CSV format and upload it via the Postcode action in the flow.
Key Notes
| Item | Details |
|---|---|
| Postcode Action | Found under Location in the actions panel — routes calls based on caller postcode input |
| CSV File | Must contain two columns: postcode and destination number — one mapping per row |
| Caller Input | When a call lands, the system prompts the caller to enter their postcode as a keypad input |
| Condition Met Path | If the postcode matches a CSV entry, the call is forwarded to the mapped destination number |
| Condition Not Met Path | If no 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 |