Versions Compared

Key

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

Please see SOP on the EB Product Onboarding APPROVAL ticket here: Processing EB Onboarding APPROVAL tickets

...

  • The ticket will always have the subject, “EverBright Partner Onboarding”

  • The ticket will include the information required to setup the partnership including:

    • Installer name

    • Installer contact email

    • Installer’s EverBright account manager

2. Update the SS ticket

  • Update the ticket’s Organization field to the Installer name, from the form.

  • Add the organization’s account manager and David Ellis as a Watcher.

  • Set Reporter to onboarding@goeverbright.com

  • Set Request Type to Company-specific Data Change

  • Use the Needs Configuration? Automation dropdown to select Integrated Finance

  • An initial response will be automatically sent to the customer - but since customer isn’t listed as reporter or as a request participant, the message should not be received by them.

...

  • Support will send an internal comment to David Ellis asking if approved to push live (Note: automate this step once config ticket closes - TBD)

    • Slack David for an update within 24 hours if not received

...

  • A separate “approval” ticket comes in to Jira - it will have a subject line like: “Partner Name - EB onboarding approved” and is linked to this ticket

  • Link for approval ticket SOP: Processing EB Onboarding APPROVAL tickets

Important Note: if any customer communication is needed (for example, not ready to launch in their state, etc.) - please tag their account manager and David Ellis in an internal comment letting them know that communications are needed - remember, customers are not copied on onboarding tickets