<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rss [<!ENTITY % HTMLlat1 PUBLIC "-//W3C//ENTITIES Latin 1 for XHTML//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent">]>
<rss version="2.0" xml:base="http://www.noaholiphant.com/dev">
<channel>
 <title>Noah Oliphant - CRM</title>
 <link>http://www.noaholiphant.com/dev/taxonomy/term/12/all</link>
 <description></description>
 <language>en</language>
<item>
 <title>Challenges of Constituent Relationship Management</title>
 <link>http://www.noaholiphant.com/dev/node/19</link>
 <description>&lt;p&gt;One of my roles at the American Cancer Society is to manage the tools our division use for Constituent Relationship Management (CRM).  I provide trainings, define business processes, and support the field in using our CRM tools.  This task has proven to be very difficult, with the biggest obstacles coming from the CRM domain in general.&lt;/p&gt;
&lt;p&gt;Everyone in my division practices Constituent Relationship Management.  They must, or they would not be successful in their jobs.  The question is whether they are performing their CRM tasks efficiently or would they be able to accomplish more if they were to use the tools available to them.&lt;/p&gt;
&lt;p&gt;A standard problem in the CRM domain is ‘User Adoption’.  I can speak from experience that this is the fundamental problem with all CRM tools.  Until the tools are able to integrate completely and seamlessly with mail and calendar applications, only the most sales driven professionals will use them.&lt;/p&gt;
</description>
 <category domain="http://www.noaholiphant.com/dev/taxonomy/term/12">CRM</category>
 <pubDate>Thu, 13 Apr 2006 12:18:20 -0600</pubDate>
</item>
</channel>
</rss>
