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.

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, running below — sample data, live to click

ALF/ Today

Tuesday · Reception answering

The company is running.

ALF Reception is answering calls and turning them into jobs. One decision is ready now. The rest remain ordered behind it.

Calls covered

Overflow · out of hours · second line

ALF Reception

CALL · HANDING OFF

72.0 SEC

No hot water or heating since this morning. The boiler pressure gauge is reading zero, and two young children are in the flat. Noah can take a callback at any time today.

ALF stopped once: creating the next business record needs your approval. Everything the caller said is already captured.

NEEDS YOU · 9

One interruption.

ALF handles the certain work. You handle the judgment.

ALF RECEPTION · NOW

Create Noah Williams’s job now?

Boiler pressure loss at 5 Furnace Row, ZZ99 3AA · Emergency.

Handled without you

Every action carries evidence

  • 30 days68 calls answered and structuredcaptured
  • Now12 jobs hold a completed outcomedurable
  • Open10 open jobs remain in the operating recordwatched

Raw calls stay for 90 days. Customer, job and evidence records remain.

This is the ALF OS client app drawn from sample records for Example Plumbing & Heating. The controls act on the sample data: creating a job opens the record built from what the call captured, dismissing takes the next interruption, and the rail switches views.

What we do

Diagnose it. Build it. Run it.

The expensive mistake is building the wrong thing well.

DiagnoseWe find where your business loses time and enquiries, then rank what is worth fixing first.
DesignWe build the smallest system that fixes it, and test it on your real calls before it goes live.
ManageWe run it afterwards — monitoring, updates and improvements based on what real use shows.

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.