Automations
If-then rules that take work off your hands, approvals that stay strict
Some steps you do every time again, and others you would rather not let pass without a second pair of eyes. A discount above a limit, an expensive purchase, a quote: someone should look at that before it goes ahead.
With simple if-then rules you let something start automatically on an event, for example on a completed job. If such an automation fails, that never touches the underlying action: the job stays completed, only the follow-up step did not go through.
Approvals work the other way round, strict: on discount, quote, purchase and work order you set a limit above which someone has to approve first, with four eyes. Without that approval it does not go through. One system is easy-going, the other is a lock.
If-then on events
Let a follow-up step start automatically on a completed job or another moment.
A failure does not touch the job
If an automation goes wrong, the underlying action simply stays in place.
Four eyes on approval
Above a limit someone else has to approve first before it goes ahead.
Limits you set yourself
Decide per discount, quote, purchase or work order from what amount approval is needed.
Strict where it must be
Without the required approval an action does not go through, no exception.
Easy-going where it can be
Routine steps run on their own, so that your attention goes to the real work.
Which work you hand over to an if-then rule
Much administration is a fixed reaction to a fixed event. If a work order is signed, create a draft invoice. If a quote is accepted, plan the job and send a confirmation. If an invoice is fourteen days overdue, send a reminder. Today you do that work yourself, every single time.
In TelMaar you record such rules once: an event, a condition and an action. The rule then runs by itself and a log shows what it did. If something goes wrong, that is in the log too, with the reason.
Why approvals need to stay strict
Automating must never mean that a large discount, an expensive purchase order or a quote above a certain amount leaves unseen. That is why you can set a threshold per document type: above it a second pair of eyes is required before it may proceed.
The approver gets a notification, sees the document with the reason it was held and approves or rejects, also from their phone. Who approved what and when stays recorded. So you remove routine work without losing control over the money.
Frequently asked questions about this feature
What happens if an automation fails?
Then it does not touch the underlying action. The job stays completed or the invoice stays sent; only the automatic follow-up step did not go through.
What can I set an approval on?
On discount, quote, purchase and work order. Above the limit you set yourself, someone else has to approve first, with four eyes.
Can an action go through without approval anyway?
No. An approval is strict: without the required approval the action does not go through. That is precisely the point of it.
Ready to see how it works for yourself?
Start for free and discover in a few minutes why TelMaar fits your business.
Start for free