Leaders CRM: Do's and Don'ts: Difference between revisions
Jump to navigation
Jump to search
New page: * Don't enter things like "Lincoln-move to" or "Omaha or Lincoln" in the city field. Try to keep city names consistant. Typing "St Petersburg" for one record and "St. Petersburg" for ano... |
mNo edit summary |
||
| Line 1: | Line 1: | ||
* Don't enter things like "Lincoln-move to" or "Omaha or Lincoln" in the city field. Try to keep city names consistant. Typing "St Petersburg" for one record and "St. Petersburg" for another (with period) will cause problems in using the search and match functions. "Nebraska City" versus "NE City". | * Don't enter things like "Lincoln-move to" or "Omaha or Lincoln" in the city field. Try to keep city names consistant. Typing "St Petersburg" for one record and "St. Petersburg" for another (with period) will cause problems in using the search and match functions. "Nebraska City" versus "NE City". | ||
* Enter email addresses correctly. Do not enter things like "work:email@address.com" or " | * Enter email addresses correctly. Do not enter things like "work:email@address.com" or "nxxaub@yahoo.com - wife nancy's email". Notes do not belong in the email field. | ||
* Do not put notes or email addresses in the web site field. Notes belong in | * Do not put notes or email addresses in the web site field. Notes belong in the notes field, and any extra contact information that will not fit into the main fields can also go into the notes or as a primary note. | ||
the notes field, and any extra contact information that will not fit into the | |||
main fields can also go into the notes or as a primary note. | |||
* For Title/Position try to limit the title or position names. If something already exists that is close, use it rather than creating a specific unique title all of the time. This speeds up database queries and searches. Be | * For Title/Position try to limit the title or position names. If something already exists that is close, use it rather than creating a specific unique title all of the time. This speeds up database queries and searches. Be consistant in using acronyms or abbreviations. Check to make sure that a title might already exist not abbreviated before entering in an abbreviated version and visa versa. | ||
consistant in using acronyms or abbreviations. Check to make sure that a title might already exist not abbreviated before entering in an abbreviated version and visa versa. | |||
* Don't rate the skill level or put comments in the Title/Position. A correct entry looks like "Network Administrator". A problematic entry example might be "network admin - good", "network admin - telecom guy", or "network admin - | * Don't rate the skill level or put comments in the Title/Position. A correct entry looks like "Network Administrator". A problematic entry example might be "network admin - good", "network admin - telecom guy", or "network admin - top secret clearance." Those additional comments belong in the notes. Using slang like "Network techy" is also not recommended. | ||
top secret clearance." Those additional comments belong in the notes. Using slang like "Network techy" is also not recommended. | |||
[[Category:Leaders CRM]] | [[Category:Leaders CRM]] | ||
Revision as of 22:10, 30 January 2008
- Don't enter things like "Lincoln-move to" or "Omaha or Lincoln" in the city field. Try to keep city names consistant. Typing "St Petersburg" for one record and "St. Petersburg" for another (with period) will cause problems in using the search and match functions. "Nebraska City" versus "NE City".
- Enter email addresses correctly. Do not enter things like "work:email@address.com" or "nxxaub@yahoo.com - wife nancy's email". Notes do not belong in the email field.
- Do not put notes or email addresses in the web site field. Notes belong in the notes field, and any extra contact information that will not fit into the main fields can also go into the notes or as a primary note.
- For Title/Position try to limit the title or position names. If something already exists that is close, use it rather than creating a specific unique title all of the time. This speeds up database queries and searches. Be consistant in using acronyms or abbreviations. Check to make sure that a title might already exist not abbreviated before entering in an abbreviated version and visa versa.
- Don't rate the skill level or put comments in the Title/Position. A correct entry looks like "Network Administrator". A problematic entry example might be "network admin - good", "network admin - telecom guy", or "network admin - top secret clearance." Those additional comments belong in the notes. Using slang like "Network techy" is also not recommended.