A customer asks for an update. You message the person handling the job. They check with a colleague, who searches their inbox for an approval. Eventually, someone replies.
The work itself may be progressing. Finding out where it stands has become another job.
That makes it a useful place to consider automation. If your team spends part of each day chasing information or reminding people what happens next, start by looking at those tasks.
Start with a task your team repeats
A good first candidate has a clear trigger and a predictable action.
When a customer submits an enquiry, someone acknowledges it and assigns it to a colleague. When a job needs approval, someone contacts the approver. When an invoice approaches its due date, someone checks whether a reminder is needed.
To choose where to start, ask your team which task they repeat most often and what happens when they forget it. A two-minute task deserves attention if someone does it twenty times a day. An occasional task may also be worth automating if missing it delays a whole job.
You need to understand the steps before you can decide which ones software should handle.
Enquiry handling is often a useful first project
Consider what happens after someone completes your website’s contact form.
The enquiry reaches a shared inbox. Whoever sees it first forwards it to the right person. That person replies when they have time. Unless someone keeps a separate record, it can be difficult to tell which enquiries still need attention.
An automated process can record the enquiry, send an acknowledgement and assign it according to agreed rules. It can also flag enquiries that have waited too long for a response.
Your team still needs to read the request and give a useful answer. The automation handles the routine steps around that conversation.
Before setting it up, decide who owns each type of enquiry and what happens when that person is away. Otherwise, the system will assign work to someone who cannot act on it.
Approval requests need a clear owner
Approvals often stall because nobody knows whose decision is missing.
A quote waits in an inbox. A document comes back with changes, but the requester doesn’t see the reply. Someone asks for approval again because they cannot find the first response.
Automation can send the request to the right person and record the decision against the job. If it remains unanswered, the system can send a reminder or notify an agreed substitute.
Make sure the approver receives enough information to decide. Sending an automatic request without the relevant document or context just creates another exchange of messages.
For sensitive or unusual decisions, keep a person responsible for the judgement. Automate how the request reaches them and how the outcome is recorded.
Status updates depend on accurate records
An automatic update is useful only if it reflects what has happened.
If a job reaches “Ready for delivery”, a system could notify the customer. But if the team uses that status before the final checks are complete, the message will create confusion.
Agree what each stage means and who updates it. Then choose the moments when a notification would help someone act or reduce the need for a phone call.
Be selective. A customer may want to know when their order is ready. They probably don’t need a message for every internal step. Your team can also become overloaded if every change generates an alert.
Avoid starting with the most complicated process
A process with frequent exceptions takes more work to automate well. If people disagree about how it should operate, settle those questions first.
For your first project, choose something you can describe clearly, test with real examples and pause if it causes problems.
Payment reminders, for instance, may sound straightforward. But the system must check for payments and disputes before sending a message. A reminder sent after a customer has paid creates avoidable work for accounts and can damage the relationship.
The details matter more than the apparent simplicity of the task.
Decide how you will judge the result
Before introducing automation, record what happens today. How long do enquiries wait for a response? How many approvals need chasing? How much time does someone spend preparing status updates?
Choose a measure that matches the problem you want to solve. Then run a small trial and check both the results and the messages people receive.
Ask the team whether they spend less time chasing and whether any new exceptions need manual attention. Adjust the process before expanding it.
That is a practical start on the Automate rung. Choose one repeated task, give it clear rules and check whether the change helps people complete their work.
Speak to CMSD about identifying a first automation project for your business.