Skip to content

Industries

Voice agents for public services

Help citizens reach the right information or service in their language while preserving a clear route to public employees and emergency channels.

SECTOR REALITY · BELGIUM

The right service from the first contact.

37%

of Belgians surveyed still preferred speaking to an employee by phone over using a website or email in 2025

DataSynergy survey for THoCC. This is a stated channel preference; it shows the importance of telephone contact, not voice-agent performance.

Citizen-service friction

  • Citizens do not always know which level of government or institution owns their request, so contacts often begin at the wrong service.
  • Status, procedure and deadline questions repeat, but the answer must remain accessible, multilingual and tied to the real case.

Direct operational utility

  • Identify the topic, location and language, then route to the competent service with guidance from an approved source.
  • Handle simple procedural questions or an authorised status check and hand over whenever a decision or interpretation is needed.

01 · Concrete applications

From a citizen question to the right public service

Banana Navy public-service voice assistant with routing and information flows
  1. 01

    Explain practical procedures from approved public information.

  2. 02

    Identify the municipality, service or topic concerned.

  3. 03

    Create a structured request or callback task.

  4. 04

    Redirect emergencies and sensitive situations to the appropriate human channel.

02 · Operating model

Three layers of needs, designed together.

01

Citizen orientation

  • Identify the municipality, service and topic concerned.
  • Provide practical information from the approved public source.
02

Request creation and follow-up

  • Structure a service request with the necessary reference details.
  • Create a ticket or callback task when the connected system permits it.
03

Sensitive and urgent routing

  • Recognise configured urgency or vulnerability signals.
  • Redirect the caller to the competent employee or published emergency channel.

03 · Call journey

From the first sentence to the right next step

  1. 01

    Receive

    The citizen calls the published service number.

  2. 02

    Understand

    The agent identifies language, location and request.

  3. 03

    Check

    It checks the competent service and the approved information source.

  4. 04

    Act

    It answers, records a request or proposes the correct channel.

  5. 05

    Hand over

    A public employee takes over when judgement, identity checks or urgency are involved.

04 · Connected tools

The systems involved

  • Public telephony
  • Validated information portal
  • Citizen-request or ticketing system
  • Directory and routing rules

06 · Questions

Questions to frame the deployment.

01Which citizen requests can a voice agent handle?

It can answer defined practical questions, identify the competent service and prepare a request. Eligibility decisions, disputes and situations requiring public authority stay with employees.

02Can it connect to an existing citizen portal?

It can use an available API or approved workflow to consult information or create a request, provided the access scope and permitted fields are defined and tested.

03Does it replace an emergency line or public employee?

No. It should clearly state its scope and redirect emergencies, contested cases, identity-sensitive requests and decisions to the appropriate human channel.

04How are languages and personal data handled?

The selected languages should be tested with local terminology and accents. Only data required for the configured request should be collected, under the organisation’s chosen access, retention and hosting rules.

Banana Navy · Voice AI

Start with your real call scenarios.

We map the journey, permitted actions, integrations and human handover before choosing the architecture.

Call our Voicebots