Rules vs Campaigns – The BizConnector Approach

Campaigns as incorporated in Salesforce and other applications implement the traditional model, in which leads and contacts are explicitly added to a named campaign.

This enables these leads and contacts – called members in Salesforce – to be tracked and sent emails according to the strategy and objectives of a specific campaign.

So members have to be explicitly added to a campaign in order to be part of that campaign. And if there is more than one campaign, this has to be done separately for each campaign.

The BizConnector model is very different. Instead of incorporating the notion of campaigns in which you have to specifically add members to campaigns, BizConnector has rules which ‘discover’ leads naturally and automatically when they match rule conditions.

There is a natural conflict in Campaigns vs Rules. Without BizConnector, the campaign drives how you decide what to do about a lead. In BizConnector, rules take over this role, and rules are much more dynamic in nature.

So, simply by the match of rule conditions with the field values in a lead or contact, a rule can ‘fire’ on that lead or contact. In this way a relationship is created between the rule and a lead or contact – individually. This relationship is dynamic – it starts when the match is recognized and the rule fires, and it stops when the rule conditions no longer apply to the lead or contact or when the rule actions have run their course.

This dynamic behavior is much more in tune with the needs of the market today. Market conditions change daily, if not hourly or by the minute. This is surely true for your industry. BizConnector rules are sensitive to change – in (near) real time – record by individual record. It is this flexibility and dynamism that makes BizConnector rules achieve your marketing, lead nurturing, and workflow objectives.

 

 

A Little BizConnector History

At this juncture, with the start of a new year and the relaunch of this website, it may be useful to take a look at the history of BizConnector since its appearance in 2005, to relate it to its offshoot ‘Lead Follow-Up’ on Salesforce.com, and in a future post, to describe its expected evolution and roadmap.

BizConnector started off as ‘a web-based email communication tool that enables ‘contextual interaction’ with recipients, addressing the needs of companies seeking to cultivate their customers and grow their businesses by using the latest web technologies to manage marketing campaigns in an intelligent way’. Essentially, it was a mass-emailer with interactive ability – a trail-blazer in many ways.

The original BizConnector had a place for business rules, but it was the development of Lead Follow-Up – a marketing automation app on Salesforce AppExchange – that featured real-time business rules as its core architectural foundation. As the name implies, Lead Follow-Up was built – with a more restricted vision than the original BizConnector – to address the needs of marketers to nurture leads and prospects. Integrated deeply with Salesforce.com through the API, its basic modus operandi is to use events in Salesforce data to trigger ‘drip marketing’ campaigns and workflows. It was expanded to attach not only to Leads, but to Contacts, Accounts, Opportunities, Tasks, Events, and Cases. And it incorporates features such as landing pages and a closed-loop feedback mechanism that makes it a powerful tool, despite its apparent simplicity.

BizConnector can now be described, at its core, as a (Near) Real-Time Business Rules Engine for small business. With the development of ‘channels’ that can be used for business rule triggers and actions, BizConnector now has the ability to connect with external systems and applications, be triggered by events outside Salesforce, and pull content from multiple sources. Channels are open-ended, and can be developed by third parties. And the forthcoming BizConnector API, to be announced, will provide a platform for new and exciting applications.

Please visit here again for more information about the BizConnector roadmap.