Page Comparison

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

1. Onboarding form (ticket) will be sent directly to Support

The ticket will always have the subject, “EverBright - New Partner Onboarding”
The ticket will include the information required to setup the partnership including:
- Installer name
- Installer contact email
- Installer’s EverBright account manager

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.

Find the automatically generated linked CS ticket (you may need to refresh your SS ticket to see the linked ticket)
Add Components (Contractor name)
Change the Epic to EverBright Configurations
Add assignee names based on workload https://sighten.atlassian.net/secure/Dashboard.jspa?selectPageId=1206

Configure the product in the account according to the instructions
When complete (but not pushed live) - the config team close the CS ticket and the SS ticket will be moved to “waiting for support”

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

...