Versions Compared

Key

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

...

STEP

ACTION

1

  • Does the customer’s concern warrant Compliance’s involvement?

    • If yes:

      • Collect and consolidate as much information/proof as possible

      • Go to Step 2

    • If no, follow appropriate process(es) and Stop

2

  • Seek approval to notify Compliance:

    • Internal Comment:

      • Summarize the matter

      • Provide a brief overview of actions taken during your investigation

      • Note any relevant findings/discoveries (e.g., reviewed WC, etc.)

      • If provided, provide proof/documentation shared

      • Request approval to involve Compliance

    • Tag (@): Cassandra Mercado, Sabin Abad

    • If false/unfair/deceptive trade practice by an installer, Label: “Promises”

    • Go to Step 3

3

  • Was approval received by a Team Supervisor?

    • If yes,

      • Update the EBH ticket status to: “Waiting on Compliance

      • Go to Step 4

    • If no, follow appropriate process(es) and Stop

Info

Note: Updating the EBH ticket status will create a duplicate, linked POLICY ticket in a separate project: EB Compliance. This will allow you to facilitate conversation internally with the Compliance team. When customer interaction is necessary, it would be done via the original Support ticket.

4

  • Locate the linked POLICY ticket created

  • Update the ticket:

    • Reporter: Aileen Kozlowski

    • Request Participants: Steven Edwards, Christopher Strain, Cassandra Mercado, Sabin Abad, and, if false/unfair/deceptive trade practice by an installer, the installer’s Account Manager

    • Ticket Status: Waiting on Compliance”

    • Comment:

      • Include an overview of the matter, actions taken, findings made, copies of any supporting documents, Engine job link, and request review/input by the Compliance

Info

Note: Ensure you frequently monitor the ticket for updates.

...