ALF Automation In development

The admin between the enquiry and the job.

The job is captured. Then someone retypes it, remembers to follow up, and updates the record. That gap is where jobs go quiet.

What it looks like

A job that moves without anyone pushing it.

What you get is not a dashboard. It is the follow-up that would have been forgotten, having happened.

Takes in

  • A job captured by Reception
  • An enquiry from the website
  • A step that did not happen

ALF Automation

  • Runs the step you would otherwise remember to do
  • Stops and asks when the next step is a judgement call
  • Records what it did, in order

Hands on

  • Your CRMthe job written once, not typed three times
  • The customerthe follow-up that would have been forgotten
  • Youwhat ran, what waited, and why

It does not message a customer on your behalf without a rule you approved first.

How the module plugs in. A schematic, not a screen.

What it does

The step you would otherwise remember to do.

Designed behaviour — this module is in development, and these are the responsibilities it is being built to hold.

WritesThe job into your customer record once, from what Reception captured, instead of it being typed again.
Follows upAgainst the callback window the caller actually gave, rather than whenever someone next thinks of it.
RecordsWhat ran, what waited and why — in order, so a job that stalled is visible rather than forgotten.

Where it stops

What it will not do.

It does not message a customer on your behalf without a rule you approved first, and it stops and asks whenever the next step is a judgement call rather than a step.

Early access

Not finished, and not for sale yet.

It is being built now. Early access means showing us the handful of steps you repeat every week, so the module is shaped around work you actually do.

Ask about early access →

Questions

About ALF Automation.

When will this be available?

There is no date yet, and we would rather say that than pick one. It is in development; when it is live this page will say so, and the pricing page will move it out of "in development" on the same day. Nothing about it is for sale in the meantime.

Will it message my customers on its own?

Not without a rule you approved first, and not when the next step is a judgement call rather than a step. It stops and asks. A follow-up that goes out on its own judgment is exactly what we are not building.

What does early access involve?

Showing us the handful of steps you repeat every week, so the module is shaped around work you actually do. It is a conversation, not a commitment.

Can I pay for it now to reserve it?

No. It contains work that is not finished, so there is nothing to sell you yet. ALF Reception is available today and everything in it is working — if the problem you have is the phone, that is the module that can help now.

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.

)}

Start here

Tell us what you would need from it.

Automation is what happens to a job after Reception takes it. It is the module that decides whether the system saves you time or just tells you about work faster.