Spell out:
- Who has what rights to the system; who can Create, Insert, Modify or Delete records, assuming your software supports all these functions? Forward this information to your system administrator to action.
- Decide on a procedure to check for any duplicates before creating a record. Depending on what 'de-duping' or 'data scrubbing' features your system has, this might require some simple searches before starting a new record.
- Do you allow abbreviations or acronyms? For example: IBM, or I.B.M, or International Business Machines Inc. or Incorporated and so on. A policy on ensuring consistency of input will help to avoid duplications in future.
- Are records going to be created in Upper and Lower case and when are CAPS acceptable?
- By when do you expect records, notes and so on to be created or updated? Same day, on return to the office?
- Check to see whether your Postal Services have specific requirements. Ensure your data meets these criteria.
- Is the primary address of clients to be created as a postal or a physical address?
- Make sure everyone checks spellings if they are unsure and do not trust spellchecker! When in doubt, ask the client - they'll respect that. Is it Clark with an 'e'; Shawn, Sean or Shaun? One certain way to get your mail binned is to spell someone's name incorrectly.
- Also confirm the kind of corporation e.g. LLC, Inc, PTY Ltd. and so on.
- Make rules for creating new profiles or User Definable Fields (UDF) (or whatever your specific CRM software calls them.) Place a lot of emphasis on this. Every time a new UDF is needed, it should first be approved. Otherwise duplicates will permeate your database e.g. Lead Source: Yellow Pages, YP, yelo pages.
- Ensure that email addresses are put in correctly. Basic but common mistake!
- Set up procedures, if not supported by your software, of how to create records from inbound emails.
- If applicable, are you going to use Mandatory/Forced fields?
|