Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 5 Next »

These customers are existing users of the platform, however new to EverBright Product or Products

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. This includes any changes to products, states allowed, etc.

Please see SOP on the EB 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 - Product Onboarding”

  • The ticket will include the information required to setup the product(s) 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 Onboarding

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

3. Update the CS ticket (created by the automation)

4. Account is configured (by config team)

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

6. Support will close the EB Product Onboarding ticket

  • Ticket can be closed after config is complete.

  • Approval will come in a separate ticket; products will be made active in that ticket.

 

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

  • No labels