KW Command and Brivity
If you're new to PieSync, this guide will you get started with the essentials.
PieSync will sync the contacts of Brivity with KW Command's Contacts database.
When you sync Command with Brivity, you can customize the following four elements to your sync.
- Sync direction
- Connection rules
- Connection settings
- Field mappings
There is no one typical use case, no one best practice that can be documented to sync Command and Brivity. We'll provide various different tips, rules, and field mappings for you to draw inspiration from. You don't have to use them all!
Start by choosing the direction of your sync. You can consider three different settings.
- Most agents opt for a two-way sync, allowing records to be modified by PieSync in either system. This is the setup we see most commonly as it would enable contacts to move and be modified through Command into Brivity as well as the other way round.
- You could choose for a strict one-way sync from Brivity into Command. You don't want Command to be touching your Brivity ever.
- Of course, there's the opposite way too. Through PieSync's rules you define which data can move into Brivity.
On to the connection rules. These define which contacts are in the scope of the sync. Rules come with filters and actions which will prove tremendously useful in syncs with other apps such as CRMs or marketing platforms.
Leaving the default setup, PieSync would create in Brivity any newly created Command contacts (1), as well as in fact create any new Brivity contacts in Command (2). Once they are created or identified, it would update and keep those contacts in continuous sync (3). It would do the same in the other way round, requiring PieSync to identify which contacts are potentially already present in both systems.
PieSync matches contacts on the basis of their email address exclusively
This default setup works perfectly for most agents. PieSync will make sure the addressbook in Brivity stays in sync with the contacts data in KW Command.
Stage & Tag syncing
If you like a bit more control, and don't want to overload either system with contacts, you could filter the rules. For instance, filter KW Command's rule to only sync contacts in a certain stage. In the following two rules, we only allow PieSync to start syncing Qualified leads. And to bring over the contacts that have the tag Agent into Brivity and add the same tag there.
Underneath the rules, we give you some easy toggles to play around with to tweak your connection even more.
Only sync contacts with an email address
'Avoid Duplicates' is enabled in the configuration set-up so that PieSync will only sync contacts that have an email address. We use the email address as the main identifier for a contact in order for us to prevent creating duplicates and to match and enrich contacts where possible in both applications. Read more about this
Default field mappings
The field mapping defines how contacts will sync. A huge time & lifesaver in PieSync is that most of these are automatically set for all basic contact fields that Command & Brivity share by default.
Typically it's best to keep these default field mappings all activated as they represent the essential contact attributes that you would not want to grow out of sync in any circumstance.
Customizable field mappings
Field mapping also includes ability to include the mapping of number of kids, a field that can be created in Brivity as well. Mappings are fully customizable not only before setting up a new sync, but it can also be modified for an ongoing sync.
PieSync syncs more than just Brivity
Being able to sync Command with Brivity aids in frictionless selling because it keeps the underlying contact data in sync, and saves time in manual import/export operations.
That ease of use & data consistency comes in handy as well when syncing contacts to a billing app, or a secondary CRM, a VOIP system, or even another dedicated marketing platform.
Here’s what this could look like syncing not only Command and Brivity, but Google Contacts and Dotloop as well.
PieSync is not only a turnkey solution to sync Command and Brivity exclusively. In fact, it solves a data problem that goes beyond these two apps. On average, users tend to connect 3-4 applications all through PieSync.