NEW: Feature update to SCB lockouts (to be released in February 2022 release)

 

 

SCB lockouts 

 

For policies that are purchased with Agile Sprint, when a Social Criminal or Behavioural (SCB) lockout is triggered then:

 

• Agile Sprint receives a Periscope Lockout (SCB) activity.
• The Broker receives a Periscope Lockout (SCB) activity.
• The activity is Open and appears under Lead Management for both Agile Sprint and the Broker.
• It can be manually closed (no restrictions).

 

However, in this scenario, when the lockout is triggered it is then Agile Sprint who are required to override it, if required/requested by the broker .  

They will have the ability to do this from their end, via Periscope.

They see the Lockout activity, as mentioned above, and action any approval from their system, which will in turn, close the Broker Lockout activity. 

 

Here is the example of the SCB Lockout:

 

 

 

Here is the example of the previous activity, once Exhale has approved the override in periscope (now closed):

 

 

 

Insured or Postal Code lockouts - Set by the broker

For quotes (regardless of the insurer), when an Insured or Postal Code lockout (set by the broker) is triggered then:

 

• The Broker will receive the corresponding lockout activity (noting if Postal Code or Insured lockout and that it was set by them).
• The activity is Open and appears under Lead Management.
• It can be manually closed (no restrictions).

 

As these are set by the broker, the broker can override, via Periscope. Then the customer OR broker/user can proceed with policy purchase.  (Overrides are completed in periscope, and by users with permission/access to that module). 

 

 

Insured or Postal Code lockouts - Set by Agile Sprint

For quotes with Agile Sprint, when an Insured or Postal Code lockout (set by Agile Sprint) is triggered then:

 

• Agile Sprint will receive the corresponding lockout activity (noting if Postal Code or Insured lockout and that it was set by Agile Sprint). 
• The Broker will receive the corresponding lockout activity (noting if Postal Code or Insured lockout and that it was set by Agile Sprint). 

 

Here are examples of Insured and Postal code lockouts set by Agile Sprint:

 

 

In this scenario, when the lockout is triggered it is then Agile Sprint who are required to override it, if required/requested by the broker .  

They will have the ability to do this from their end, via Periscope.

 

 

 

 

Example:

Agile Sprint have a postal code lockout, which you are aware of, BUT SGI are also not quoting for the risk.

 

Once you have quoted and if you save the Agile Sprint quote (where you know that the postal code lockout should appear), those existing quotes are 'spoiled' because they/you chose Agile Sprint and went to Purchase. The practice should be to start a new quote for the customer and chose SGI this time.   Going back into the quote with the lockout will not provide a quote. 

 

It is also possible that the other insurer or insurers are not switched on for that product or province or their quotes are down or they are declining to quote. Not all lockouts are coded into the system for other insurers (like postal codes or territories they do not write in)

 

 

They will be unable to proceed with the quotation or proceed to Checkout and Pay.  They receive this message, and the information to contact your office, if they want (your telephone number appears on the screen) :

 

 

 

 

An error message box could pop up if there is a lockout or decline from the insurers.  Even if the change that you are trying to make is not linked to changing the address, this would block the Change Policy.    The process, when the error message appears,  should be to check Periscope (or ask someone who has permission to access Periscope) and see if the postal code is a lockout.  If it is not in your own platform as a lockout, it might still be on the insurers side, so you should contact them and ask them if that is what is causing the error.  Discuss with the insurer what action needs to be taken to resolve or process the change.   If support is required after this has been done, then submit a ticket including all steps taken and any emails from the insurers, if provided.

 

 

 

This activity shows that the risk was declined due to Periscope Insured lockout.   It was set by the brokerage. The platform is working as expected and there is a decline.

 If you have a query about this, check your periscope module or speak to your digital champion. It was set by your brokerage if it says 'set by-------------', in our example above it is set by the test brokerage ' Chirp'.

 

There is more clarity on the activities for lockouts, in bond.

The lockout reason and who set the lockout will show. 

 

In this example, it was set by the carrier, Exhale.