Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-24 01:18:42 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 84

Update README.md (#8809)

Browse source 
Creating a new PR for the handbook edits I made as there is an issue in the UI currently.
This commit is contained in:
Zay Hanlon 2022-11-23 20:10:44 -05:00 committed by GitHub
parent dfefe64b3b
commit 057b06ad6f
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
handbook/customers/README.md
View file

@ -18,10 +18,10 @@ This workflow outlines the process that sales and customer success can follow wh
1. (AE) A customer is sent an order form
- If the customer requires the use of their own legal contract, the account executive (AE) will send that contract to the business operations (BizOps) team for review. Then:
- If the customer can use DocuSign, the AE sends out the order form. The AE must cc themselves and BizOps on the order so that all parties receive a fully executed copy when signing is complete.
c- If the customer does not use DocuSign, the AE sends out the order form directly to the customer.
- If the customer does not use DocuSign, the AE sends out the order form directly to the customer.
- The AE then sends the paper signed copy to BizOps for Fleet review and execution (via DocuSign by the CEO).
- BizOps will cc the AE and stay cc’d on the contract when the final copy is sent to the CEO for Fleet execution.
*Note: Chief Revenue Officer (CRO) serves as backup to BizOps
- Note: The Chief Revenue Officer serves as the backup to BizOps
2. The Customer and Fleet sign the order form.
- (AE) The AE adds the fully executed contract to the opportunity record.
- (AE) The AE marks the opportunity 'Closed Won' and includes the 'Closing Date'.
@ -42,7 +42,7 @@ This workflow outlines the process that sales and customer success can follow wh
- Any proof of concept (POC) notes that are relevant
- Customer expectations for timeline
- Server deployment type
5. (CS) The Head of CS kicks off the CS responsibilities in the 'New Sale Issue'
4. (CS) The Head of CS kicks off the CS responsibilities in the 'New Sale Issue'
- Create an “Existing Business” renewal opportunity in Salesforce.com (SFDC).
- Send the customer [welcome email](https://docs.google.com/document/d/11zrktUdb5FmJQgMyhtU26Wa-YzMES2jGcqEC7cw8tAo/edit) (internal drive) & [deployment checklist template](https://docs.google.com/spreadsheets/d/1tAQV6AqrRhqKusbA9Z6-5RBtOUknjkXVJXyF-Qp1Zls/edit#gid=1709744959) (internal drive)
- Create the customer Slack channel