How We Designed Our Intent Engine to Avoid Over-Personalisation
Personal relevance is helpful only while the customer still feels in control of what the website thinks and what happens next.
Quick answer
We designed our Intent Engine so browsing context can support a likely route but cannot dominate customer input. The system prefers declared page meaning, recent coherent activity and explicit choices, while corrections override assumptions, sensitive journeys are protected, and commercial actions remain customer-controlled.
Why this matters for businesses
Most websites still measure success mainly through traffic, clicks and form submissions. Those numbers are useful, but they do not explain whether the customer understood the problem, followed a sensible path or reached the right service. Intent-aware design adds meaning to the journey while keeping important decisions under customer and human control.
What over-personalisation feels like
A website becomes uncomfortable when it acts as though it knows more than the customer intentionally shared: carrying old topics too aggressively, making confident claims from weak signals, or changing offers based on opaque profiling.
That can damage trust even when the underlying technology is technically impressive.
Bounded evidence instead of unlimited behavioural memory
Our design treats browsing as a small supporting input rather than the main source of truth. Recent context matters more than stale activity, repeated passive reading has diminishing returns and unrelated page movement lowers coherence.
The website does not need a permanent behavioural profile to remember that the customer has recently been exploring a particular help area.
Customer corrections take priority
Whenever the customer changes direction, the explicit statement should override inferred context. That is why “not quite”, “something different” and natural-language correction paths are important parts of the interface.
A website that cannot be corrected is not truly customer-controlled.
Sensitive topics need a different policy
Scam recovery, cybersecurity incidents and supported-help journeys should not automatically become commercial readiness signals. The same semantic layer that improves routing can also mark those topics as protected.
This lets the website be smarter without treating vulnerable or safety-related reading as an opportunity to sell.
Keep commitments behind explicit action
The system can suggest a likely service, but it should not submit an enquiry, accept a price, schedule paid work or make a binding decision because of browsing context. QuoteMe and other transactional workflows still require explicit customer action.
That separation is one of the most important controls in an AI-assisted customer journey.
The business lesson: restraint is a feature
The best personalisation often feels like less friction rather than more visible AI. Remember the confirmed topic, ask fewer repetitive questions and show a relevant next step but keep the customer able to change direction.
For many businesses, that is enough intelligence to create a noticeably better journey without building an invasive data system.
How this fits with the Your IT & Tech Mates Intent Engine
Our current design separates four jobs. Content declares what a page is for. The journey layer records recent interaction and checks whether it is coherent. The Intent Engine interprets what the customer appears to need, with explicit customer wording taking priority. Commercial readiness is assessed separately from intent confidence. Keeping those responsibilities separate makes the system easier to explain, test and improve.
We also deliberately avoid the rule “more browsing equals more confidence”. Passive reading stays weak evidence, repeated behaviour has diminishing returns, and sensitive support or security topics are not treated as ordinary sales signals.
Practical takeaway for another business
Start with one high-friction customer journey. Write down the real questions customers ask, the pages that help answer them, the small number of decisions that change the next step, and the service or human handoff that should follow. Make the content useful first. Then add automation only where it removes repetition or confusion.
The result should feel less like “AI watching the customer” and more like a well-trained staff member who remembers the relevant part of the conversation, asks a sensible next question and accepts correction without argument.
Frequently asked questions
What is over-personalisation?
It is when a website relies too heavily on inferred or historical behaviour and starts making decisions that feel intrusive or unjustified.
Does your Intent Engine use browsing context?
Yes, as bounded supporting evidence. Explicit customer wording and corrections remain stronger.
Do you need a permanent customer profile?
No. Many useful journey improvements can work with session-level or short-lived context.
How are sensitive topics handled?
They can guide safer routing but are excluded from ordinary commercial readiness scoring.
Can the website submit something automatically?
Not from browsing context. Important requests and commitments still require explicit customer action.
What is the simplest privacy-first improvement?
Reuse confirmed context so customers repeat themselves less, while giving them a clear way to correct or clear that context.
Continue the Intent-Aware Website series
Could this approach help your business website?
If customers regularly choose the wrong form, repeat themselves, struggle to find the right service or arrive with incomplete context, an intent-aware journey may help. The first step is usually a workflow and content review, not replacing your whole website.