Versions Compared

Key

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

Note: These tickets are for installers NEW to both the platform and to EB products.

Please see SOP on the EB Onboarding APPROVAL ticket here: Processing EB Onboarding APPROVAL tickets Important: Support can only process tickets originating from David Ellis' Onboarding team; i.e. if a request comes from an account manager, please have them loop in onboarding@goeverbright.com and submit the ticket according to process.

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

...

  • 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 Onboarding

  • Add Request Participants: allsales@goeverbright.com, Alice.Reeve@goeverbright.com, Tim.LoCascio@goeverbright.com, jordana.norring@goeverbright.com, and the organization’s account manager.

  • 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 Installer name)

  • Change the Epic to EverBright Configurations CS Onboarding

  • QA assignee - Cherish Sharma

  • 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”

5. Support will initiate approval to push products live

  • 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

...

  • If any customer communication is needed (for example, not ready to launch in their state, etc.)

    • Tag the Account Manager and David Ellis in an internal comment and follow this SOP to escalate to the ticket to the Account Manager

    • Priority - High

Note

Customers / Installers are not copied on onboarding tickets

5. Support will close the EB Onboarding ticket

...

  • 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

...

:

Hello,

Configuration is complete, and the account is ready to launch. Please coordinate with [account manager] to schedule Onboarding training. [Account manager] please confirm all required documents have been submitted.

Regards,

  • Close the ticket (no need to wait 24 hours)