You are here
RedHen CRM Part 1, Keeping all your eggs in one Drupal basket RedHen CRM Part 2: Welcome To The Hen House
Introducing RedHen CRM
The Drupal community has long aspired for native CRM functionality for many years. Unfortunately, solutions to this problem in older releases of Drupal were less than perfect - usually relying on the node system to manage contact data. Of course, the node system was designed for managing content, so these node-based CRM solutions required lots of extra code and duct tape to keep content and contacts separated.
Fortunately, the arrival of the entity framework in Drupal 7.x core has opened the door to the development of more robust CRM solutions built natively in Drupal. So, after a year of scheming and over 700 hours of very intense development, ThinkShout is proud to announce the Alpha release of RedHen CRM.
Why Does Native CRM Matter?
CiviCRM is a mature open source CRM solution that integrates with Drupal, so why not just use that? Drupal also integrates well with many 3rd-party SaaS solutions, such as Salesforce, why reinvent the wheel?
There are many benefits to integrating your Drupal site with a 3rd-party CRM solution. But there are many missed opportunities and drawbacks to these integrations as well. The most obvious benefits to native CRM in Drupal include:
- A more seamless user experience for site visitors registering for events, making donations/payments, or engaging in other website transactions.
- The opportunity to leverage Drupal's growing suite of mobile and responsive tools and themes for CRM interfaces.
- The ability to expose CRM data as content, and/or the ability to display aggregate CRM data on your site.
- Increased opportunities to integrate CRM data with Drupal contributed tools - such as data visualization tools, geo-mapping tools, and more.
- Decreased staff training costs - because staff doesn't need to get trained on multiple platforms.
- Potential reductions in technical risk - because all your tools rely on a single, Drupal framework.
- Potential reductions in hosting and IT costs.
- The ability to do complex engagement scoring or engagement analytics (more on this later).
- And probably most important - the ability to fully customize your CRM solution.
Native CRM And (Not Versus) Enterprise CRM
One last point before diving into the guts of RedHen CRM:
While we think that it's possible to build very robust, large-scale CRM solutions natively in Drupal, our goal in releasing RedHen is not to compete with the enterprise CRM market. Platforms like Salesforce will inevitably out scale what we can build with Drupal.
That said, enterprise CRM solutions are often overkill for small to mid-sized organizations. Moreover, even if your organization does need an enterprise CRM solution, we see RedHen as a natural integration point between your website and such a system.
With the right Drupal development partner, tools such as RedHen open the door to the creation of highly innovative "front end" CRM tools. We anticipate that collecting and displaying data in RedHen (and Drupal) will often be much more affordable and nimble than trying to develop comparable features upon larger, more cumbersome enterprise packages.
What Can You Do With RedHen CRM?
RedHen CRM has been largely designed around the association management (AMS) needs of membership organizations. That said, the RedHen framework is flexible and can be leveraged to develop a wide range of CRM solutions. For example, RedHen could be used as a light weight sales pipeline management tool for small to mid-size businesses.
Getting Started
RedHen CRM is similar to Drupal Commerce in its modular structure. As with Drupal Commerce, the core RedHen modules that can be downloaded on the Drupal.org project pagewon't provide you with a working CRM right out of the box. They require configuration. In the future, ThinkShout is likely to release RedHen "Features" or "Apps" that provide prepackaged CRM solutions for different use cases.
In the short term, if you would like to explore RedHen CRM, we would encourage you to check out our demonstration RedHen CRM installation profile. This install profile will build out a simple example of how RedHen could be leveraged to support the CRM needs of a fictional "pet shelter" organization.
Project Structure
RedHen CRM relies heavily on custom Drupal entity types and bundles. The Entity API module is leveraged to do most of the heavy lifting for these custom entities. The Relation module is leveraged to manage connections between these custom entity bundles. The core RedHen module provides shared APIs, although the majority of RedHen features are broken out into separate sub-modules that ship with the main module. As with Drupal Commerce, we will continue to include key sub-modules with the main module code base. However, we anticipate that an ecosystem of plug-in modules will soon be available to extend the core feature set.
Basic Concepts and Features
RedHen CRM defines two main entity types: Contacts and Organizations. Site administrators can then create different entity bundles for each of these types. Each bundle can then befielded.
Connections can then be made between contacts, as well as between contacts and organizations. Connections are managed as custom entity bundles as well, based upon the relation entity type defined by the Relation module. As such, these connections can be fielded as well. In other words, you can create a relationship, or connection, between contacts and organizations that include field data about the relationship. Potential connection fields might include "job title" or "job start date."
Memberships are another custom entity type defined by the "RedHen Membership" module. Both contacts and organizations can be associated with memberships. RedHen's membership management features are very flexible and feature rich. Memberships can be associated with the management of Drupal user roles to provide website access based upon individual and organizational membership status.
Optionally, contact entities can be associated with Drupal user accounts. Currently, these connections are managed from the contact entity edit screen. Contacts can be associated with existing Drupal user accounts, or a new Drupal user account can be created from the contact entity edit form.
Notes is another custom entity type and bundle provided by the "RedHen Notes" sub-module. Notes provide a site administrator a simple tool for capturing tagged notes about contacts and organizations. As a custom entity bundle, notes are fieldable as well.
The Notes module also integrates with the "RedHen engagement scoring" sub-module. Engagement scores allow a site administrator to track and score various types of interactions with contact entities.
Finally, RedHen CRM ships with a "RedHen groups" sub-module that allows you to groupifyRedHen organizations. Groupified organizations function similarly to Organic Groups, in that they provide a simple container for managing private node content associated with each organization.
Extending RedHen CRM with Views and Rules Integration
The RedHen CRM framework does not require Views. However, because RedHen is built upon Entity API, you can easily extend RedHen to work with Views and Rules. With Views, you can customize your instance of RedHen CRM to create personalized reports of contact, organization, membership and/or engagement scoring data. With Views plugins such as Views Bulk Operations and Views Data Export, you can further extend RedHen with bulk editing and export tools.
For More Information
Complete RedHen site administration docs will be coming soon. You can also check out the README files contained with each RedHen module. For technical issues, please use the D.O. issue queue. For community support and to learn about RedHen usage, please consider joining the RedHen Drupal group and follow us on Twitter @RedHen_CRM.
Next Up: A RedHen CRM Feature Deep-Dive
For a detailed look at RedHen CRM, check out Part 2 of this article.
介绍 RedHen CRM
Drupal 社区很多年，都为本机 CRM 功能渴望。不幸的是，在 Drupal 的旧版本中这个问题解决方案较完美-通常依赖于节点系统来管理联系人数据。当然，用于管理内容，所以这些基于节点的 CRM 解决方案所需的大量额外代码和胶带保持内容和联系人分隔设计了节点系统。
幸运的是，实体框架在 Drupal 7.x 版核心的到来已经打开了通向更强健的 CRM 解决方案本身建立在 Drupal 中发展。因此，经过一年的策划和超过 700 个小时的激烈发展，ThinkShout 是自豪地宣布阿尔法发布的RedHen CRM.
本机的 CRM 为什么重要?
CiviCRM是一个成熟的开源与 Drupal 集成在一起的 CRM 解决方案，那么为什么不能用的吗?Drupal 还集成了与许多第三方 SaaS 解决方案，如 Salesforce 很好，为什么重新发明轮子呢?
有很多好处到 Drupal 站点结合第三方的 CRM 解决方案。但有很多错过的机会和这些集成以及缺点。本机的 CRM 在 Drupal 中最明显的好处包括:
- 站点访问者注册为事件、 捐赠/付款，或从事其他网站交易更加无缝的用户体验。
- 有机会利用 Drupal 的套不断增长的移动和反应灵敏的工具和 CRM 接口的主题。
- 能够公开的内容，作为 CRM 数据和/或您的网站上显示聚合 CRM 数据的能力。
- 工具-如数据可视化工具、 地理制图工具和更多，更多的机会与 Drupal 集成 CRM 数据作出了贡献。
- 减少员工的培训费用-因为工作人员不需要在多个平台上得到训练。
- 技术风险-潜在减少因为你所有的工具都依赖于一个单一的 Drupal 的框架。
- 主机，它的潜在减少成本。
- 能够做复杂的订婚得分或接触分析(稍后详细介绍)。
- 也可能是最重要的-完全自定义您的 CRM 解决方案的能力。
本机的 CRM 和(不与)企业 CRM
前潜入 RedHen CRM 的胆量的最后一点:
虽然我们认为它是可能以构建非常健壮，大规模的 CRM 解决方案，以本机方式在 Drupal 中，我们在释放 RedHen 的目标并不是与企业 CRM 市场竞争。平台像 Salesforce 必然淘汰规模我们可以建立与 Drupal。
也就是说，企业 CRM 解决方案往往矫枉过正的小型到中型组织。此外，即使您的组织需要企业的 CRM 解决方案，我们看到 RedHen 作为一个自然的集成点之间您的网站和这样一个系统。
与右 Drupal 开发伙伴，工具，如 RedHen 的极富创新性的"前端"CRM 工具创造开门。我们预计，收集和显示数据在 RedHen (和 Drupal) 往往将更多负担得起和比试图开发时更大、 更笨重的企业软件包功能相当灵活。
与 RedHen CRM，你可以做什么?
RedHen CRM 很大程度上围绕会员组织的协会管理(AMS) 需要。尽管如此，RedHen 框架是灵活的可以利用开发的宽范围的 CRM 解决方案。例如，RedHen 可以用作重量轻销售管道管理工具为小到中等规模的业务。
入门
RedHen CRM 是类似于Drupal 商务中的模块化结构。与 Drupal 商务核心 RedHen 模块，可以下载Drupal.org 项目页面上不会为您提供开箱工作 CRM。他们需要的配置。在将来，ThinkShout 是容易释放 RedHen"功能"或"应用程序"，为不同的用例提供预先包装的 CRM 解决方案。
在短期内，如果你想要探讨 RedHen CRM，我们会鼓励你查阅我们的示范 RedHen CRM 安装配置文件。此安装配置文件将打造出一个简单的例子，如何可以利用 RedHen 支持 CRM 的一个虚构的"宠物收容所"组织的需求。
项目结构
RedHen CRM 严重依赖于 Drupal 的自定义实体类型和包。利用实体 API模块做最繁重的工作为这些自定义的实体。利用关系模块，以管理这些自定义实体捆绑包之间的连接。核心 RedHen 模块提供共享的 Api，尽管大多数 RedHen 功能分为船舶与主要功能模块的单独子模块。与 Drupal 商务，我们将继续包括与主要功能模块的代码库的关键子模块。不过，我们预计很快将可用来扩展的核心功能集生态系统的插件模块。
基本概念和特征
RedHen CRM 定义两个主要实体类型: 联系人和组织。网站管理员然后可以为每种类型创建不同的实体束。然后可以在每个捆绑包派出了。
之间的联系，以及之间的联系和组织，然后可以进行连接。连接管理作为自定义实体捆绑，以及根据关系模块所定义的关系的实体类型。因此，这些连接可以派出以及了。换句话说，你可以创建一个关系或联系和组织，包括有关关系的字段数据之间的连接。潜在的连接字段可能包括"职位名称"或"工作开始日期"。
成员资格是由"RedHen 会员"模块定义的另一个自定义的实体类型。联系人和组织可以与成员相关联。RedHen 的会员管理功能非常灵活，功能丰富。成员资格可以与管理 Drupal 用户角色提供基于个人和组织成员资格的网站访问关联。
(可选) 联系实体可以与 Drupal 用户帐户相关联。目前，这些连接是从联系人实体编辑屏幕进行管理。联系人可以是与现有的 Drupal 用户帐户相关联或从联系人实体编辑窗体可以创建一个新的 Drupal 用户帐户。
注意到是另一个自定义实体类型和包提供的"RedHen 笔记"子模块。注意到为捕捉带标记的笔记，关于联系人和组织提供网站管理员一个简单的工具。作为一个自定义实体包，笔记也 fieldable。
注意到模块还集成了"RedHen 参与评分"的子模块。敬业度的分值允许站点管理员跟踪并得分各种类型的互动与联系实体。
最后，RedHen CRM 附带允许您向groupify RedHen 组织"RedHen 组"子模块。Groupified 组织功能类似于有机基团，在这他们为管理与每个组织相关联的私有节点内容提供一个简单的容器。
扩展视图与规则集成 RedHen CRM
RedHen CRM 框架并不需要的意见。然而，因为 RedHen 建立在实体 API，您可以轻松扩展 RedHen 意见与规则而努力。与视图，您可以自定义你的 RedHen CRM 打造个性化的报表的联络、 组织、 会员和/或参与评分数据的实例。与意见意见批量操作和视图数据导出插件，您可以进一步扩展 RedHen 批量编辑和导出工具。
更多的信息
完整的 RedHen 网站管理文档将会很快。你还可以签出，每个 RedHen 模块包含的自述文件。对于技术问题，请使用D.O.问题队列。社会支持和要了解 RedHen 的使用，请考虑加入RedHen Drupal 组，按照我们上 Twitter @RedHen_CRM.
接下来: RedHen CRM 功能深入了解
详细看看 RedHen CRM，请查阅这篇文章的部分 2 。
来自 http://thinkshout.com/blog/2012/06/sean/redhen-crm-part-1/
In Part 1 of this article we explored the major benefits and broad concepts of RedHen CRM. In this article, we will take a detailed look at RedHen's current feature set - as demonstrated in oursample RedHen installation profile.
In this RedHen CRM demonstration, we will show how the framework could be leveraged to build an association management system (AMS) supporting a fictional organization: The National Association of Pet Shelters.
In this example, we have created two different types (or in Drupal speak "entity bundles") of individual contact records - one for shelter staff and another for volunteers, each with its own unique set of fields. Similarly, we have created two different types of organization records - one for the shelters themselves and another for foundations that support the work of these organizations. We can then leverage RedHen to show the connections between these contact and organization records, as well as to manage both individual and organizational memberships within our fictional association.
Working with Contacts
Configuring Contact Entity Bundles
RedHen CRM defines a custom entity type for "Contacts." As mentioned above, RedHen CRM allows site administrators to create their own "contact bundles" - each with its own unique sets of fields:
Below is a listing of the fields that have been added to our demonstration CRM's "volunteer" contact bundle:
The "RedHen Contact Email" field is a new field type defined by RedHen CRM to provide additional options for managing the unique email communication preferences of your RedHen contacts. The "Availability" field provides an example of how we can extend contact records to include additional, customized field data about our contacts.
Filtering Contacts
Once we've configured our content entity bundles, we can view and search our contacts across various fields and properties:
Notice that when we change our "contact type" filter (or, in Drupal speak, when we filter on "contact entity bundle"), RedHen CRM's contact listing automatically pulls in the fields available as filter options for the selected bundle:
Working with Individual Contact Entities
The default contact entity display:
Editing fields and properties on a contact entity (In this case, a staff contact entity):
Connecting Content Entities with Drupal User Accounts
Optionally, you can choose to associate contact entities with Drupal user accounts on your site. You can either choose to connect the contact entity with an existing user account:
Or, you can create a new Drupal user account for the contact entity from within the RedHen interface:
Within the next month, we will be extending this feature to allow Drupal users to edit their own content information via this linkage. But for now, this feature is primarily leveraged for managing access control and Drupal user roles via our membership management tools, which we describe shortly.
Working with Organizations
Organizations work similarly to Contacts. RedHen defines an entity type for organizations - which can be extended by a site administrator as custom organization entity bundles.
Connecting Contacts and Organizations
RedHen CRM leverages the Relation module to allow for different types of relationships (orconnections in RedHen CRM speak) between contacts - as well as between contacts and organizations.
As with all the other entity types/bundles that are part of RedHen CRM, these relationships arefieldable:
This means that you can add fields to your relationships to track metadata about the connections between RedHen entities.
Managing Primary Contacts for Your Organizations
When managing connections between contacts and organizations, site administrators can also determine the primary contact for an organization entity. See the "Primary Contact" link on the right-hand side of the screenshot below:
The primary contact is a dynamic property for organization entities, and has been exposed to Views and Rules.
Managing Memberships
Our clients' reoccurring need for a flexible and customizable membership management solution was one of our primary motivations in developing RedHen. Selling Drupal user roles with Drupal Commerce, or managing the expirations of Drupal user roles with contributed modules such as Role Expire is simply not a robust enough solution for large membership organizations with complex business rules around membership-based services.
Individual vs. Organizational Memberships
With this in mind, RedHen CRM allows you to create different types of memberships, which can be applied to both content entities organization entities. These membership types are, of course, entity bundles, so again - they are fieldable.
Assigning Drupal User Roles Via Memberships
As mentioned above, Drupal user accounts can be associated with RedHen contacts. Once these connections are made, the assignment of an active membership can be leveraged to provide a user account with a Drupal user role.
When a RedHen membership that is associated with a Drupal user role is assigned to a RedHen Organization - this role is applied to all Drupal user accounts associated with contacts related to that RedHen organization.
Let me repeat this point, because it is truly one of the most unique features of RedHen CRM:
With RedHen CRM, you can manage Drupal user roles via organizational memberships.
Role-based Membership Benefits
It goes without saying that Drupal's role-based permission and access control system is one of its great strengths. Combining the Drupal user role framework with CRM functionality represents on of the most important value propositions of RedHen CRM and, more generally speaking, native Drupal CRM tools.
Leveraging RedHen CRM with Drupal Commerce, you could use these membership management tools to provide discounts on e-commerce transactions. Leveraging a wide variety of contributed access control modules, could you could also build premium content libraries. The "Association Management Solution" (AMS) opportunities are endless.
Capturing Notes on Contacts and Organizations
Notes can be added to both contact and organization entities. As an entity bundle, notes can be extended with fields.
In the case of our RedHen Demo CRM, we have extended the notes bundle with a taxonomy reference field for the "type" of note that is being recorded. When viewing note history, these notes can then be filtered by this type taxonomy.
Engagement Scoring
In the notes screenshot above, you'll also notice a dropdown option for Engagement Score.
Engagement scoring (often referred to as "engagement analytics" or "engagement metrics") is a relatively new concept in measuring the interactions of web site visitors. Web analytics packages such as Google Analytics generally focus on measuring quantitative analytics - or the number of page visits and clicks. Engagement scoring focuses on measuring the quality of these interactions by weighting the value of different types of interactions between site visitors and your website. For example, sharing an article from your website to a social network might be worth "5 engagement points", commenting on a blog post might be worth "10 points."
The RedHen Engagement module provides an API and framework for tracking this type of engagement. The module also integrates with the "RedHen Notes" module, so that offline interactions with RedHen Contacts can also be tracked and scored. To learn more about engagement scoring in RedHen, check out this blog post.
Tracking Event Registrations
RedHen CRM integrates closely with the Entity Registrations module - which our ThinkShout geeks also maintain. As shown in the screenshot below, the Entity Registrations module allows you to manage event registrations as entities.
When enabled, the RedHen Registration module adds an additional tab to the contact entity screen called "Registrations." There, both authenticated and anonymous event registrations will be listed for each contact, based upon a matching email address.
Note: In the future, we plan to extend this module such that new registrations associated with email addresses *not** found in RedHen CRM will trigger the creation of new contact entities.*
RedHen Organizations as "Groups"
The RedHen Organization Groups module allows you to groupify organization entity bundles.
This module provides functionality similar to Organic Groups. A groupified organization can have node content associated with it. Optionally, this content can be made private, and therefore only viewable to Drupal user accounts associated with RedHen contact entities which are in turn associated with a specific RedHen organization entity.
In the screenshot below, you can see how a node can be added to a groupified RedHen organization:
Then, when looking at a RedHen organization entity, you can see all associated group content:
So, why not just use Organic Groups?
The description above begs the question: Why not just use OG? In developing this feature, we considered leveraging Organic Groups. However, the relationships between Drupal user records, contacts and organizations were too complex to cleanly build this feature on top of both RedHen and Organic Groups. That said, much of the architecture of this module is based upon design patterns from Organic Groups.
在这篇文章的第一部分 1我们探索的主要优点和广泛的RedHen CRM的概念。在本文中，我们将详细的看看 RedHen 的当前功能集-我们的RedHen 安装配置文件示例中所示.
在 RedHen CRM 在该例中，我们将展示如何可以利用框架构建支持一个虚构的组织协会管理系统 (AMS):国家的协会宠物收容所.
在此示例中，我们都会产生两种不同类型 (或在 Drupal 中讲"实体束") 的个人的联系人记录-一个收容所工作人员和志愿者，每一个都有它自己独特的另一种设置的字段。同样，我们已创建两个不同类型的组织记录-一个庇护所本身，另一个用于支持这些组织的工作的基础。然后，我们可以利用 RedHen 来显示这些联系和组织的记录，之间的连接，以及管理我们虚构的协会内的个人和组织成员身份。
使用联系人
配置联系人实体捆绑
RedHen CRM 定义一个自定义的实体类型为"联系人"。如上文所述，RedHen CRM 允许站点管理员创建自己"接触束"-每个都有其自己唯一的字段集:
下面是已添加到我们示范 CRM"志愿者"接触捆绑的字段的列表:
"RedHen 联系人电子邮件"字段是由 RedHen CRM 提供用于管理您的 RedHen 联系人的唯一的电子邮件通讯首选项的附加选项定义新的字段类型。"可用性"字段提供的如何，我们可以扩展包括有关我们接触更多的自定义字段数据的联系人记录的示例。
过滤联系人
一旦我们内容实体束，我们已经配置了，我们可以查看和搜索我们的联系人跨各种字段和属性:
请注意当我们改变我们"联系类型"筛选器 (或，在 Drupal 中说话，当我们对"联系人实体捆绑"进行筛选)，RedHen CRM 联系人列表自动拉在可用作为所选包筛选器选项字段:
工作与个人联系实体
默认联系人实体显示:
编辑字段和联系人实体 (在这种情况下，一个工作人员接触的实体) 的属性:
连接内容实体与 Drupal 用户帐户
(可选) 您可以选择将联系人实体与 Drupal 用户帐户对您的站点相关联。你也可以选择连接的联系人的实体与现有的用户帐户:
或者，您可以创建联系人实体从 RedHen 接口内新的 Drupal 用户帐户:
在下个月，我们将扩展此功能，以便允许 Drupal 用户编辑自己内容的信息，通过这种联系。但现在，这项功能主要杠杆管理访问控制和通过我们的会员管理工具，我们描述不久的 Drupal 用户角色。
组织的合作
组织工作同样到联系人。RedHen 定义的实体类型的组织 — — 可以作为自定义组织实体捆绑扩展由网站管理员。
连接的联系人和组织
RedHen CRM 利用关系模块以允许不同类型的关系 (或连接在 RedHen CRM 发言) 以及联系人和组织之间联系-。
作为与所有其他实体类型/包 RedHen CRM 的一部分，这些关系都是fieldable:
这意味着可以将字段添加到你的人际关系来跟踪 RedHen 实体之间的连接有关的元数据。
您的组织的的管理主要联系人
当管理连接之间联系、 组织和站点管理员还可以确定一个组织实体的主要联系人。在右手边的下面的截图上看到"主要联系人"链接:
主要联系人是一个动态的属性对于组织的实体，和暴露的意见和规则。
管理成员身份
我们客户的重复出现需要一个灵活且可自定义的会员管理解决方案是我们在发展 RedHen 的主要动机之一。销售与 Drupal 商务，Drupal 用户角色或管理到期的 Drupal 用户角色与贡献的模块，如角色到期不只是一个足够健壮的解决方案，为大型会员组织与周围会员制服务的复杂的业务规则。
个人与组织的成员身份
为此，RedHen CRM 允许您创建不同类型的成员，可以适用于这两个内容实体组织实体。当然，这些会员类型是实体束，再一次-他们是 fieldable。
将通过会员的 Drupal 用户角色分配
如上文所述，Drupal 用户帐户可以是与 RedHen 联系人相关联。一旦进行这些连接，则可以利用的活跃会员资格转让与 Drupal 用户角色提供一个用户帐户。
当与 Drupal 用户角色相关联的 RedHen 成员分配到一个 RedHen 组织-这个角色被应用于与该 RedHen 组织相关的联系人关联的所有 Drupal 用户帐户。
让我重复这一点，因为它是真正的 RedHen CRM 最独特的特征之一:
与 RedHen CRM，您可以管理 Drupal 用户角色通过组织成员身份。
基于角色的会员优惠
不用说，Drupal 的基于角色的权限和访问控制系统是其最大的优点之一。Drupal 用户角色框架结合 CRM 功能表示的 RedHen CRM 和更多一般来说，本机 Drupal CRM 工具最重要的价值主张。
利用 RedHen CRM 与 Drupal 商务，您可以使用这些会员管理工具对电子商务交易提供折扣。利用种类繁多的贡献的访问控制模块，可以你也可以建立优质内容库。"协会管理解决方案"(AMS) 机会是无穷无尽的。
获取联系人和组织笔记
可以将注释添加到联系人和组织实体。作为实体包，笔记可以扩展字段。
在我们的 RedHen 演示 CRM，我们有延长分类参考字段"类型"的注意，正在录制笔记束。当查看注释历史，这些笔记然后可以按此类型分类进行筛选。
参与评分
在上面的笔记截图，你还会注意到一个下拉列表中选择参与评分.
参与评分(通常称为"参与分析"或"参与指标") 是一个相对较新的概念，在测量 web 站点访问者的相互作用。如谷歌分析的 web 分析软件包一般都集中于测量的量化分析 — — 或页面访问数和点击。参与评分重点在于测量质量的这些交互的加权值的不同类型的网站访问者和网站之间的交互。例如，分享到社交网络从您的网站的一篇文章可能值得"5 接触点"，在博客上发表评论后可能值得"10 点"。
RedHen 参与模块为跟踪这种类型的参与提供了一个 API 和框架。模块还结合"RedHen 笔记"模块，以便脱机和 RedHen 联系人的交互也可以跟踪并得分。学会更多关于订婚得分在 RedHen，查阅此博客文章.
跟踪事件注册
RedHen CRM 与实体注册模块-我们 ThinkShout 极客们也保持紧密集成。下面的屏幕快照所示，实体注册模块允许您管理作为实体的事件注册。
启用时，RedHen 注册模块会将一个附加选项卡添加到联系人实体屏幕称为"登记"。在那里，既经过身份验证和匿名事件注册将列出为每个联系人，根据匹配的电子邮件地址。
注意: 在将来，我们计划将此模块，使新注册关联的电子邮件地址 *不 * * 发现在 RedHen CRM 将触发创建新联系人 entities.*
RedHen 组织作为"组"
RedHen 组织团体模块允许您对groupify的组织实体束。
此模块提供类似于有机基团的功能。Groupified 的组织可以有与之关联的节点内容。或者，此内容可以是私有的并与 RedHen 联系实体这是反过来与特定的 RedHen 组织实体因此只可查看到 Drupal 用户帐户相关联。
在下面的屏幕快照，您可以看到如何可以将节点添加到 groupified 的 RedHen 组织:
然后，当看着 RedHen 组织实体，您可以看到相关联的组的所有内容:
那么，为什么不只是使用有机群体?
以上的描述引出了一个问题: 为什么不能用 OG?在开发这个功能，我们认为利用有机基团。然而，Drupal 用户记录、 联系人和组织之间的关系太过复杂，干净利落地建立此功能在 RedHen 和有机基团。这就是说，此模块的体系结构基于设计模式从有机基团。
下一个是什么?
ThinkShout 今年夏天将推出 RedHen CRM 上的我们第一次客户端站点。我们目前正努力稳定的 1.0 版的 RedHen-同时探索新功能和工具。
我们很感兴趣不断探索:
- Drupal 商务更深地融入。
- CRM 数据可视化-最明显的是地理位置和组成的数据，以及谷歌图表可视化的订婚得分数据映射。
- 批量导入工具，以及迁移 2.x 一体化。
- Apache Solr 集成。
- 更好的 HTML5 和 RedHen CRM 接口的响应主题的发展。
我们希望，社会将继续与我们合作，使 RedHen CRM 领先的协会管理解决方案。问题在队列中，并在您附近的 Drupal 阵营，我们会看到你!
来自 http://thinkshout.com/blog/2012/06/sean/redhen-crm-part-2/