FAQ: 1.5 Application Process
How is the application process developed?
Application can be processed online. Thanks the Lifeware’s service permission system it is also possible to support many functions and departments.
Is there a graphic representation or a description of the implemented processes?
Yes, however, every company works according to its own insurance processes. The documentation that Lifeware provides represents only a possible solution set.
Are there scheduled or non-scheduled changes? What are the triggers for these actions?
Scheduled: Technical extrapolation, dynamics, premium collection, premium payment, scheduled Reporting Non-scheduled: contract mutations: account mutations, mutations of insured, broker mutations, beneficiary mutations, etc. The batches are triggered by the scheduled execution time or by a specific customer requirement.
Is it possible to redirect an application?
Is the risk analysis supported by the system?
Yes, but it needs be reworked for every customers' needs
How are risks surcharges defined?
Online manually, because it should be done by the responsible person.
Is it possible during the application process to define exclusion clauses?
Yes, not only exclusion clauses are supported but also the production of a counteroffer. The application cannot be transformed into an insurance policy until the customer accepts the counteroffer.
Are the histories of applications and contracts stored?
Yes, in contrast to the offers, the applications and the contracts are filed in the database forever. Even if an application is deleted it still leaves a trace in the system
Which business service processes are supported by the system?
All the necessary data is available online.
Does Lifeware’s service have standard interfaces with external key systems?
No, the system does not have standard interfaces but customized interfaces. Typically the external systems are management information systems, commission systems, partner systems, etc.
Is it possible to decentralize the application’s process to the point of sale?
Yes, because all the processes are integrated in one central system and the system is available on the Web. It is not important where the user physically sits. Much more important are the user permissions: depending on the permissions the user can work either
  • as a broker and make offers
  • or as a clerk and process applications.
Is the permission system based on the user’s function?
Yes, it is possible to personalize the process according to the user’s role. This is done with the permission system.
How does an application become a contract?
The transfer from the application process to the contract administration process is called “put in force”. The put in force process is responsible for checking that all the rules are respected and consistent: only at this moment an application becomes a contract.
© 2017 Lifeware SA
Contact us | FAQ | Solution by Tinext SA