EverBright Compliance and Bug Holds

Background: As EverBright grows the size of our business, Our Compliance and Deal Processing Teams requires the ability to identify, review, and render a decision on potential fraudulent jobs.

As a result; The Compliance Team would like to trigger a “flag” on jobs meeting certain fraud/risk criteria and keep them from being approved or actioned on by DP.

Therefore; this new feature will enable us to put a Hold on specific workflows to block actions by the Installer and prevent unwanted approvals and payments.

Please DO NOT redirect Reps with their Organizations or Installers since they will not be able to take any action

Avoid sharing additional information regarding the hold/block in the account with Sales Reps/installers

FAQ:

What are the Two Types of Holds that can be set?

Compliance Hold	This Hold is used when there is a suspicion of fraudulent activity

Compliance Hold	This Hold is used when there is a suspicion of fraudulent activity
Bug Hold	This hold is used when there is a critical bug where we want to pause any progress on the workflow. Example: Incorrect metric in a contract that we need the customer to re-sign, but don't want them to get M3 approved where re-signs become very difficult

What is the customer impact/experience?

If a hold is in place on a workflow, the Installer will not be able to take any action. If they try to click or complete any action they will get an Error Message.

If a hold is in place on a workflow, the Installer will not be able to take any action. If they try to click or complete any action they will get an Error Message.
They will see a large banner at the top of their workflows indicating that the job is on hold and what type of hold it is
Once holds are removed from a workflow, Any Milestone submission dates or Credit expiration dates (If in M1) will be extended by the number of days of the hold