Jump to content
  • 0

Suggestions on making the renewal invitation process slicker?



Hi. We are a high volume, small premium, personal lines operation and currently invite all our invites manually. This involves doing a batch print of all due renewals, manually loading the premium and rebroking those that need be. We then do another batch print to generate letters to be sent out. We anticipate that 75% of all renewals could be automatically processed with no adjustment.


What we would like to do is automate as much of this as possible.


Does anyone have any suggestions on how to do this without spending nearly £32K on what OGI are quoting to automate it.




Link to comment

3 answers to this question

Recommended Posts

  • 0

Hi Mark


Being as I have built the majority of our personal line products using Scheme Toolkit they are mostly fully automated. We run batchcalcs which amend NCB, index link (if applicable), apply new endorsements (again where applicable) and of course raise the renewal transactions.


We then do what you do as in use Client Letter Print to print them out en masse.


Kind regards



Link to comment
  • 0

Hi,  it sounds as if you have already checked out the automated standard system options for         "  * Letter Generation"  - although I must admit it has been years since I have had to look at it.


The BROOMS system also offers -     "Chaser Sequence Maintenance"  for chasing - although by letter is maybe a tad old fashioned these days.


An alternative method - You can also generate letters when setting up the transaction with a  Date to be Sent (  print date in advance) and just print all unprinted letters on a daily basis.

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Posts

    • Partnership deals that are in the interests of Open-GI's profits and not the best infrastructure for their clients. HP - (30% returns from printers to servers when I worked for a HP partner. Haven't been pleasantly surprised with 6 more years of dealing with their hardware). Microsoft - Oh ook another 60 security holes and a zero-day (mean nothing anyone other than Microsoft can do to fix it) that has been actively exploited for over two months now. Sophos - Tavis Ormandy of Google's top security team, charitably wrote a 30 page paper, which concludes that the company was "working with good intentions" but is "ill-equipped to handle the output of one co-operative security researcher working in his spare time". Recently, they forced through Multi-Factor Authentication for their "cloud" management site (which has a really useless, coutnerintuitve and uninformative interface), that is completely useless in a ransomware take over, you could easily be left without access to your "cloud". They should implement physical keys if they are going to push for this, not software methods that can be taken over as part of an attack. 
    • The real question for Open GI is why is only 1 browser supported?   Why do you think that is?   10 points for each correct answer …
    • Open Attach hasn't changed. It should be a database, more secure, better control over user access, find and retrieve files more quickly, et cetera.   Now everyone is being pushed to use MS Edge. I thought I saw a notice that you could use Firefox or Chrome, that seems to have been retracted and no one in support knows anything about it. Not sure I want to trust payments to a web browser, which is made by the some company that produces Windows, which has 50-100 vulnerabilites each month with 1-6 of them being zero days.
    • A year later, it doesn't seem to be any better. Still getting frequent news flashes of it being down, having problems and one case of a whole afternoon and evening of it being unvailable.    Core seems to be having problems, the level 2 and 3 staff appear to have been lumped into level 1, so their time is being wasted with donkey work and it seems that when people leave, they are not being replaced. Support turn around times are growing and bugs in the code are increasing.
    • So #BIBA for Real is back! Anyone else going?    Handy Tip - "Speak to more people you don't know, than those you do know"   You can thank me later - with flowers 🌻 💖
  • Create New...