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 59

Handbook – updated Sales team writing principles (#6792)

Browse source 
* Update sales.md

- I renamed the writing principles section. The previous version was a bit of a tongue-twister for me :)
- I broke the principles into subheadings to make the section more scalable. We may need to add more principles later.

* Update sales.md

- I added an intro to the section
This commit is contained in:
Mike Thomas 2022-07-22 13:26:24 +09:00 committed by GitHub
parent c37d924e78
commit 546543c361
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
handbook/sales.md
View file

@ -19,24 +19,26 @@ At times, our sales team will reach out to prospective customers before they com
- Be personable.
- Ask for the meeting with a proposed time.
## Principles for writing for the Sales team
## Sales team writing principles
### We want to abide by the following principles in our communications:
When writing for the Sales team, we want to abide by the following principles in our communications.
First, maintain naming conventions so people can expect what fields will look like when revisiting automations outside of Salesforce. This helps them avoid misunderstanding jargon and making mistakes that break automated integrations and cause business problems. One way we do this is by using sentence case where only the first word is capitalized (unless it’s a proper noun). See the below examples.
### Maintain naming conventions
Maintain naming conventions so people can expect what fields will look like when revisiting automations outside of Salesforce. This helps them avoid misunderstanding jargon and making mistakes that break automated integrations and cause business problems. One way we do this is by using sentence case where only the first word is capitalized (unless it’s a proper noun). See the below examples.
| Good job! ✅ | Don't do this. ❌ |
|:----------------------|:---------------------|
| Bad data | Bad Data
The second principle is to be explicit, which goes back to people understanding what they are reading and how to use terms for proper use of automations outside of Salesforce. In the case of acronyms, that means expanding and treating them as proper nouns. Note the template for including acronyms is in the first column below.
### Be explicit
Being explicit helps people to understand what they are reading and how to use terms for proper use of automations outside of Salesforce. In the case of acronyms, that means expanding and treating them as proper nouns. Note the template for including acronyms is in the first column below.
| Good job! ✅ | Don't do this. ❌ |
|:----------------------|:---------------------|
| Do Not Contact (DNC) | DNC
## Intro deck
Fleet's intro deck adds additional detail to our pitch. Find it in [Google Slides](https://docs.google.com/presentation/d/1sMCld6OPPG-LzJojmoSPxnOt17H-KYYfl5QFbBO29Fk/edit?usp=sharing).
@ -89,7 +91,6 @@ Directly Responsible Individuals (DRI) engage in the ritual(s) below at the freq
| TODO | TODO | TODO | TODO
| TODO | TODO | TODO | TODO
## Slack channels
This group maintains the following [Slack channels](https://fleetdm.com/handbook/company#group-slack-channels):