VOX Logo
Sign Up
Intelligent Dispatch

One national number routed anywhere in Australia.

Voxworks AI-powered call routing places callers with the exact team from a brief initial exchange. Voxworks confirms the location, urgency and job type, then immediately connects the caller to the right local team with a warm handoff, post-transfer transcription and call analysis.

Illustrative routes. Your network, your rules.A caller describes their problem and location. Voxworks confirms the location, applies the business’s territory rules, and connects the call to the appropriate local team with the job details. Choose a city to see an example. Current example: Lane Cove, NSW, routed to the Sydney North team. Hydraulic hose failure · equipment stopped.

What is intelligent dispatch?

AI understands the caller's location and places the call with the right team every time.

Voxworks Intelligent Dispatch is an AI call routing system for national businesses that take calls centrally with a redirect to local teams. Intelligent call routing immediately resolves transfer logic such as office hours and franchise territory rules, and adds structured intake, emergency handling, warm handover and a recovery plan when a transfer cannot connect.

Intelligent Dispatch is designed to replace clunky IVR menus and DTMF postcode input machines with a more conversational experience that reduces friction and enhances transparency around your first customer touchpoint.

How it works

Rapidly connect to the right local team.

  1. 1

    Caller speaks naturally.

    The caller explains their request and location in their own words.

  2. 2

    AI captures the key details.

    Your intake flow asks about the site, issue, equipment, urgency and caller. Location and urgency are confirmed before routing.

  3. 3

    Your territory rules apply.

    State and suburb resolve to an approved locality, with postcode as a fallback. Your coverage and suburb exceptions decide the destination.

  4. 4

    Warm transfer with context.

    The receiving team hears a short job summary before the caller is connected. The customer does not have to start again.

  5. 5

    If unanswered, recover.

    Your configured recovery flow can try an on-call team, notify the branch, arrange a callback or route to backup.

Key Features

Dispatch that understands the caller and respects your rules.

Head office keeps control of territories, opening hours and escalation. Voxworks handles the conversation around them.

  1. 01 / 08

    Location matching with Australian place names

    Voxworks stores a database of 18,000+ Australian placenames together with common mistranscriptions. Every single location in Australia is matched to a transfer endpoint. If the AI cannot resolve the location, we ask the caller for postcode and use the example to help the system self-improve. This results in high accuracy location matching.

    Location matching18,000+ placenames
    Heard on the call
    • “Lane Cove”
    • “Lain Cove”
    • “Lane Cov”

    Common mistranscriptions resolve to the same place.

    Candidates · New South Wales
    1. Lane Cove, NSW2066
    2. Lane Cove North, NSW2066
    3. Lane Cove West, NSW2066
    Matched endpoint

    Sydney North team

  2. 02 / 08

    Configure custom territory rules

    The caller's distance to the nearest location is immediately calculated, with suburb exceptions taking priority. Where two centres cover an area, the caller is offered multiple choices.

    Territory rulesHead office controls
    Nearest approved centres
    • Sydney North6.2 km
    • Sydney CBD8.1 km
    • Parramatta14.7 km
    Suburb exceptionTakes priority

    Lane Cove 2066 → Sydney North, regardless of distance.

    Overlapping coverageCaller chooses

    Where two centres cover an area, the caller is offered both.

  3. 03 / 08

    Schedule-aware routing

    Each destination has its own opening hours, public-holiday handling and timezone. Closed destinations follow the configured fallback route, such as an after-hours technician.

    Destination schedules19:42 AEST

    • Perth depot

      AWST · 17:42

      Open

    • Adelaide branch

      ACST · 19:12

      Public holiday

    • Sydney North

      AEST · 19:42

      Closed
    Sydney North is closedConfigured fallback: after-hours technician
  4. 04 / 08

    Fallback chains

    Link closed destinations to an after-hours technician, neighbouring branch or national queue. Configure separate recovery steps for transfers that cannot connect.

    Fallback chainsPer destination
    Sydney NorthClosed destination
    1. Sydney NorthClosed · 19:42
    2. After-hours technicianOn-call roster
    3. Neighbouring branchSydney CBD · open late
    4. National queueAlways available
    Transfer cannot connectSeparate recovery steps
    1. No answerRing timeout reached
    2. Try on-call numberSecond attempt
    3. Notify branchSMS with captured context
    4. Arrange callbackWindow recorded
  5. 05 / 08

    Warm handover with context

    Give the receiving team a private spoken summary before connecting the caller. Choose a cold transfer for routes where speed matters.

    Transfer mode
    WarmCold
    Receiving team hearsPrivate

    “Breakdown enquiry. Excavator with a blown hydraulic hose in Lane Cove, machine down. Caller is Dave. Connecting you now.”

    The summary plays before the caller is bridged.

    Caller hearsOn hold · 9s
    “Thanks Dave. I’m connecting you to the team covering Lane Cove now.”
    Connected to Sydney North with context
    1. 1Team answers
    2. 2Spoken summary
    3. 3Caller bridged
    4. 4Transcript sent
  6. 06 / 08

    Urgency triage

    Ask the questions that distinguish a machine-down breakdown from a routine enquiry, then follow the appropriate escalation policy.

    Urgency triageMachine down
    Your triage questions
    • Is the machine stopped?Yes
    • Is anyone at risk on site?No
    • Is the site accessible now?Yes
    Escalation policy applied
    Breakdown · urgentNow
    • Route to on-call technician first
    • SMS the branch manager
    • Skip the general queue
    Routine enquiryNext business day

    Standard branch queue, transcript emailed to the office.

  7. 07 / 08

    Post-call capture

    Send a transcript and summary by email or webhook. Configure SMS alerts and structured callback details so unresolved jobs have a next step.

    After the call3 actions sent
    Email · Sydney North

    Dispatch: Excavator breakdown · Lane Cove NSW

    Caller
    Dave · site contact
    Urgency
    Machine down
    Issue
    Hydraulic hose failure
    Routed to
    Sydney North · connected
    Full transcript and summary attached.
    SMS · Branch manager

    Urgent job routed to Sydney North. Excavator down, Lane Cove. Callback window: before 8:00am.

    Webhook · Job system
    { "intent": "breakdown",
  "site": "Lane Cove NSW",
  "urgency": "machine_down",
  "callback_by": "08:00" }
  8. 08 / 08

    Head-office visibility

    Routing decisions are written to an audit log. Review the matched location, chosen destination and routing outcome alongside the call record.

    Routing audit log
    TodayAll branches
    TimeMatched locationDestinationOutcome
    19:42Lane Cove NSW 2066heard “Lane Cove”On-call technicianConnected · after hours
    16:05Richmond VIC 3121heard “Richmond”Melbourne EastConnected
    14:18Newstead QLD 4006heard “Newstead”Brisbane CentralRecovered · callback
    11:31Spearwood WA 6163heard “Postcode 6163”Perth depotConnected
    Every row links to the call record, transcript and summary.

Illustrative examples. Your destinations, territories and schedules are configured for your network.

When the transfer fails

AI stays with the customer and finds a route.

An unanswered transfer should have a next step. When a transfer cannot connect, the AI stays with the caller and follows your configured escalation policy.

Caller’s location confirmed

Correct branch rings

Does the team answer?

  • Yes · connected

    Warm handoff with context.

    The team hears the job summary, then the caller joins. The details travel with the call.

    Right team. Context already captured.

  • No · transfer cannot connect

    AI stays with the caller.

    Follow the recovery options in your escalation policy. The caller’s details stay attached to the next step.

    No voicemail dead-end.

Your recovery options

Choose the steps and order for your network during setup.

  • Try the on-call number.

    Give the after-hours technician or on-call team the next opportunity to take the job.

  • Notify the branch.

    Send an SMS or email with the captured context so the team can follow up.

  • Arrange a callback.

    Ask for a preferred callback window and record it with the job details.

  • Route to backup.

    Connect to a neighbouring centre or the national team, with the context still attached.

Built for national networks

One 13 number. Many teams. Consistent intake.

AI call dispatch for businesses with complex routing requirements.

Franchise networks

Give callers to the national number a consistent first response while respecting each franchise’s territory.

Field service and breakdown response

Identify urgent equipment failures and route the job to the team covering the site.

Trades with regional depots

Send enquiries to the right depot and follow its on-call arrangements when the office closes.

Explore

Facilities and property maintenance

Confirm the property location and urgency before connecting the caller to the responsible maintenance team.

Explore

Towing and roadside

Capture the caller’s location and vehicle issue before handing over to the approved local operator.

After-hours contact-centre overflow

Keep intake and escalation working when the central team is offline or unable to take the call.

Under your control

Australian-hosted, audited, under your control.

  • Natural Australian voices and Australian data residency.
  • Every routing decision written to an audit log.
  • Head office approves territory rules. The AI cannot invent a destination.
  • A recording notice is included at the start of the dispatch flow.
  • Transfer numbers stay in the routing system and are not exposed to the AI model.

Questions

Intelligent dispatch FAQs

  • No. Voxworks imports your approved postcode and suburb coverage and applies those rules. Suburb exceptions keep their priority, and head office controls changes.

  • Each destination has its own schedule, including timezone and public-holiday handling. When a branch is closed, the call follows the fallback route you define, for example to an after-hours technician or your national team.

  • The AI asks for a four-digit postcode and checks it against your coverage rules. If the location still cannot be matched, the call goes to the national fallback team you have configured.

  • With a warm transfer, the team hears a short spoken summary of the job before the caller is connected. Post-call actions can send the transcript and summary by email or webhook, with SMS notifications configured as needed.

  • The dispatch flow follows the recovery steps agreed during setup. These can include trying an on-call team, notifying the branch, recording a callback window or routing to a backup team. Closed-destination fallback and recovery after an unsuccessful transfer are configured for your network.

  • Yes. The recommended pilot keeps your existing dispatch during hours and enables AI for after-hours calls and failed transfers. Review connection, recovery and branch impact before expanding.

  • Yes. Point your 13, 1300 or local number at Voxworks. Your branch numbers stay as they are. We help set up the forwarding and approved destinations for your network.

Start with a focused pilot.

We help configure your locations, phone endpoints, territory rules and recovery flow.

  1. 01

    Keep existing dispatch during office hours.

    Your team keeps handling daytime calls while we design the geographic coverage and escalation policy.

    Existing daytime dispatch

  2. 02

    Enable AI when calls need outside hours cover.

    Begin with failed transfers and after-hours calls, using the same approved destinations and territories.

    After hours · Failed transfers

  3. 03

    Measure the branch impact and expand.

    Review connection, recovery and callback outcomes with your teams before expanding coverage.

    Connection · Recovery · Branch feedback

Book a demo