The Contact Type mapping allows you to change the way your institution's contact types are categorized for reporting purposes in the Platform. You can map each contact type to one of the following options:
- Activity (Use this for any type that is not a "true" contact, such as administrative entries. Activities will display in relationship profile, but will not be considered when calculating the last time a prospect was contacted or when showing the number of contacts made by an officer)
- Event
- Letter/Email
- Other (Use this for types that are "true" contacts but do not fit into one of the other contact type categories)
- Phone
- Visit
Changes made to the contact type mapping may not reflect in the platform until the next time you nightly feed is processed.
The Edit Contact Type Mapping table shows all of the codes you have defined, even if the codes are not in use (these will have 0 records). The table also shows all codes that are in use, even if a code definition was not found (Your Description will show "No Description Found").TT
Please note we may have built custom logic around your data if this was requested or necessary for implementing your data feed. If so, the codes and descriptions shown here may not match exactly what is in you system. Please contact Reeher Support at support@reeher.net with any questions about the information presented here.
Click on the thumbnail below for a closer look!
Examples of where this shows up in the platform:
Click on the thumbnails below to expand the images. These are intended to show a few examples of where this data mapping affects the features in the platform. These examples are not an exhaustive list of all platform features impacted by this data mapping.
