Please see SOP on the Initial EB Product Onboarding ticket here: Processing EverBright Partner Onboarding Requests
...
Link to the Partner’s SS EB Product Onboarding ticket - and then close the onboarding ticket
If there is no active EB product onboarding ticket, send David Ellis an internal comment / slack for direction; he will initiate that ticket.
Update the Approval ticket’s Organization field to the Installer name from the subject line
Make sure the account manager is copied as a request participant
Make sure the Reporter is set 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 first available (config schedule - select an employee who is working at the time you’re creating the ticket so it’s expedited) ADD LINK
4. EB Products are turned on / activated (by config team)
Config will activate the product in the account according to the instructions
When pushed live - the config team close the CS ticket and the SS ticket will be moved to “waiting for support” (TO DO: automate this step to close the SS ticket too with a note that the products are launched)
5. Support will close the EB Approval ticket
...