Unified Customer Engagement Hub Blog

Get insight, news, best practices, and other opinions on trending, industry leading, and other technology topics.

All Posts

Simplifying Robotic Process Automation


Are you confused by all the hype around Robotic Process Automation?  Do you have nightmares of Alexa taking over your workplace and having to slowly shut her down like Hal from 2001: A Space Odyssey?  Yet, according to Harvard Business Review ““A recent survey indicates that about half of the S&P 500 will be replaced over the next 10 years, a generational change that we call “disruptive change.””  Businesses are scrambling to re-invent themselves or face the threat of “uberization” of their respective industries.  As you seek out a way to adopt technologies that will enable you to transform your business like Robotic Process Automation, consider 3 guiding principles to align your endeavors for success.

3 Guiding Principles of Robotic Process Automation

Data Integration

Automation of almost any task requires data.  All too often that data is trapped in silos of disparate systems of record. Ripping and replacing systems of record is not only a daunting task, but often cost and time prohibitive.  Any Robotic Process Automation should be able to connect those systems and pull the relevant data into the workflow that you desire to automate quickly and easily.  Keep in mind that once the said process has completed its task, the result needs to also be pushed back to those very same silos to update those systems of record.  So needless to say, first connecting the data that will be used in any automation is a foundational requirement.

Intelligent Automation

Once the data is accessible and consolidated, the focus shifts to automating the actual task at hand.  While targeting high volume manual repetitive tasks prone to error is a sweet spot for RPA, most robust processes require some degree of logic.  Not always can automation substitute human reasoning, but many tasks can be completed if basic logic can be a part of the equation. For example, if you are an agent in a healthcare hospital systems and you receive a call from a patient about a question on an insurance claim they received, you not only need to access multiple applications to look up the patient account to verify that they are registered as a patient and validate their insurance coverage/carrier, the hospital ticketing system to see their account history to determine if this is an on-going or new issue, but also perhaps the billing system to see if they have any balances due.  If the patient is not current on billing, the logic and business rules may determine that patient be routed to the billing department first to reconcile any outstanding billing issues.  Therein lies some basic business logic that would also need to be automated to receive the call, identify the patient by their phone number, look up patient information  from 3 systems (patient registration records/ticketing/billing), apply if-then-else logic and route the customer to the appropriate representative.  So it’s not a matter of simply screen scraping data from one interface into another, but truly connecting the back end data and applying business rules or logic that drive Intelligent Robotic Process Automation.  With intelligent calculations and logic, businesses are able to increase efficiency and re-allocate their precious resources to more value rich tasks.


As with any transformative technology, the logical approach is to select a project where short term gains can be quickly realized, test out the ability to solve the business problem and deliver on the ROI.  This same route should provide a clear path way to extend the initial project across other areas in the enterprise to drive exponential value.  So your RPA approach needs to be both modular for easy maintainability (i.e. update one Return Authorization Approval (RMA) node that is used by dozens of unique processes) and powerful enough to apply more complex algorithms and logic that integrates more and more data.  

Aligning for Success

While market pressures are forcing companies to transform their businesses, Robotic Process Automation can help pave that path by freeing up the brainpower of the enterprise by relegating manual repetitive tasks to a virtual workforce.   Applying some simple business rules and logic to connected data easily, allows the enterprise to take a crawl, walk, run approach to the looming Gartner prediction that the Robotic Automation market will grow at a compounded rate of 41% over the next 5 years. 

To talk more about this, or learn more about making your robotic processes intelligent, please contact us. We look forward to helping you advance your business into the 21st century and beyond.

Related Posts

Reduced Training: The Unexpected Benefits of a Unified User Interface

Workplace productivity is a significant concern in today’s competitive economy. To stay efficient and ensure profitability, companies need to do more with less—especially regarding time and money. One way to do this is by reducing the amount of time and money spent on training employees.

The Citizen Architect Persona

We built our platform to be put into the hands of a “Citizen Architect”, someone you probably already have in your organization.  The persona of a Citizen Architect is going to be someone with an understanding of how processes work and the intricacies of the specific operating procedures.  These resources do not need to be overly technical, however any grasp of HTML or Programming can certainly help relate some of the general concepts and best practices we recommend when using SpiceCSM.  Many of our clients exclusively use non-technical resources to manage all their business process and content management while allowing technical resources to focus on the connections that push and pull data between those processes.

Trending: Phased Deployments

At SpiceCSM we have noticed a growing trend in deployment methodologies used when implementing a client's solution. When working with clients who have many overarching project goals or other unique complexities involved, we have seen many of them turn to a phased “crawl, walk, run” approach to maximize their returns and make the deployment work more seamlessly.  The concept applied here simply means that by offering an incremental approach to deploying a project or use case we try to avoid being so far sighted that it prevents progress towards a more immediately usable solution.  Instead, by focusing on and solving “micro-projects”, the synergy of those projects being completed in a more timely manner can have as big if not a bigger impact on the organization than one large project done in the same amount of time.