Versions Compared

Key

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

Swell has multiple requests that that they can make. Below is how to process their multiple new partner requests.

1.

...

Partner requests form will be sent directly to Support

  • The email will be sent from Tong-Tong as a forward. The body of the email will contain the org contact email.via as a Typeform. It should look something like this.

  • Make the reporter: Ahmad Murphy (amurphy@swellenergy.com).

  • Add as request participants skielas@swellenergy.com , peter@swellenergy.com

  • Mark the ticket as a Company Specific Data Change

  • Mark the account manager (of the partner) on the SS ticket as a watcher (look on the QuickSight “Support Salesforce” dashboard

  • Provide the initial response

2. Make a CS ticket 

  • The CS tick should contain:

    • Assignee = CS Team Member

    • QA Assignee = QA Team Member

    • Epic = Stable Solar ConfigurationsCopy the name of the installer into the description of the ticket. Swell Configurations

    • Ticket Type = Int Fin

    • Component = Swell Financing

  • Instructions on how to make a linked CS ticket from Support are here.

3. Account is configured

4. Once CS UAT is complete, Support will

...

close the ticket.

Hi {Customer},

Congrats, Stable Solar's products are now live in your account!

/wiki/spaces/SS/pages/714866740 are some training materials on how to use Stable Solar services in Sighten. Please let us know if you have any questions.

Have a great day!

...

  • Support team will receive notice that CS ticket is in UAT.

  • Support will send customer email below and send launch emails.

...

Requester

...

{Account contact email}

...

Participants

...

Watchers

...

{Account Manager}

...

Summary

...

Stable Solar's Products are Live in your Sighten account!

...

Comment

  • done, and new workflow status will read “waiting for customer”

  • After 24 hours, if customer does not reach back out, Support will change SS ticket workflow from “waiting for customer” to “closed”