How to Improve Insurance Agent Productivity using Rule driven Automation
Published by Rajgo January 4th, 2007 in Business Rules, BRMS, Rule Engine, Business Rule Engine, Business Rules Management System, Insurance, BankingWell, wishing all you bloggers out there a happy new year.
I was reading Jacques Kemp, and here he has written about Agent Productivity and Retention. Some excerpts here.
A 2006 Limra report, Agent Production and Survival Asia Region, tells us that of newly hired agents in 2004 in Asia, 72% stayed in their function after one year. Of the ones that were hired in 2003, 58% did not leave the company. Agents hired in 2002 and 2001 stayed in their function in 70%, respectively 81% of the cases. The four-year retention rate average was 20%.
Insurance agents need considerable training and the insurance company that can improve retention rates would thus be able to significantly reduce costs of recruiting, hiring and learning. That is also more or less Limra’s conclusion in the report on what to do: hire, train, compensate and help agents better in doing their job.
The ending observation is also interesting
By rolling out online hiring tools with pre-filtering profiles, embedding efficient e-Learning in the agents training program, providing agents with tools (mobile or desktop based), and many more such activities, ING and competitors in one way or the other, are trying to push the break-even moment sooner.
Paradoxically enough, this will not entirely solve the issue because retention after the break-even moment becomes an even more urgent matter that cannot be addressed anymore with a first aid kit of training and hiring.
If I got this right, these are the challenges with Sales agents.
- Long learning curves for new agents. There are so many products to learn about
- High attrition rates
- High cost of training. It takes months/years for agents to become productive, and even longer for the company to break even
- Decision making by the sales agent is manual, and Needs expertise
Approaches like improved training are at best short gap measures. Now, how about something like this.
- Creative decisions that agents take, like say, suggesting college tuition payments for children, what if your Agent portal can suggest this possibility to the agent, if given the customer details
- What if the system can suggest the best product match for a prospect, and suggested benefits.
- What if the system can make appropriate up-selling, cross-selling recommendations?
- What if the system can suggest what information to collect from a customer/prospect?
- What if the time and cost spent on training, can be used to build a intelligent product recommendation/agent assist service that will take the decisions that an agent is expected to take.
I would venture out to say, that such a solution is not wholly unimaginable. Business Rules Management Systems, provide for such a solution.
Now let us see, how we can think of a solution.
- Capture all the product eligibility, underwriting guidelines, rate sheets as Business Rules using a Business Rules Management System
- Capture the customer/product match logic that is now available with the company, with experienced agents as business rules (recommendation rules)
- Supply applicant information to the Rule engine, and the rule engine takes provides the appropriate recommendation
Now, depending upon the extent to which the rules have been captured you can do any of the following
- Provide an online, fully automated Web Agent that will guide customers/prospects using a Rule driven user interface through out their interaction
- Provide an Agent portal that will provide recommendation assistance to Sales agents on the field.
So, what are the benefits that I see with this approach?
- I am not sure you can do without agents, as many customers require a personal touch
- But, the time & money spent in training agents on all the company’s products can be brought down greatly by deciding to automate the business decisions that agents are expected to take. Remove the expertise factor, essentially!
- Get rid of agents for low margin products, and use a Web agent exclusively
Well, what do you say to that?



















Much of this is being done today in one division at John Hancock with an application set that is about 5-6 years old. I was just talking with them today about the next generation of this system. Though I was not involved in the implementation of the current and previous generations, I did advise the lead developers on the architecture of the system. Among other things, I designed a custom inference engine (BRMS), blackboard system and language for their applications. Unfortunately, their implementation produced a monolithic behemoth where the front end and back end were too closely coupled and dependent. Now they need to fix that and a few other things. They also started adding features to the rules engine to do things like drive UI composition just because it seemed like the place to hang it on. Future work will entail putting some of the “intelligent” capabilities upstream into the product management area of the business process.
Client retention is a larger issue than agent retention and both areas can benefit from this type of thinking.