Set Up Connection Campaigns

Before diving into the details, let’s take a high-level tour of how a connection campaign works. The diagram pictured below shows the flow of a campaign.

Because the process ends with the creation of a connection request you may wonder, "Why not just create the connection request directly?" The answer is that we realize it may take days or weeks to process through the list. We don’t want the age of the connection requests to be skewed by the date the request was created, especially if it takes several days or weeks for a connector to be assigned. It might be perfectly reasonable for a request to be waiting for someone for several days. We want to be able to measure requests by age as a reflection of how efficiently connectors are working requests. This provides good accountability to the process.

Now that we’ve looked at the feature from a 30,000-foot view, let’s dive into each component in detail.

Connection Campaigns

We'll start with the Connection Campaigns page. This allows us to define as many campaigns as we’d like. You can find this list under People > Connections > Connections Configuration > Connection Campaigns.

As you can see, this lists the campaigns and provides a few metrics about each. These include:

• Active Requests: This is the number of active connection requests that are currently open.
• Pending Connections: This is the number of people still on the campaign list waiting to be moved to a connection request.

Selecting a campaign will take you to the Campaign Detail page.

Campaign Detail Page

This page is the control center for a campaign’s configuration. Below we'll walk through each section of the setup.

    Please contact {{ Person.NickName }} with a quick phone call.
    Here are the family members:
    {% for m in Family.Members %}
    * {{ m.Person.FullName }} - {{ m.GroupRole.Name }} 
    ({{ m.Person.ConnectionStatusValue.Value }}, {{ m.Person.RecordStatusValue.Value }})
    {% endfor %}