Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Did they include all the policy types noted on the original ticket - i.e. Auto AND General Liability if both are about to expire

Info

Their accord/COI lists the basic information listed above. However, many organizations use various insurance brokers and can/do send in multiple documents.

...

2

...

  • Create a case in Salesforce:

Info
  • Upload the insurance document to the existing Case under the related tab

  • Relate the email as follows:

    • Name: Organization

    • Relates To: Case

...

If a customer indicates that they are exempt from Worker’s Compensation (by their state), reply that EverBright requires a state-issued document showing that the organization is exempt from Worker’s Compensation.

Create a case assignment for Risk on the existing case and request a review of the documents once received.

...

If the “Description Section” section has any additional information that may conflict with current policies or expectations, then please reach out.

Info
  • If any of the above information is missing, tag Malcolm Cardone Spence in the case feed for next steps.

  • If the phone number is missing, google the main number for the insurance company rather than asking the customer for it.

...

3

...

  • Once you’ve determined that the insurance documents are sufficient and complete, create a CS ticket to send to configuration.

Info
  • Mark it as a “Task”

  • Enter the component (org name),

  • Epic: EverBright

  • Assign based on workload (add link to dashboard)

...

4

  • Copy the link to the CS ticket and paste it in the Case Feed

...

5

...

  • When configuration is complete, send an email with the following note to the customer

Info
  • Use the ‘Insurance Updated’ quick reply in CXone

...

6

...

Background: Installers quoting EverBright products must have valid insurance policies on file with EverBright specifically named as additionally insured. If the policy has expired, they will be blocked from executing deals.

Effective October 21, 2024, the responsibility for notifying installers of expiring or expired insurance policies has transitioned to the Sales & Account Management teams. The Support Team will no longer be involved in reaching out to customers regarding insurance updates.

New Process Overview

  • Sales & Account Managers (AMs) are now responsible for notifying installers about expiring or expired insurance policies.

  • Support will no longer be responsible for notifying customers of expiring insurance.

...

If

...

Then

...

Request received from chat, phone

  • The installer reaches out to support about their expiring insurance

  • Advise the customer to email the COI to support@goeverbright.com

...

Request received via email

  • The installer/organization admin reaches out to support about their expiring insurance

...

  • Follow the steps below: How to process Certificate of Insurance (COI) Updates

How to process Certificate of Insurance (COI) Updates:

...

Step

...

Action

...

Reference

...

1

...

Check the document attached to the email for correctness

...

  • First check - Does the named insured match the organization’s legal entity name

Info

They may operate under a different name - make sure their legal name is on the policy - i.e. Western Valley Development dba Radius Energy; if in doubt, check Salesforce

...

  • Is EverBright listed as an additional insured on their General Liability and Auto Insurance (not needed on workers comp insurance)?

...

...

  • Everbright is required to be listed as the certificate holder for all customers that offer EverBright TPO (third-party operator) products: EverFixed and EverFlex

Info
  • RIC-only customers do not require EverBright as a certificate holder

  • TPO and RIC customers require Everbright as a certificate holder

  • Information can be found in the MISA Type Executed field in Salesforce

  • Check-in Settings under Finance products (EverFixed, EverFlex)

...

  • Is the policy limits within our requirements? ( Installers may hold limits above the below ranges)

Info
  • General Liability - $1,000,000 per occurrence; $2,000,000 aggregate

  • Auto - $1,000,000 Combined Single Limit

  • Workers' Compensation - $1,000,000

  • Non-owned Auto - $1,000,000 (If an installer claims to not have autos then a Non- Owned Auto Policy can be provided)

Background: Effective December 12, 2024, the updated process for reviewing and approving Installer Insurance Renewals includes an initial review by the Risk Team before the insurance policies are updated on the platform. The submission process remains the same, but additional time (3-5 days) is allotted for the Risk Team's review. Requests via Slack are no longer accepted. Follow this step-by-step guide for the updated process:

STEP

ACTION

REFERENCE

1

Notification of Expiring/Expired Insurance

  • Installers are notified of expiring or expired insurance through Engine notifications.

  • Account Managers receive the "[Internal Only] Take Action: Installer Insurance Expiration Report" email containing the list of Installers with policies expiring within 31 days or already expired.

2

Submission of COI(s)

Info

Confirm the following:

  1. Installers or Account Managers submit the Certificate of Insurance (COI) to Support.

  2. Submission Method:

Case Creation:

  • Support creates a Salesforce case for the submission.

Follow the Creating and Assigning Cases process

3

Case Assignment to Risk Team

  • Support assigns the case to the Risk Team for review.

  • Use the "COI Review" referral reason when assigning the case.

4

Risk Team Review

Validation Process: The Risk Team validates and approves/rejects the COI(s).

If COI is Approved proceed to Step 5

If COI is Rejected proceed to Step 6

5

  1. Create a Jira Ticket:

    • Support creates a Configuration Jira ticket to update the insurance policy in Engine.

  2. Configuration Team Updates Insurance:

    • The Configuration Team updates the insurance policy in Engine (allow 3 days for this update).

  3. Confirmation:

    • Once the update is complete, Support confirms with the Installer/Account Manager.

    • Please use the quick reply named “Insurance Updated”

CLOSE Case Ticket

Follow the Handling Configuration Requests in Salesforce process

Use CS Installer Configuration - CS-28900 Epic Number

6

Rejection Notification:

  1. Support notifies the customer or Account Manager of the rejection.

  2. Include details regarding why the COI was rejected and the necessary next steps.

CLOSE Case ticket

Please use the Quick Reply named “COI Rejection”

...

Important Notes

  • Processing Time: Expect 3-5 days for the Risk Team review and an additional 3 days for the Configuration Team to update insurance policies on Engine.

  • No Slack Requests: Do not accept requests related to COI submission or insurance renewal in Slack Configurations or Customer Support channels.