ALF OS
Five modules. You probably need one.
Each module is bought on its own. The consultancy is how you find out which one you need, and who owns it once it is running.
The modules
Bought separately. Built to hand work to each other.
A job captured by Reception is the job Automation moves and the question Knowledge answers.
One of them, running
This is ALF Reception, answering.
The other four are bought the same way and land in the same records. Reception is the one that is live today, so it is the one there is something to look at — the call it took, the job it made, and the question the caller never answered.
ALF OS, recorded — sample data
What we do
Diagnose it. Build it. Run it.
The expensive mistake is building the wrong thing well.
Afterwards
Someone has to own it in six months.
That is what separates a managed system from an automation someone built and walked away from.
We will not build something we cannot run, and we will say when a process change, a form or a phone setting would do most of the work instead.
Questions
About running a system.
Which module should I start with?
Almost always the one covering where enquiries are being lost, which for most service businesses is the phone. If you are not sure where they are going, that is what the audit is for — and it can say the answer is a setting you already pay for.
Can a business start with only one system?
Yes, and most should. The smallest useful system that solves one expensive problem is a better first move than a programme. If a second one is worth building, that decision is easier once the first is running and you can see what it changed.
Do the modules need each other to work?
No. Each is bought and run on its own. They share the same customer and job records when more than one is running, which is what makes a follow-up know what the call was about, but none of them requires another to be useful.
Does every client receive every ALF module?
No. ALF OS is a family of modules, bought one at a time, not a bundle. We configure only the modules the agreed problem justifies, and the roadmap says which those are before anything is built. Most engagements involve one.
What is included in ongoing management?
Monitoring of the live system, routine changes as the business changes, prompt and knowledge updates, workflow maintenance, usage and reliability checks, agreed support, and improvements based on evidence from real use. The fee covers the infrastructure and usage that specific implementation needs, so it is quoted per system rather than as a standard rate.
Start here
Start with the problem, not the module.
Fifteen minutes is enough to tell whether there is something worth auditing — and to say so if there is not.