Solutions
Cut support tickets by doing the task, not explaining it
The largest category in most support queues is not defects. It is people who cannot find how to do something they are entitled to do. Deflection with better articles helps a little. Doing the task helps a lot.
Deflection has a ceiling
Knowledge bases and answer bots take a "how do I" ticket and return instructions. That is genuinely useful, and it is also the reason deflection rates plateau: the user still has to perform the steps, and a proportion of them fail partway through and open the ticket anyway.
The instructions are also the part most likely to be wrong. Documentation ages the moment the interface changes, so a confident answer describing a button that moved two releases ago produces a more frustrated ticket than no answer at all.
Completing the task removes the ticket
When a user asks how to update every contract expiring this month and notify the account managers, Merlean can do it, in their session, with their permissions, and tell them what it changed. There is no set of steps to follow and no place to get stuck.
Because the underlying model is derived from the application's current source, the action taken reflects how the software works now. A stale answer is not possible in the way it is with written documentation.
- The "how do I" category shrinks, because the question is answered by the result.
- Escalations from partially completed work drop, because the work is completed or reported as failed, not abandoned halfway.
- Agents keep the tickets worth their attention: genuine defects, edge cases and account issues.
What to measure
Track the share of tickets tagged as usage questions before and after, not overall volume, which moves for unrelated reasons. Track time to completion for the workflows you expose first. And track the workflows users ask for that Merlean could not complete, because that list is the most honest roadmap you will get.
Frequently asked questions
Does this replace our help centre?
No. Documentation still serves people who want to understand the system rather than complete one task. Merlean removes the subset of traffic that only ever wanted the task done.
What about tickets that are actual bugs?
Those still reach your team, which is the point. Removing usage questions makes defect reports easier to see rather than burying them.
Can it escalate to a human?
Yes. When a request falls outside what the application can do, or a step fails, the user is told plainly rather than left with a plausible-sounding non-answer.
See it against your own application
Merlean reads your repository and shows you what it understood before anything is exposed to a user. The fastest way to judge the fit is to point it at a real codebase.
Related
Add an AI assistant to your web app that actually does the work
Embed an AI assistant in your SaaS product that completes tasks instead of explaining them. One script tag, no per-feature integration code, works on any web stack.
Onboard users without teaching them your interface
New users are productive on day one when they describe outcomes instead of learning navigation. Cut training time and time to first value.
Merlean vs chatbots
Support chatbots and RAG assistants retrieve answers. Merlean executes actions inside your product. Where each belongs, and why deflection rates plateau.