Not the Technology
For many people, contacting the police is one of the few interactions they will ever have with policing.
They may be reporting a crime, seeking help for somebody vulnerable, providing information, asking what has happened to an existing case or dealing with an immediate threat to life.
What happens next matters.
How quickly the contact is answered, whether the circumstances are understood correctly, how risk and vulnerability are identified, whether information has to be repeated, and whether the right response follows can all shape both the operational outcome and the public’s confidence in policing.
That is why 999, 101 and digital public contact should not primarily be thought of as contact-centre technology.
They are part of an end-to-end policing service.
And when forces consider modernising that service, the starting point should not be the telephony platform, the digital channel or the latest automation capability.
It should be a much simpler question:
What experience and outcome are we trying to create for the person contacting policing – and for the people responsible for responding?
Public contact is an operational capability
It is easy to view public contact as the front door to policing.
In reality, it is much more than that.
The information captured during an initial interaction can influence:
- whether an incident is treated as an emergency;
- how risk and vulnerability are assessed;
- whether officers are deployed;
- the priority given to that deployment;
- what information is available to attending officers;
- whether safeguarding activity is initiated;
- how an investigation begins;
- what intelligence is created;
- whether another organisation is better placed to respond.
A seemingly simple phone call or online report can therefore become the first stage of a much larger operational workflow.
That changes how the capability should be designed.
Success cannot simply be measured by whether a call was answered or an online form was submitted.
The real questions are whether policing understood the need, identified the risk and connected that contact efficiently to the appropriate response.
Start by understanding why people contact policing
Before changing technology, it is worth understanding the demand the service is actually handling.
That sounds obvious, but public contact environments can absorb a remarkably diverse range of demand.
The Home Office recently reported that 101 receives around 20 million calls each year, with approximately one in five relating to matters more appropriately handled by organisations such as local authorities, NHS 111 or other services. [Source: GOV.UK]
That illustrates an important point.
Not every improvement to public contact requires policing to process the same demand more quickly.
Sometimes the better outcome is:
- helping someone reach the correct service earlier;
- making information easier to find without contacting the force;
- avoiding unnecessary repeat contact;
- offering a more appropriate digital route;
- identifying genuine risk faster;
- preventing lower-priority demand from obscuring urgent need.
The design problem is therefore broader than “how do we handle more calls?”
It is:
“How do we help people reach the right outcome with the least unnecessary effort, while ensuring policing identifies and prioritises the contacts that genuinely require its attention?”
That is a service-design question before it is a technology question.
Not every channel is suitable for every type of contact
Public expectations have changed.
People increasingly expect to be able to interact with organisations digitally, at a time and through a channel that suits them.
There is clear value in providing alternatives to the telephone for appropriate types of police contact.
But channel choice should not become an objective in itself.
A digital interaction may work extremely well for:
- reporting certain offences;
- providing additional information;
- submitting evidence;
- checking progress;
- making routine enquiries.
It may be entirely unsuitable where somebody is frightened, vulnerable, unable to express the situation clearly or facing an immediate threat.
The challenge is therefore not to move as much demand as possible from one channel to another.
It is to match the nature and urgency of the contact to the right interaction.
The national Digital Public Contact programme has similarly emphasised reducing citizen effort, using channels consistently and ensuring real and immediate risks to life are identified and prioritised. [Source: London City Hall]
That feels like the right design principle.
Channel strategy should follow the public need, not the other way around.
The first interaction can shape everything that follows
A contact handler may have only a short period of time to understand what has happened.
They may need to establish:
- who is involved;
- where the incident is taking place;
- whether anybody is in immediate danger;
- whether children or vulnerable adults are involved;
- whether weapons are present;
- whether there is relevant previous history;
- whether another incident is connected;
- what response is required.
Good technology can clearly help.
It can present relevant information, reduce repetitive data entry, support structured questioning and make it easier to access information held elsewhere.
But the objective should remain better assessment, not greater technology utilisation.
This distinction matters.
A technically successful implementation can still create a poor operational result if it makes it harder for the person handling the contact to understand what is happening.
The user experience of the police employee matters just as much as the public-facing interface.
Public contact cannot end at the contact platform
One of the recurring risks in technology transformation is optimising one part of a service without considering what happens immediately afterwards.
Police contact is a good example.
The initial interaction may need to connect with:
- command and control;
- records management;
- intelligence;
- incident history;
- safeguarding information;
- mapping and location services;
- digital evidence;
- case-management processes;
- partner organisations.
If those connections are weak, the organisation often compensates through people.
- Information gets re-keyed.
- Users search several systems.
- Call handlers ask questions whose answers may already exist elsewhere.
- Officers receive incomplete context.
- Members of the public repeat information they have already provided.
- Separate records of the same event begin to diverge.
None of those things necessarily indicates that an individual platform is poor.
They often indicate that the service has not been designed end to end.
Integration therefore needs to be understood in operational terms.
The important question is not simply whether two systems have an API.
It is whether the information required at the next stage of the policing response arrives accurately, securely and at the right time.
Reducing repeat contact is an outcome in its own right
A particularly useful way to assess the effectiveness of public contact is to consider why people come back.
Some repeat contact will always be legitimate.
Circumstances change. New evidence emerges. Risk increases. People need further help.
But other repeat demand can result from uncertainty.
- A victim may not know what has happened since their original report.
- Someone may not understand what will happen next.
- An online report may disappear from view with no obvious indication of progress.
- A caller may be transferred between teams without a clear resolution.
This matters for two reasons.
First, it affects the person’s experience and confidence in the service.
Second, it creates additional demand for the force.
Improving communication and visibility can therefore benefit both the public and policing.
Sometimes the best way to reduce contact demand is not to make the initial interaction shorter.
It is to make the overall journey clearer.
The workforce has to be part of the design
Public contact is demanding work.
The people operating these services deal with urgency, ambiguity, distress, vulnerability and occasionally significant risk.
Any transformation therefore needs to consider the workforce alongside the process and technology.
That includes:
- the information staff need to see;
- how quickly they can find it;
- how many systems they need to navigate;
- whether the workflow supports rather than interrupts conversation;
- how supervisors identify emerging risk;
- training and competency;
- workload and demand peaks;
- escalation;
- resilience when systems fail.
A new platform may offer substantially greater functionality, but if it adds cognitive load at the point where somebody is trying to assess a difficult situation, the operational outcome can get worse rather than better.
The best technology in these environments should often feel almost invisible.
It should remove friction and bring useful information closer to the user.
Automation should remove friction, not judgement
There are increasingly capable tools available to support activities such as:
- routing;
- transcription;
- summarisation;
- searching;
- data capture;
- identifying missing information;
- presenting relevant records;
- reducing duplicate entry.
Some of those capabilities can potentially return meaningful time to contact handlers and improve consistency.
But the useful question is not:
“Where can we deploy AI?”
It is:
“Where are people spending time on repetitive activity that technology can safely remove or simplify?”
That distinction protects the operational purpose.
Routing a routine enquiry to the appropriate organisation is very different from deciding whether somebody is vulnerable.
Producing a draft summary of a conversation is very different from determining the appropriate policing response.
The more consequential the judgement, the more important it is that human accountability remains explicit.
Technology should help people reach good decisions.
It should not make responsibility for those decisions less clear.
Resilience is part of the service
For critical police contact, service availability is itself an operational outcome.
A public contact strategy therefore needs to consider what happens when:
- a primary platform becomes unavailable;
- connectivity is disrupted;
- a building cannot be used;
- demand suddenly increases;
- a third-party service fails;
- staff need to work from alternative locations.
Resilience should not be added as a technical design requirement late in procurement.
It needs to follow from understanding which services policing must continue to provide and under what circumstances.
The question is not simply “is the platform highly available?”
It is:
“Can the force continue to understand and respond to public need when something goes wrong?”
Those are related questions, but they are not the same.
Five principles for getting police contact right
For forces considering significant change across 999, 101 or digital public contact, five principles provide a useful starting point.
1. Begin with public and operational outcomes
Define what better looks like before selecting technology.
That might mean faster identification of risk, reduced citizen effort, fewer unnecessary contacts, better information for responders or improved victim communication.
2. Understand demand before designing channels
Know why people are contacting policing, which demand genuinely requires a police response and which interactions are most appropriate for each channel.
3. Design the complete journey
Follow contact beyond the first interaction into assessment, deployment, safeguarding, investigation and eventual outcome.
The service boundary should not be dictated by the boundary of the contact platform.
4. Design around the people delivering the service
Reduce system switching, repetitive entry and unnecessary cognitive burden.
Give staff access to the information that helps them exercise professional judgement.
5. Measure the outcome, not the technology
Success measures might include:
- faster identification of vulnerability;
- fewer avoidable repeat contacts;
- reduced transfer between teams;
- improved quality of information passed to responders;
- time returned to contact handlers;
- greater service resilience;
- improved public experience.
The number of licences deployed or automated interactions completed tells us very little about whether policing has improved.
Start with the service
Policing will continue to adopt new ways for the public to make contact.
The technology supporting those interactions will also continue to evolve.
That is necessary.
But modernisation should not become synonymous with platform replacement, digitisation or automation.
The objective is a public contact service that can understand need quickly, recognise risk, make effective decisions and connect people to the right response with as little unnecessary friction as possible.
Technology matters because it can help deliver that.
But the technology is not the outcome.
Getting the service right is.
Clarity starts with a conversation
At dstilld technologies, we work with police forces, technology partners and specialist vendors to connect operational requirements, architecture, commercial strategy and delivery assurance.
If you are facing a similar challenge, feel free to get in touch.
We are always happy to have an initial conversation, share our perspective and help you think through the problem. There is no obligation to turn that conversation into a paid engagement.
Sometimes a short discussion is all that is needed to identify the next sensible step.