What gets done by hand every day goes out on its own, on time.

Repeated tasks are the ones that get forgotten.

A follow-up, a confirmation email, a short report: each takes two minutes, and nobody treats it as work. That's exactly why they get skipped one day in three, and why the alert arrives once the problem is already there.

• Follow-ups sent whenever someone remembers
• Confirmation emails written one at a time
• Documents received by email, then re-keyed
• The alert that arrives once the problem is already there

An event, a rule, and the rest goes out on its own.

Every automation starts from a dated event in the app: a quote sent, an order delivered, a threshold crossed, a date reached. It triggers what follows in the name of the person handling the job, and the send is filed in that job's history.

So the client gets a message from a person, not from a no-reply address — and replies in the usual thread.

• Quote and payment follow-ups
• Order and transport tracking
• Confirmation, reminder and delay emails
• Reports and weekly summaries
• Alerts when a threshold is crossed

What shouldn't be automated isn't.

Chasing a major client happens on the phone, and no setting will change that. So you set the amount above which the automation hands over, and anything past that threshold surfaces in the daily list instead of going out by itself.

Each automation is switched on and off separately, and every send is traced: you know what went out, when, to whom, and under which rule.

• An amount above which the automation hands over
• Each automation switched on and off separately
• Every send traced in the job's history
• A follow-up stops the moment the client replies