Using Process Automation day to day

A good automation works in the background and is barely noticed. Even so, it's worth knowing how to confirm everything is running smoothly and what to do when an exception comes up.

Checking results

• In the first few weeks, spot-check some results: invoices issued, messages sent, rows logged.
• If the automation produces a daily report, use it as a quick check that everything ran.
• Keep a simple note of anything odd you notice and send it to us in one go.

Handling exceptions

When the automation meets a case it can't handle, it follows the rule set during configuration: usually it pauses that case and alerts you. Deal with it manually and, if it happens again, tell us so we can add a rule.

When a tool changes

Software vendors regularly change their APIs, alter plans or retire features. With a maintenance plan, we keep track of these notices and adapt the automation, in most cases before there's any impact. Major changes, such as switching invoicing software, are handled as a new quoted request.

What maintenance covers

The exact scope depends on the plan agreed in the proposal.

Bringing your team along

Tell your team what is now automatic, so nobody keeps doing the task by hand out of habit. Make it clear who receives alerts and who handles exceptions. When someone joins or leaves, check that access and alert recipients are still right and let us know if anything needs changing. If something stops working, see troubleshooting.