Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MST/-7.0/no DST' instead in /home/dougyeag/public_html/joomla/libraries/joomla/utilities/date.php on line 56

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MST/-7.0/no DST' instead in /home/dougyeag/public_html/joomla/libraries/joomla/utilities/date.php on line 198
CRM: Customer is King
User Rating: / 1
PoorBest 
Written by Doug Yeager   

Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MST/-7.0/no DST' instead in /home/dougyeag/public_html/joomla/libraries/joomla/utilities/date.php on line 117

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MST/-7.0/no DST' instead in /home/dougyeag/public_html/joomla/libraries/joomla/utilities/date.php on line 245

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MST/-7.0/no DST' instead in /home/dougyeag/public_html/joomla/libraries/joomla/utilities/date.php on line 249

Warning: strftime() [function.strftime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MST/-7.0/no DST' instead in /home/dougyeag/public_html/joomla/libraries/joomla/utilities/date.php on line 250
Saturday, 12 July 2008 20:21

What to look for in a Customer Relationship Management (CRM) Solution?  The Customer is King - lose sight if this and your adoption of CRM will be hamstrung

Customer is King
 

Show them you know them..
Next generation engagement systems, delivered on-line, must remove barriers and enable the moments of passion when donors want to learn, to network, to give. Internet-enables philanthropy to tap the participatory, passion-driven and self-service attributes of the Web. This is an evolution of the philanthropic service model to meet high net worth donors where they are.
Future requirements include the ability to capture giving preferences, deliver timely giving opportunities in response to those preferences and provide information regarding the eventual impact of contributions using Web-based applications. “Show me you know me” technology and social networking tools will eventually connect tens of thousands of new donors on a timely basis with charitable options and stories of the impact they are creating with their giving.
Foundations are beginning to address this service model requirement by employing Customer Relationship Management capabilities. In so doing they are learning many valuable lessons, such as:
  • The bigger the project the more likely it is to fail.
  • Data exchange is a primary factor in design.
  • Targeted investments are more easily evaluated for ROI.
They have also learned that CRM is NOT a monolithic one-size-fits-all system. Yes, it includes base contact management functionality, but it also reaches out to deliver specialized functions:

Base Functions

  • Contact management
  • Relationship management (and mapping)
  • Activity tracking

Extended Functions

  • Workflow: pipeline, call routing, approvals
  • Development: wealth appending data, list management
  • Communications: e-Newsletter, email, market segments

Web Accessible Applications

  • Event Management
  • Membership & Volunteer Management
  • Advocacy
  • Grants Management
  • Direct Giving
  • Interface to Content Management
The expectation was that foundations would start with base functions and add-on from there. But foundations discovered that any system that required duplicate data entry was doomed, and so the lack of an interface to back office systems like FIMS or Foundation Power effectively froze out adoption (although it is expected to be unfrozen with the launch of the Atlas Data Bridge; see related story).
  • Early adopters of CRM have instead found a way to bring in some of the specialized CRM functions that are less dependent on data synchronization. Doing so solves a short term problem while promising integration with the rest of the platform as the data exchange becomes available. Here are some examples of how foundations are iteratively applying CRM functions to serve their business needs:
  • Online Donation: several foundations are using online giving facilities to streamline disaster response and broaden initiative fundraising efforts.
  • Wealth Appending: one foundation has acquired outside lists for its geographic area, and is using wealth appending tools to screen potential prospects for development and engagement.
  • Grant Processing: foundations are using online grant facilities to gather applications.
  • Inquiry Management: a foundation is in the process of deploying a CRM tool to route and track incoming calls.
  • Event Management: foundations are taking requests for events and event registration online.
The common denominator to all of these projects is that they run on top of a CRM system. None of the organizations are using the “core” contact management function, but anticipate moving to it within a year.
Best practices call for any large system to be implemented in a staggered manner, one step at a time. If CRM is in your future, and we know that contact management is still 3-6 months away (waiting on the data bridge), the question then becomes: what is your killer-app? What project could you bring online to start this ball rolling?
For more information, please contact Doug Yeager ( This e-mail address is being protected from spambots. You need JavaScript enabled to view it )
 

 


Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MST/-7.0/no DST' instead in /home/dougyeag/public_html/joomla/libraries/joomla/utilities/date.php on line 117

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MST/-7.0/no DST' instead in /home/dougyeag/public_html/joomla/libraries/joomla/utilities/date.php on line 245

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MST/-7.0/no DST' instead in /home/dougyeag/public_html/joomla/libraries/joomla/utilities/date.php on line 249

Warning: strftime() [function.strftime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MST/-7.0/no DST' instead in /home/dougyeag/public_html/joomla/libraries/joomla/utilities/date.php on line 250
Last Updated on Thursday, 30 April 2009 20:52
 

Who's Online

We have 1 guest online

Help Pay for this thing:

Creative Commons License
Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License
RocketTheme Joomla Templates