Business Process Automation starts with the process

A quotation is taking too long to reach a prospective customer. The business is busy, the team is frustrated, and someone suggests an automated follow-up system.

That might help. But what if the quotation has not been prepared because the original enquiry is missing essential information? Or it is waiting for a decision only the owner can make? Or someone has already sent it, but the status was never updated?

The visible symptom is the same: slow progress. The underlying problem is different in each case.

Before choosing an AI tool, CRM or automation platform, it helps to establish what is actually holding the work up.

The same questions apply to customer onboarding, job scheduling, recurring service reminders, bookkeeping and follow-up sequences. Enquiry handling is one place to begin, but the principle extends to the work that happens throughout the customer relationship and behind the scenes.

Automating an inefficient process does not necessarily make it a better process. Sometimes it simply allows the inefficiency to happen faster.

Start with the work you are trying to improve

Business process automation uses technology to carry out defined parts of a business process, such as routing an enquiry, creating a task or sending a reminder when specified conditions are met.

The practical question is which part deserves that treatment.

At New Beginnings Web and Marketing, our work includes connecting website enquiries with CRM workflows. My view is that the connection is only part of the job. A record arriving in a CRM still needs a purpose: someone must know what happens next, what information is required and when the enquiry needs personal attention.

That distinction matters because it is possible for the technology to work while the business process remains frustrating.

A website form can submit successfully. A CRM record can be created correctly. An email notification can arrive immediately. The prospective customer can still wait because nobody clearly owns the response.

Before adding another action, establish the outcome you want. “Automate our enquiries” is broad. “Make sure every suitable enquiry reaches the right person with enough information for a useful first response” gives you something concrete to assess.

Follow one piece of work from beginning to end

Choose a manageable process, such as an enquiry becoming a quotation. Walk through recent examples with the people who actually handle them, including an awkward case that needed extra attention.

Record what happened, rather than what the procedure says should happen. A simple table is enough:

Separate time spent doing the work from time spent waiting for something.

Preparing a quotation might be straightforward once the scope is clear. If it waits for clarification or approval, speeding up document generation may make little difference to the customer’s total wait.

ASQ’s guidance on process mapping supports examining the actual sequence of work with the people involved. You do not need specialist diagramming software to begin. You need an accurate account of where work moves, pauses or comes back for correction.

The purpose is to understand the conditions people are working within. If someone keeps a separate spreadsheet, ask what it gives them that the main system does not.

Five questions to ask before choosing a solution

The following is a practical way to organise that investigation. The categories overlap, and one workflow may contain several problems. Use them to identify what needs attention first.

1. Is the process itself unclear or unnecessarily complicated?

A process challenge exists when the way work is organised creates the difficulty.

Perhaps every quotation needs approval from the owner, although many use standard scope and pricing. Perhaps two people check the same information. Perhaps enquiries move between colleagues without a clear next owner.

Ask: If we did this manually with complete information and suitable software, would the sequence still cause delays?

If it would, review the sequence, responsibilities or decision rules.

You may need to remove a duplicate check, define who can approve routine work or agree what counts as a complete hand-off. Automating reminders to an overloaded approver could produce more notifications without removing the queue.

Keep controls that serve a real purpose. The aim is to simplify responsibly, rather than remove every approval because it takes time.

2. Does the software support the job people need to do?

Sometimes the process is reasonable, but the tool makes it difficult to perform.

A scheduling system might not represent the combination of staff, equipment and appointment length the business needs. A CRM configuration might make the next action difficult to see. A quotation system might require a separate document because it cannot represent the required scope clearly.

Ask: Can the existing system do this properly, with an appropriate configuration and people who know how to use it?

Check settings, permissions, available functionality and training before assuming a replacement is necessary. A workaround can indicate a missing capability, but it can also indicate that the capability has not been configured or understood.

A business may already have software that can handle the task, while staff continue to follow procedures written before those features became available. Review how people use the system alongside the standard operating procedures that guide them.

For a small family-run business, enabling a supported bank feed in its bookkeeping system could remove the need to import bank transactions manually. Xero, for example, describes bank feeds that automatically import transactions ready for reconciliation. Someone still needs to check and reconcile those transactions. The immediate improvement comes from using an available connection. About bank feeds in Xero.

The same principle applies to an existing CRM reminder feature or a scheduling system’s recurring appointments. Investigate the capabilities relevant to the problem and update the working procedure so the team can use them consistently. You may be able to achieve the desired improvement with a modest configuration change and training. A large custom workflow is only worth considering when the requirement justifies it.

Where a genuine limitation remains, changing or extending the tool may be justified. Adding automations around an unsuitable system can leave the team maintaining an increasingly complicated set of workarounds.

3. Do suitable systems need a better connection?

An integration challenge occurs when the systems can each do their job, but information does not move between them appropriately.

For example, the enquiry is captured correctly on the website, yet someone has to retype it into the CRM. Or an accepted quotation must be copied into an accounting system before the next step can begin.

Ask: Is the repeated work mainly moving information that already exists somewhere else?

If so, investigate the connection. Establish which information should move, when it should move and which system holds the authoritative version of each item.

An accepted quotation, for instance, may be ready to create a draft accounting record. It may still need a person to confirm billing details or resolve a scope change before anything is issued.

Integration is often implemented through automation. The useful distinction is that the immediate need is a reliable transfer between suitable systems. It does not automatically require replacing either system or introducing AI.

Compatibility, permissions and supported interfaces still need checking for the actual products involved.

Platforms such as Zoho Flow, Zapier and Latenode can help connect applications and automate workflows. They become relevant once you can describe the information that needs to move and the action it should trigger. First establish whether the existing systems already provide a suitable connection, then assess any additional platform against the remaining requirement.

4. Is the information incomplete, duplicated or unreliable?

A data problem can follow work from one system to the next.

A service request lacks a location. Two customer records contain different contact details. A quotation is marked as awaiting a response even though the customer has accepted it by email.

Ask: Would the next person or system know what to do if this information arrived instantly?

If the answer is no, faster transfer will not resolve the missing or conflicting detail.

The UK Government Data Quality Framework distinguishes between aspects of data quality, including completeness, accuracy and uniqueness. In practical terms, a filled-in field can still be wrong, and two individually plausible records can still represent the same customer.

Decide what information is necessary at each stage, where corrections belong and how existing records are identified before new ones are created. Avoid making every conceivable field compulsory on an enquiry form; collect what is needed to take the next useful step.

5. Is there a clear and worthwhile automation opportunity?

Once you understand the work, look for steps where the intended action can be described and checked.

Examples might include assigning an enquiry using an agreed service-area rule, creating a follow-up task after a quotation is sent, or passing confirmed details into another system.

Ask: Can we explain what starts this action, what it needs, what it should produce and what happens when it cannot proceed?

A useful candidate usually has reasonably consistent inputs, a clear purpose and enough value to justify setup and ongoing attention. Frequency matters, but an infrequent task can also be worth automating if a missed deadline or error has a significant consequence.

Microsoft’s automation design guidance favours procedural tasks with a worthwhile return and recognises that a workflow can retain human decisions.

You do not need to automate the entire process to improve one part of it.

The same quotation delay can need different fixes

Consider an illustrative service business whose quotations regularly take longer than intended. This is a diagnostic example, and not a reported client result.

Several of these can exist together. The point is to investigate before purchasing a solution for the symptom.

For follow-up automation, the rule needs more detail than “send an email after three days”. Which quotation version does it refer to? Has the customer replied through another channel? Has the work been declined? Who can pause the sequence?

Those questions determine whether the follow-up helps the conversation or creates an awkward message at the wrong time.

Follow-up cadences need a clear purpose and stopping rules

A follow-up cadence is a planned sequence of messages and activities over time. It might support a quotation, guide a new customer through onboarding or prompt a conversation before a service renewal.

An illustrative onboarding cadence could begin when a customer accepts a proposal. It could send a welcome message, create a task to collect outstanding documents and remind the account owner to arrange a handover once those documents have arrived.

Before building it, decide what qualifies someone to enter the sequence, which steps depend on earlier actions and when personal contact would help. Define what should pause or end the sequence, including a completed action, a changed requirement or a request to stop receiving messages.

A fixed schedule can become frustrating if it keeps asking for documents the customer has already supplied. The process needs a way to recognise progress and keep the relevant record up to date.

Your CRM may already support this. Zoho CRM’s Cadences, for example, provides follow-up sequences involving emails, tasks and calls, with later steps configured around earlier outcomes. Check the available features and settings in the account you use. Zoho CRM Cadences documentation.

Other workflows need their own conditions. A service reminder depends on a reliable due date and completion status. A job-scheduling workflow needs confirmed availability and a way to handle changes. An accounting hand-off needs agreed details and a clear approval point. In each case, identify the information and decisions that make the next action appropriate.

Where AI can help and where a person should decide

AI-assisted workflow automation deserves the same scrutiny.

Examples of AI-assisted workflow automation include preparing a summary of a long enquiry for a staff member to check, drafting a clarification message from information already supplied, or turning meeting notes into a proposed list of follow-up tasks for approval.

Before using them, decide how the output will be checked. If an enquiry leaves out a service location, the workflow should request it or flag the gap. It should not treat a plausible guess as a confirmed detail.

Where the rule is already exact, a conventional automation may be sufficient. Creating a task after a recorded event does not inherently need AI interpretation.

Keep a person involved where the work requires judgement about scope, unusual pricing, conflicting instructions, complaints or a commitment to the customer. Automation can prepare information and prompt the decision without making that decision itself.

Human involvement should be visible in the workflow: who reviews the item, what they must check and how the next step is released.

Test one improvement against a business outcome

Start with a bounded change you can observe. You do not need to finish redesigning the whole business before testing a sensible improvement.

Write a short brief:

• Problem: What is happening, and what evidence shows it?
• Outcome: What should improve for the customer or team?
• Scope: Which step will change, and who owns it?
• Rules and information: What must be true before it runs?
• Exceptions: What needs a person, and how will they see it?
• Failure response: Who is alerted, and how can the work continue?
• Review: What will you compare before deciding whether to expand it?

For enquiries, you might monitor time to a useful response. For quotations, compare total turnaround, correction work and staff effort. Track exceptions too. A faster workflow that creates more corrections has moved the burden elsewhere.

Include configuration, subscription, monitoring and maintenance costs in the decision. Time released from administration can be valuable capacity, but it is not automatically a cash saving or additional revenue.

Test awkward cases as well as the normal route: an existing customer submitting again, a quotation changing after follow-up is scheduled, or a connected system being unavailable. Microsoft’s error-handling guidance illustrates why failure paths, records of errors and notifications need deliberate design.

Someone should own the workflow after it goes live and know how to pause it when the business changes.

A useful place to begin

Choose one recurring frustration and follow the work closely enough to explain it.

Where does it wait? What gets copied? Which decision is unclear? What information is missing? What does the customer experience while all of that happens?

You may find a useful automation opportunity. You may find that a clearer responsibility, a simpler approval or a change to the existing software solves the immediate problem.

Either finding gives you a better basis for spending money.

If you want us to help assess a workflow, start with one concrete example of where work gets stuck. That gives us a useful starting point for deciding what needs to change and which technology, if any, should support it. You can contact us here