Leaders CRM: Do's and Don'ts: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
=== Location Fields === | |||
* 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". | ||
=== Email and Web Fields === | |||
* 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. | * 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. | * 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. | ||
=== Employment Data Fields === | |||
* 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. | * 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. | * 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. | ||
=== Notes === | |||
* Using uppercase characters like Résumé instead of Resume will limit matches in a text search for "resume" or "Résumé". Also, the search is currently case sensative, which is something that will be changed in future versions. | |||
[[Category:Leaders CRM]] | [[Category:Leaders CRM]] | ||
Revision as of 07:04, 31 January 2008
Location Fields
- 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".
Email and Web Fields
- 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.
Employment Data Fields
- 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.
Notes
- Using uppercase characters like Résumé instead of Resume will limit matches in a text search for "resume" or "Résumé". Also, the search is currently case sensative, which is something that will be changed in future versions.