Available Columns in the Contacts Applet

Your Command contact database includes the ability to fully customize how you view your contacts, based on the task at hand. You can choose which columns show up, and in which order. Below are the columns that are available for you to add and what they mean:

Team Specific Columns

Owner - denotes who can take the contact with them if they leave the team, as well as who has the ability to delete or export the contact.

• In a team account, the team can be the owner of a contact, instead of an agent on the team. This is a good way for a Rainmaker to distinguish their own SOI from team captured leads/contacts, while still allowing the Rainmaker or team members with Unlimited permissions to assign these to team members.

Assignee - this denotes the team member who is taking point on the contact. This gives team members with Standard permissions visibility into the contact and the ability to do things like edit the contact details, add the contact to team SmartPlans and campaigns, create Opportunities for the contact, and more.

Legacy Tags - all custom tags that were added to contacts prior to them being moved to the team Command account will remain on the contact in the Team Contact Database. These are labeled as Legacy Tags on the contact card, and will remain on the contact unless it is removed or if the contact ownership is changed to a different team member.

• Keep in mind that these Legacy Tags cannot be added to other contacts in the team Command account, and are meant to be temporary while the new Team Contact Tags are applied to the contacts. 
  
  

Universal Columns

Primary Email - the main email address added to a contact, and the default email address SmartPlans and Campaigns will send emails to.

Primary Phone - the main phone number added to a contact, and the default phone number SmartPlans will send text messages to, using Twilio. 

Primary Address - the main physical address added to a contact, and the physical address that generates the Primary Neighborhood associated with a contact.

Mailing Address - the physical address added to a contact where direct mail campaigns will be sent (when you target your database), and the physical address required for exporting mailing labels, in Command.

Tags - labels you can add to your contacts to help you group contacts together, in ways that make sense to your business. You have the ability to color code tags, as visual indicators, and you can apply multiple tags to a single contact. These tags can also be used to trigger contacts to be added to specific SmartPlans, and you have the ability to trigger tags to be automatically added to leads captured from specific social campaigns.

Recently Active - the date a contact last interacted with your KW Site or App. This will advance when a contact logs in to either, or takes an action on your site or app that logs on the contact timeline.

Last Contacted - the date you last interacted with a contact. This includes any email sent using Command Email (SmartPlans, Client Updates, Email Campaigns, and sharing offer comparisons), text messages sent using Twilio in Command, and interactions you log manually on a contact (calls, notes, texts, emails, and meetings).

• The exception is any email or notification the system sends to contacts that come from the KW Consumer platform. If your client sets up alerts for things like saved searches or collection updates, and the system will send those emails using a no-reply email address.

Last Message - this field is not currently being used.

Created - the date a contact was captured or entered in Command.

Updated - the last date a change was made to a contact, or that a new contact timeline event was logged. If neither of those things have occurred, it will display the Created date here.

Date of Birth - the date of birth entered for a contact, and the date that triggers the "My Birthday" SmartPlan.

Company - the company the contact works for.

Title - the job title of the contact.

Custom Fields - when managing columns, in Contacts, all of the custom fields you have created will be available to be added to the database view, where you can sort the database by that column. Each agent or team must create the custom field first, before it can be added as a column.