Contact centre software Channel-independent Case management integration

Custom customer contact system development

Appfront builds a custom customer contact system (CCS) for your customer contact centre (CCC). Enquiries from residents and businesses arrive by phone, front desk, web, email and chat in a single system, where your staff log and handle them. It includes a knowledge base for first-line answers, referral to the specialist departments, an integration with your case management system and clear management information on customer contact.

What is a customer contact system?

A customer contact system (CCS) is the software a municipal customer contact centre (CCC) uses to organise contact with residents and businesses. It brings all channels together (phone, front desk, web, email and chat) so an enquiry is logged and handled in one place, however it arrives. The staff member sees the contact history and can answer many questions straight away at first line using a knowledge base.

In practice, a custom CCS means: logging and routing contacts across all channels, first-line answers from an up-to-date knowledge base, referral and escalation to the right specialist department, an integration with the case management system via the ZGW APIs, and identification of the resident via DigiD. On top of that, the system provides management information on volumes, channels and topics.

Custom often fits better than an off-the-shelf package when your way of working, channel mix or integrations differ from what a package offers. Instead of adapting your processes to the software, we build the software around your processes, extensible and without depending on a vendor's roadmap. A CCS fits in with our broader software for municipalities.

One customer view across all channels

Phone, front desk, web, email and chat come together in a single record. The staff member sees previous contacts and open cases, so residents don't have to explain their situation over and over again.

First-line answers with a knowledge base

An up-to-date knowledge base, maintained by the specialist departments, shows the right answer for the subject of the contact. This way, a large share of enquiries is resolved straight away without transferring.

Integration with the case management system

Via the ZGW APIs, the CCS reads the status of open cases and logs new enquiries or reports as a case. Specialist departments pick up the escalation in their own environment, with a traceable handover.

Our development process for a customer contact system

We work to a methodology that removes uncertainty early and delivers a stable system. From an initial analysis of your contact centre processes, channels and integrations through to go-live and ongoing maintenance, every step is aimed at a customer contact system your own organisation can understand and manage.

1
Analysis & scope

We map your contact centre processes: which channels come in, how enquiries are logged and routed, which specialist departments pick up escalations, and which integrations with the case management system and data sources are needed.

2
Design

We design the architecture, the data model for contacts and the customer view, the knowledge base structure and the integrations via the ZGW APIs and DigiD, with attention to accessibility and security.

3
Build and iteration

We build in short iterations with automated tests, structured logging and monitoring. You'll see working versions along the way and help steer the project based on what the KCC (customer contact centre) needs in practice.

4
Go-live & maintenance

A controlled go-live with data validation and a safety net, followed by ongoing maintenance, monitoring and further development of the customer contact system.

What a customer contact system delivers in practice

Every customer contact system is configured around your channels, your KCC way of working and the systems it connects to. Below are the features we deliver most often for municipalities and public-sector organisations with public contact.

Contact registration across all channels

Enquiries via phone, front desk, web, email and chat are registered in a single system, with subject, channel and handling status. Staff work from one screen and don't have to switch between separate systems.

Knowledge base for the front line

A central knowledge base, maintained by the specialist departments, with up-to-date answers to frequently asked questions. The system suggests relevant articles based on the subject, so the front line can resolve a large share of enquiries straight away.

Referral and escalation

Enquiries that don't belong in the front line are passed on to the right specialist department, together with the context of the contact. The handover is traceable, so it stays clear who has picked up an enquiry and what its status is.

Integration with the case management system and data sources

Integration with the case management system via the ZGW APIs to retrieve case statuses and register new cases, plus resident identification via DigiD. Where needed, we connect additional data sources to build a complete picture of the customer.

Self-service and status enquiries via the web

Web forms and self-service that let residents submit or view simple enquiries or status requests themselves. These flow into the customer contact system as registered contacts, so the channel follows the same handling process as phone and front desk.

Management information and reporting

Insight into volume per channel, recurring topics and the share handled in the front line. This lets the KCC plan staffing and see where the knowledge base or service can be improved.

Which organisations and processes it suits

A customer contact system is used by a range of public organisations with public contact. The common thread is always the same: register enquiries across multiple channels, resolve as many as possible in the front line, and pass the rest on to the specialist department in a targeted way.

Municipal customer contact centres

A municipality's KCC handling enquiries from residents and businesses via phone, front desk, web, email and chat. Front-line answers via the knowledge base, referral to specialist departments and an integration with the case management system. Fits within our broader software for municipalities.

Implementing organisations

Public implementation organisations and joint arrangements with a high volume of public contact. A customer contact system brings the channels together, supports the front line with a knowledge base and ensures a traceable handover to the teams that process a request or report further.

Public space reports

Residents report a blocked drain, broken street lighting or litter by phone, at the front desk or on the web. The customer contact system registers the report, answers common questions immediately and passes the report on via the case management system to the right department for handling.

Alongside a citizen portal

The customer contact system is the staffed side of your service delivery, alongside digital self-service. Enquiries that get stuck in a citizen portal still reach you in person via the KCC, with the same registration and the same view of the customer.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

We build a customer contact system with a modern web stack and open government standards. We set up the integrations with the case management system and the basic registers through the government APIs intended for this purpose, so your own team can manage and further develop the system. The relevant integrations for this process: ZGW API (case management system), DigiD and MijnOverheid.

If you want an incoming call on your Tritel switchboard to open the customer record straight away, read more about our Tritel integration.

React / TypeScript front-end Node.js / Python / .NET back-end REST / JSON APIs ZGW APIs (Zaakgericht Werken, case-oriented working) Digikoppeling DigiD authentication MijnOverheid Knowledge base & search index Telephony & web form integration OAuth 2.0 / OIDC PostgreSQL Role-based access control (RBAC) Audit logging WCAG 2.1 AA accessibility Monitoring & alerting CI/CD & automated tests

Why choose Appfront for your customer contact system?

Appfront builds custom software for organisations in the Netherlands, with attention to the standards and requirements that apply in the public sector. We always begin with a thorough analysis of your customer contact centre (KCC) processes and existing systems. A customer contact system must not only be technically sound, but also add practical value for the frontline staff who use it.

On every project we write clear documentation and make sure your own team, or a future supplier, can understand and maintain the software. No black box, but transparent code and clear agreements on monitoring, maintenance and further development.

You work with a dedicated point of contact who understands both the technical and the functional side. That keeps communication lines short, prevents miscommunication and speeds up decisions when choices have to be made during the build.

Also take a look at our broader services around custom software, a municipal website and AI for municipalities and government.

  • A custom customer contact system built around your KCC processes
  • Channel-independent registration and first-line answers
  • Integrations via the ZGW APIs, DigiD and MijnOverheid
  • Developed in line with GDPR and the BIO
  • Digital accessibility compliant with WCAG 2.1 AA
  • Audit logging and role-based access
  • Clear documentation that your team can read and maintain
  • A single point of contact, no passing you between account managers
  • Ongoing maintenance and proactive further development
  • An approach tailored to your existing IT landscape

Security, privacy and accessibility

A customer contact system processes the personal data of residents and businesses. That is why Appfront builds in line with the GDPR and the Baseline Informatiebeveiliging Overheid (BIO, the Dutch government information security baseline). That means data minimisation, role-based access following the principle of least privilege, encryption in transit and at rest, and extensive logging, so it is traceable who has viewed which data.

We document the data processing so that your record of processing activities is complete and you can demonstrably comply with the GDPR. Where the system touches digital services for residents, we develop in line with WCAG 2.1 AA and the statutory digital accessibility requirements for government.

More about our approach to security: information security policy and CVD policy.

  • GDPR-compliant data processing and data minimisation
  • Developed in line with the BIO
  • Encryption in transit (TLS 1.2+) and at rest
  • Role-based access and least privilege
  • Audit logging with traceable access records
  • Monitoring and alerting for anomalies
  • WCAG 2.1 AA for digital accessibility
  • Documentation for your record of processing activities

Frequently asked questions about customer contact systems

Answers to the questions we are asked most often about a custom customer contact system.

A customer contact system (KCS) is the software a municipal customer contact centre (KCC) uses to register and handle incoming questions from residents and businesses. All channels (telephone, front desk, web, email and chat) come together in one system, so that for every contact an employee can see what has been asked before and what the status is. The KCS includes a knowledge base for first-line answers, handles referral and escalation to specialist departments, integrates with the case management system and provides management information on customer contact.

An off-the-shelf package often suits a standard KCC process. Custom makes sense when your way of working, channel mix or integrations differ from what a package offers: your own knowledge base structure, specific escalation routes to specialist departments, or integration with a case management system and sources that are not supported as standard. A custom KCS is built around your processes rather than the other way round, and remains extensible without depending on a supplier's roadmap. In an intake conversation we can work out together whether custom is the right choice in your situation.

Yes. A customer contact system (KCS) should integrate with the case management system, so that a contact centre (KCC) agent can look up the status of an ongoing case and register a new report or question as a case. Appfront preferably builds this integration via the ZGW APIs (Zaakgericht Werken, case-oriented working), the national standard for case-oriented working. The system can also integrate with identification via DigiD and with any other sources needed for a complete picture of the customer.

A customer contact system brings together the channels that residents and businesses use to get in touch: telephone, the front desk, the web form or self-service on the website, email and chat. The idea behind channel-independent working is that a question is registered and handled in one place, regardless of the channel it comes in through. The agent sees the full contact history and doesn't need to ask the resident to explain everything again. We align exactly which channels we connect with your existing telephony and web environment.

The knowledge base contains up-to-date, approved answers to frequently asked questions, so that a contact centre agent can answer a large share of questions straight away at first line without transferring the caller. Subject-matter departments manage the content, so the information stays in line with current policy and regulations. The KCS shows relevant knowledge base articles for the topic of the contact and tracks which questions come up often, so the knowledge base can be expanded in a targeted way.

Yes. A KCS processes personal data of residents and businesses, so Appfront builds in line with the GDPR and the Baseline Informatiebeveiliging Overheid (BIO, the Dutch government information security baseline). Among other things, that means data minimisation, role-based access and least privilege, encryption in transit and at rest, and extensive logging so it is traceable who viewed which data. We document the data processing for your record of processing activities. Where the system touches on digital accessibility, we develop in accordance with WCAG 2.1 AA and the statutory digital accessibility requirements for government.

A KCS records how many contacts come in, through which channels, about which topics, and how many of them are resolved at first line. This produces management information that lets a contact centre plan staffing, see which topics recur often and assess where the knowledge base or the service can be improved. The reports are set up around the indicators that matter to your organisation.

Yes. Appfront regularly takes over the management of existing software, even when it was originally built by another party. We carry out a review of the architecture, the integrations with the case management system and sources, the knowledge base and the security, document the current setup and draw up improvement proposals. From that point on, we can extend the customer contact system, add integrations and keep the system under management, with clear agreements on monitoring and further development.

Ready to build your customer contact system?

Tell us which channels your contact centre serves, which integrations with the case management system and sources are needed, and what your knowledge base and escalation routes look like. We're happy to help think through the setup of your customer contact system. Schedule a no-obligation conversation via our contact page to get a clear picture of the possibilities.

Edit content