Settings

System Wide > Administrative Alerts > Contacts

Login Updates

The below email is sent when an agent updates his/her login from the Agent Portal or when a user's login information is updated on his/her contact in the Contacts module of the Administrative Portal:

BriteCore Message: Login Updated
Your login has been updated successfully. Your username is [this] and the password is [this].
Please keep this email for future reference.

Failed Email Transition

A Failed Email Transmission email is sent when a BriteCore-generated email fails to reach its intended recipient. The contents of the original email will be included in the Failed Email Transmission alert email. The following actions may initiate this alert:

  • BriteCore could not connect to the SMTP (email) server to send the email
  • BriteCore unexpectedly disconnected from the SMTP server when attempting to send the email
  • The SMTP server refused to accept the message data that BriteCore attempted to send
  • The SMTP server refused the recipients
    Transmission failures are not reported for instances where an email response from the recipient server is sent back to the sender (e.g., Out of Office reply). Such transmissions indicate successful delivery of the email to an inbox

System-Generated Email Reply To

An email is sent when a contact (i.e., agent) replies to an admin@britecore.com email rather than replying to a staff's email.

Password Lockouts

The below email is sent when a user locks him/herself out of BriteCore per the Settings > System Wide > Login Information settings:

BriteCore Alert - Password Lockout
A user's account has been locked out of the system due to too many invalid password login attempts. The account will be unfrozen in 4 minute(s). Below is the username the user was trying to use to log into BriteCore.
Username: [username as stored in BriteCore]

System Wide > Administrative Alerts > Processing

Processing Errors

Processing error emails fall into the below categories.

Nightly Processing Errors

Recipient(s) receive an email like the below regarding any error in processing that could have occurred. Errors may include settle_batch_and_run_tsr, process_auto_pay, or process_cancellation_pending_or_non_renewal. For most errors, submit a ticket to IWS along with a copy of the error:

BriteCore Alert: Nightly Processing Errors
[information related to error, usually code]

Renewal Commit Failures

Recipient(s) receive an email like one of the below with a list of renewals that failed to commit during overnight processing. Failure could be due to various reasons. In most cases, you will need to access the policy in BriteCore and manually commit the revision:

BriteCore: Renewal Commit Failures: [carrier name]
Renewal revision (YYYY-MM-DD) for policy 10-2017-1 couldn't be created. System message:
System Renewal Revision was not created because of the existence of an uncommitted, manually-created Renewal Revision. You must manually commit this revision.

Persistent Builder: Failed Renewal Processing: [carrier name]
Persistent Builder encountered an error while trying to renew policy 10-2016-1. To prevent damage to the policy's integrity, the new revision (YYYY-MM-DD) has been removed.
Please submit a ticket with the appropriate priority level and include the following information:
Policy Number: 10-2016-1
Error Date and Time: 2016-11-15 07:38:16.053643

Deliverable Creation Errors

Recipient(s) receive an email like the below with a list of deliverables that BriteCore could not generate during normal processing. In most cases, you will need to access the policy in BriteCore and regenerate the deliverable:

Deliverable Creation Error: [carrier name]
Policy 10-2017-1 failed to generate [name of deliverable]. Exception: [detail of error]
Bail Out!: [carrier name]
[name of deliverable] deliverable failed to generate: [reason for failure]

Vendor Errors

Recipient(s) receive an email like one of the below when an error occurs with a supported vendor:

BriteCore Alert - Dropbox enabled but not authorized.
Dropbox integration for print job backups is enabled in BriteCore but not authorized. Please visit [URL] to authorize BriteCore to upload print job backups to your account.

BriteCore Alert: Nightly Vendor Upload Errors
Traceback (most recent call last):
[code]
[error, such as KeyError: ‘hostIP’, error: [Errno 111] Connection refused or error: [Errno 104] Connection reset by peer]

BriteCore Alert: Ambiguous ISO Protection Class
The following policy could not determine an ISO Protection Class for the property "Property 1". Please choose a new one, then rate and commit the policy manually.
10-2016-1

Modules > Policies > Contacts

Show Premium Finance Company

When enabled, this setting displays a designated field on a policy to which a premium finance company may be added.

Suggested Interests

A definable list of interests a contact may have in a policy. When a contact is added to a policy, the user may select from these options.

Mortgagee Types

A definable list of designations a mortgagee may have in a policy. When a mortgagee is added to a policy, the user may select from these options.

Attach an Agent/Agency to a Policy

Attach agencies to policies.

Modules > Policies > Policy Numbers

Set a prefix and suffix for your policy numbers.

Modules > Policies > Terms

Terms

Define the policy term length for each policy type.

Reference New Credit Scores Every X Policy Terms

If a credit scoring vendor is enabled and credit scores are tied to rating, this setting locks a contact's credit score to a term for X terms. A credit score is locked to a term once the policy is issued (committed). If an effective date endorsement is created and a new score exists, the term will then reference the new score.

Notes

Since a score is locked to a term upon issuance (commit), a new score should be pulled prior to the renewal of the policy. When the setting is set to 0, the first locked score will be locked indefinitely. Given this, the setting should be set at least to 1.

Testing

The below queries will help test this functionality. All testing should take place in a test, rather than live, site:

# The score locked to the term
Create a policy in a test site then update the policyId
SELECT effectiveDate, expirationDate, termCreditScore FROM policy_terms WHERE policyId = '105de00d-7e5f-4f0e-a0f3-6a293bdcdfd6';

# The person's scores
Locate a contact then update the contactId
SELECT dateAdded, score FROM credit_reports WHERE contactId = '145eac40-9d48-4b98-bd05-0a1b8ade59b8'
ORDER BY dateAdded;

# Inserting a new score
Update the contactId, dateAdded, and score
INSERT INTO credit_reports (id, contactId, dateAdded, score, reportNumber, content, error, vendorId)
VALUES
(uuid(), "145eac40-9d48-4b98-bd05-0a1b8ade59b8", "2016-12-01 15:23:59", "789", "123456789" , NULL ,"0","96185f70-6efb-11de-9dde-000c2976c0ee");

Modules > Policies > Processing

Retain the default setting of manual

Modules > Policy > Policy Lifecycle > Cancellation

Cancellation Reasons

The below list is a sample of possible cancellation reasons to be entered into BriteCore:

  • Agent no Longer Represents Company
  • 1st 60 Days - Does not Meet Underwriting Guidelines
  • Changing Policy Type
  • Foreclosed Property
  • Fraudulent Act
  • Fraudulent Claim or Settlement
  • Fraudulent Statement
  • Increase in Hazard
  • Insured's Request
  • Loss History
  • Loss of Reinsurance
  • Material Change in Risk
  • Material Misrepresentation or Nondisclosure of Material Fact
  • Non-Payment of the Premium
  • Omission or Concealment of Fact Material to the Acceptance of Risk
  • Property is Vacant
  • Property Sold
  • Substantial Breach of Contractual Duties
  • Substantial Increase in Hazards Insured Against by Reason of Willful or Negligent Acts or Omissions by the Insured
  • Transferred to Another Policy within the Company
  • Underwriting

Modules > Policy > Policy Lifecycle > Non-Renew

Non-Renew Reasons

The below list is a sample of possible non-renew reasons to be entered into BriteCore:

  • A Fraudulent Act Against the Company
  • Agent No Longer Represents the Company
  • Claims History
  • Credit Report
  • Credit Score
  • Criminal Conviction of the Insured
  • Declining Condition of the Property
  • Did Not Return Required Company Forms
  • Does Not Meet Corporate Charter or Articles of Incorporation Requirements
  • Failure to Institute Reasonable Loss Control
  • Filed for Bankruptcy within previous three to five years with a Customer Performance Rating below the neutral tier
  • Filed for Bankruptcy within the previous two years
  • Foreclosed Property
  • Increased Hazard
  • Lack of Pride of Ownership
  • Liability Risk Exposure(s)
  • Loss History
  • Loss of Reinsurance
  • Material Change in Risk
  • Material Misrepresentation
  • Not Owner Occupied
  • Payment History
  • Property Condition
  • Request from Agent
  • Risk is No Longer Eligible for Replacement Cost Coverage
  • Risk is Vacant or Unoccupied
  • Risk Not Insured to Value
  • Substantial Breach of Contractual Duties
  • To Be Re-Written on a Different Line of Business/Policy Type

Settings > Modules > Policies > Policy Lifecycle > Cancellation

Allow Mortgagee Extension for X Days

When enabled, BriteCore reports a cancel date of X more days via InsVista to the mortgagee. BriteCore, however, still processes the policy on the original cancel date. In other words, BriteCore processes the policy as if there is no extension. The extension is reported to the mortgagee through InsVista only.

When a mortgagee is added to a policy, the extension automatically applies via the Grant Mortgagee Extension of Cancellation checkbox on the policy. To remove the extension, uncheck the box.

This feature was coded specifically for New York clients.

Lines > Effective Date > Policy Type > Limit Threshold

Limit Threshold upon which a Policy of this Policy Type Sends an Administrative Alert

Set a limit threshold per policy type for new and renewal business. Once the threshold is reached, an email is sent to a designated recipient(s).

When this Threshold is Reached, a Policy of this Policy Type Cannot be Written Without Administrative Approval

This second setting, when checked, requires an authorized user enter an approval code before the policy can be processed further.

Preliminary Work

  1. Determine the applicable coverage limits and value for each policy type. For example, when Homeowner's Coverages A, B, C and D limits are greater than $1,000,000, send an email
  2. Determine if an approval code will be needed in order to process policies where the limit is above the threshold
  3. Designate an authorized user who will maintain and enter the approval code when necessary
  4. Determine an approval code

Setup in the Lines Module

  1. For each applicable policy type, enter an amount for the Limit threshold upon which a policy of this policy type sends an administrative alert setting in Lines > Effective Date > Policy Type
  2. If an approval code is desired, check the When this threshold is reached, a policy of this policy type cannot be written without administrative approval box
  3. When the limit is reached, a popup will generate. Enter wording for that popup in Text for popup when limit threshold is reached. For example, "You have requested limits above $1 million in coverage. Please contact the Underwriting Department for approval"

Setup System Tags

  1. Navigate to Settings > System Wide > System Tags
  2. Select the Reinsurance Limits tag
  3. Select the Effective Date
  4. Click Tag New Items
  5. Locate the coverage(s) whose limits should be considered when calculating the threshold
  6. Check the box
  7. Repeat for all applicable coverages
  8. Click Done

Setup the Alert

  1. Navigate to Settings > System Wide > Administrative Alerts > Lines
  2. Enter an email address(es) for Limit Threshold Reached, Administrative Approval Required. When the limit threshold is reached in either the Agent or Administrative Portal, the below email is sent:
    Property limit threshold reached - 10-2016-1  
    The property limit threshold has been reached, please review.  
    [link to policy]

Setup the Approval Code

  1. Determine an alphanumeric Approval Code
  2. Communicate the code to IWS
  3. (IWS only) run the below, replacing 'approval code' with the desired code
    #UPDATE settings SET value='approval code' WHERE option='limit-approval-code'

Important notes

  • The threshold applies to BriteQuote and BriteCore users (agents and staff)
  • When the limit of the selected item(s) exceeds the threshold
    • An email will be sent to the designated contacts
    • If the approval code setting is checked, the user will receive a pop-up with the defined working and a prompt for an Approval Code. No further changes to the policy can occur until the Approval Code is entered
    • The authorized user enters the Approval Code on the policy in the Administrative Portal of BriteCore. This means the authorized user does not need to login to the Agent Portal to enter the Approval Code
    • Once the correct code is entered, the user will be able to proceed with the quote, application or policy. The following will be true
      • If an application, it must be submitted unbound
      • All limits below the approved limit will automatically be approved
      • All limits above the approved limit must be approved again
  • Whether the Approval Code is entered correctly, a note will be created in the policy’s Notes tab
  • The Approval Code is stored in the database to keep unauthorized users from accessing it
  • If Loss Exposure Groups are used to group risks, the limit threshold applies only to those tagged items that are within the same-numbered group

Feedback

Report unclear or missing documentation.